diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_0_0/5322-dstu3-validation-resources-are-out-of-date.yaml b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_0_0/5322-dstu3-validation-resources-are-out-of-date.yaml
new file mode 100644
index 00000000000..eb452d7d298
--- /dev/null
+++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_0_0/5322-dstu3-validation-resources-are-out-of-date.yaml
@@ -0,0 +1,4 @@
+---
+type: fix
+issue: 5322
+title: "Update DSTU3 validation resources to FHIR 3.0.2 instead of 3.0.1"
diff --git a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-others.xml b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-others.xml
index 63aadad65fc..095cfe62d20 100644
--- a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-others.xml
+++ b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-others.xml
@@ -1,7 +1,7 @@
 <Bundle xmlns="http://hl7.org/fhir">
  <id value="profiles-others"></id>
  <meta>
-  <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+  <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
  </meta>
  <type value="collection"></type>
  <entry>
@@ -21,7 +21,7 @@
      </telecom>
     </contact>
     <description value="Consent Directive"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -3269,7 +3269,7 @@
      </telecom>
     </contact>
     <description value="Adds additional information to a family member history supporting both the capture of mother/father relationships as well as additional observations necessary to enable genetics-based risk analysis for patients"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -3412,7 +3412,9 @@
       <path value="FamilyMemberHistory.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -4541,10 +4543,10 @@
     <name value="Shareable ValueSet"></name>
     <status value="draft"></status>
     <experimental value="false"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7"></publisher>
     <description value="Enforces the minimum information set for the value set metadata required by HL7 and other organisations that share and publish value sets"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -4672,7 +4674,9 @@
       <path value="ValueSet.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -4929,7 +4933,8 @@
       <path value="ValueSet.status"></path>
       <short value="draft | active | retired | unknown"></short>
       <definition value="The status of this value set. Enables tracking the life-cycle of the content."></definition>
-      <comment value="Allows filtering of value sets that are appropriate for use vs. not.   This is labeled as &quot;Is Modifier&quot; because applications should not use a retired value set without due consideration."></comment>
+      <comment value="Allows filtering of value sets that are appropriate for use vs. not.  
+This is labeled as &quot;Is Modifier&quot; because applications should not use a retired value set without due consideration."></comment>
       <min value="1"></min>
       <max value="1"></max>
       <base>
@@ -6654,7 +6659,7 @@
      </telecom>
     </contact>
     <description value="Describes how the ProcedureRequest resource is used to for genetics"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -6788,7 +6793,9 @@
       <path value="ProcedureRequest.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -7126,7 +7133,9 @@
       <path value="ProcedureRequest.status"></path>
       <short value="draft | active | suspended | completed | entered-in-error | cancelled"></short>
       <definition value="The status of the order."></definition>
-      <comment value="The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](event.html) for general discussion) or using the [Task](task.html) resource.  This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid."></comment>
+      <comment value="The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](event.html) for general discussion) or using the [Task](task.html) resource.
+
+This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid."></comment>
       <min value="1"></min>
       <max value="1"></max>
       <base>
@@ -7338,7 +7347,7 @@
         <valueString value="ProcedureRequestCode"></valueString>
        </extension>
        <strength value="example"></strength>
-       <description value="Codes for tests/services that can be performed by procedure or diagnostic services.  For laboratory, LOINC is  (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html)."></description>
+       <description value="Codes for tests/services that can be performed by procedure or diagnostic services.  For laboratory, LOINC is  (preferred)[http://hl7.org/fhir/STU3/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html)."></description>
        <valueSetReference>
         <reference value="http://hl7.org/fhir/ValueSet/procedure-code"></reference>
        </valueSetReference>
@@ -8067,7 +8076,7 @@
       <path value="ProcedureRequest.relevantHistory"></path>
       <short value="Request provenance"></short>
       <definition value="Key events in the history of the request."></definition>
-      <comment value="This may not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource.  (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update.  Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject."></comment>
+      <comment value="This may not include provenances for all versions of the request – only those deemed “relevant” or important.
This SHALL NOT include the Provenance associated with this current version of the resource.  (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update.  Until then, it can be queried directly as the Provenance that points to this version using _revinclude
All Provenances should have some historical version of this Request as their subject."></comment>
       <min value="0"></min>
       <max value="*"></max>
       <base>
@@ -8124,10 +8133,10 @@
     <name value="Shareable CodeSystem"></name>
     <status value="draft"></status>
     <experimental value="false"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7"></publisher>
     <description value="Enforces the minimum information set for the value set metadata required by HL7 and other organisations that share and publish value sets"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -8250,7 +8259,9 @@
       <path value="CodeSystem.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -8499,7 +8510,8 @@
       <path value="CodeSystem.status"></path>
       <short value="draft | active | retired | unknown"></short>
       <definition value="The status of this code system. Enables tracking the life-cycle of the content."></definition>
-      <comment value="Allows filtering of code systems that are appropriate for use vs. not.   This is labeled as &quot;Is Modifier&quot; because applications should not use a retired code system without due consideration."></comment>
+      <comment value="Allows filtering of code systems that are appropriate for use vs. not.  
+This is labeled as &quot;Is Modifier&quot; because applications should not use a retired code system without due consideration."></comment>
       <min value="1"></min>
       <max value="1"></max>
       <base>
@@ -9802,7 +9814,7 @@
      </telecom>
     </contact>
     <description value="This profile describes the direct or derived, qualitative or quantitative physiological measurement, setting, or calculation data produced by a medical device or a device component."></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -9965,7 +9977,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -10340,7 +10354,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -10532,7 +10546,7 @@
       <path value="Observation.value[x]"></path>
       <short value="Actual result"></short>
       <definition value="The information determined as a result of making the observation, if the information has a simple value."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -11043,7 +11057,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -11082,7 +11096,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -11424,7 +11438,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -11829,7 +11843,7 @@
      </telecom>
     </contact>
     <description value="Describes how the observation resource is used to report structured genetic test results"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -11992,7 +12006,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -12877,7 +12893,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -13076,7 +13092,7 @@
       <path value="Observation.value[x]"></path>
       <short value="Actual result"></short>
       <definition value="The information determined as a result of making the observation, if the information has a simple value."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -13584,7 +13600,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -13623,7 +13639,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -13970,7 +13986,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -14348,7 +14364,60 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="vitalsigns"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="### Complete Summary of the Mandatory Requirements  1.  One status in `Observation.status`which has a [required](http://build.fhir.org/terminologies.html#extensible) binding to:  -    [ObservationStatus] value set. 1.  A category in `Observation.category` which must have:  -   a fixed `Observation.category.coding.system`=&quot;http://hl7.org/fhir/observation-category&quot;  -   a fixed `Observation.category.coding.code`= &quot;vital-signs&quot;  1.  A code in `Observation.code`  -   a fixed `Observation.code.coding.system`= &quot;http://loinc.org&quot;  -   a LOINC code in `Observation.code.coding.code` which has an [extensible](http://build.fhir.org/terminologies.html#extensible) binding to:    -   [Vital Signs] value set.       1.  One patient in `Observation.subject` 1.  A date and time in `effectiveDateTime` or `effectivePeriod` 1.  Either one `Observation.valueQuantity` or, if there is no value, one code in `Observation.DataAbsentReason`  -   Each Observation.valueQuantity must have:   -   One numeric value in `Observation.valueQuantity.value`   -   a fixed `Observation.valueQuantity.system`=&quot;http://unitsofmeasure&quot;   -   a UCUM unit code in `Observation.valueQuantity.code` which has an [required] binding to:     -   [Vital Signs Units] value set.  -   Observation.DataAbsentReason is bound to [Observation Value   Absent Reason] value set.  1.  When using a panel code to group component observations (Note: See  the comments regarding blood pressure in the table above), one or  more `Observation.component.code` each of which must have:  -   a fixed   `Observation.component.code.coding.system` =&quot;&lt;http://loinc.org&gt;&quot;    -   a LOINC code in `Observation.code.coding.code` which has an [extensible] binding to:     -   [Vital Signs Units] value set.  1.  Either one `Observation.component.valueQuantity` or, if there is  no value, one code in `Observation.component.DataAbsentReason`  -   Each Observation.component.valueQuantity must have:   -   One numeric value in     `Observation.component.valueQuantity.value`   -   a fixed `Observation.component.valueQuantity.system`= &quot;&lt;http://unitsofmeasure.org&gt;&quot;   -   a UCUM unit code in     `Observation.component.valueQuantity.code` which has an [required] binding to:     -   [Vital Signs Units] value set.  -   Observation.component.DataAbsentReason is bound to [Observation   Value Absent Reason] value set.  1.  When using a panel code to group observations, one or more reference  to Vitals Signs Observations in `Observation.related.target`  -   a fixed `Observation.related.type`= &quot;has-member&quot;  [Vital Signs]: valueset-observation-vitalsignresult.html [Vital Signs Units]: valueset-ucum-vitals-common.html [extensible]: terminologies.html#extensible [ObservationStatus]: valueset-observation-status.html [Observation Value Absent Reason]: valueset-observation-valueabsentreason.html [required]: terminologies.html#required"></valueMarkdown>
+     <valueMarkdown value="### Complete Summary of the Mandatory Requirements
+
+1.  One status in `Observation.status`which has a [required](http://hl7.org/fhir/STU3/terminologies.html#extensible) binding to:
+ -    [ObservationStatus] value set.
+1.  A category in `Observation.category` which must have:
+ -   a fixed `Observation.category.coding.system`=&quot;http://hl7.org/fhir/observation-category&quot;
+ -   a fixed `Observation.category.coding.code`= &quot;vital-signs&quot;
+
+1.  A code in `Observation.code`
+ -   a fixed `Observation.code.coding.system`= &quot;http://loinc.org&quot;
+ -   a LOINC code in `Observation.code.coding.code` which has an [extensible](http://hl7.org/fhir/STU3/terminologies.html#extensible) binding to:
+   -   [Vital Signs] value set.
+     
+1.  One patient in `Observation.subject`
+1.  A date and time in `effectiveDateTime` or `effectivePeriod`
+1.  Either one `Observation.valueQuantity` or, if there is no value, one code in `Observation.DataAbsentReason`
+ -   Each Observation.valueQuantity must have:
+  -   One numeric value in `Observation.valueQuantity.value`
+  -   a fixed `Observation.valueQuantity.system`=&quot;http://unitsofmeasure&quot;
+  -   a UCUM unit code in `Observation.valueQuantity.code` which has an [required] binding to:
+    -   [Vital Signs Units] value set.
+ -   Observation.DataAbsentReason is bound to [Observation Value
+  Absent Reason] value set.
+
+1.  When using a panel code to group component observations (Note: See
+ the comments regarding blood pressure in the table above), one or
+ more `Observation.component.code` each of which must have:
+ -   a fixed
+  `Observation.component.code.coding.system` =&quot;&lt;http://loinc.org&gt;&quot;
+   -   a LOINC code in `Observation.code.coding.code` which has an [extensible] binding to:
+    -   [Vital Signs Units] value set.
+
+1.  Either one `Observation.component.valueQuantity` or, if there is
+ no value, one code in `Observation.component.DataAbsentReason`
+ -   Each Observation.component.valueQuantity must have:
+  -   One numeric value in
+    `Observation.component.valueQuantity.value`
+  -   a fixed `Observation.component.valueQuantity.system`= &quot;&lt;http://unitsofmeasure.org&gt;&quot;
+  -   a UCUM unit code in
+    `Observation.component.valueQuantity.code` which has an [required] binding to:
+    -   [Vital Signs Units] value set.
+ -   Observation.component.DataAbsentReason is bound to [Observation
+  Value Absent Reason] value set.
+
+1.  When using a panel code to group observations, one or more reference
+ to Vitals Signs Observations in `Observation.related.target`
+ -   a fixed `Observation.related.type`= &quot;has-member&quot;
+
+[Vital Signs]: valueset-observation-vitalsignresult.html
+[Vital Signs Units]: valueset-ucum-vitals-common.html
+[extensible]: terminologies.html#extensible
+[ObservationStatus]: valueset-observation-status.html
+[Observation Value Absent Reason]: valueset-observation-valueabsentreason.html
+[required]: terminologies.html#required"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/vitalsigns"></url>
     <name value="Vital Signs Profile"></name>
@@ -14364,7 +14433,7 @@
      </telecom>
     </contact>
     <description value="FHIR Vital Signs Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -14469,7 +14538,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
       </constraint>
       <mapping>
@@ -14534,7 +14603,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -14915,7 +14986,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -15111,7 +15182,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -15799,7 +15870,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -15838,7 +15909,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -16190,7 +16261,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -16568,7 +16639,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
       </constraint>
      </element>
@@ -16891,7 +16962,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="bodyweight"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'29463-7'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  `Observation.valueQuantity.code` = **'kg', 'g', or '[lb_av]'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'29463-7'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  `Observation.valueQuantity.code` = **'kg', 'g', or '[lb_av]'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/bodyweight"></url>
     <name value="Vital Signs Profile"></name>
@@ -16907,7 +16978,7 @@
      </telecom>
     </contact>
     <description value="FHIR Body Weight Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -17012,7 +17083,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -17078,7 +17149,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -17816,7 +17889,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -18012,7 +18085,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -18710,7 +18783,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -18749,7 +18822,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -19101,7 +19174,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -19535,7 +19608,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="resprate"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'9279-1'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'/min'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'9279-1'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'/min'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/resprate"></url>
     <name value="Vital Signs Profile"></name>
@@ -19551,7 +19624,7 @@
      </telecom>
     </contact>
     <description value="FHIR Respiratory Rate Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -19656,7 +19729,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -19722,7 +19795,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -20460,7 +20535,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -20656,7 +20731,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -21345,7 +21420,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -21384,7 +21459,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -21736,7 +21811,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -22164,7 +22239,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="heartrate"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'8867-4'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'/min'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'8867-4'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'/min'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/heartrate"></url>
     <name value="Vital Signs Profile"></name>
@@ -22180,7 +22255,7 @@
      </telecom>
     </contact>
     <description value="FHIR Heart Rate Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -22285,7 +22360,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -22351,7 +22426,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -23089,7 +23166,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -23285,7 +23362,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -23974,7 +24051,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -24013,7 +24090,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -24365,7 +24442,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -24793,7 +24870,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="bodytemp"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'8310-5'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'Cel', or '[degF]'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'8310-5'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'Cel', or '[degF]'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/bodytemp"></url>
     <name value="Vital Signs Profile"></name>
@@ -24809,7 +24886,7 @@
      </telecom>
     </contact>
     <description value="FHIR Body Temperature Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -24914,7 +24991,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -24980,7 +25057,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -25718,7 +25797,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -25914,7 +25993,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -26612,7 +26691,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -26651,7 +26730,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -27003,7 +27082,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -27437,7 +27516,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="bodyheight"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'8302-2'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'cm', or '[in_i]'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'8302-2'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'cm', or '[in_i]'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/bodyheight"></url>
     <name value="Vital Signs Profile"></name>
@@ -27453,7 +27532,7 @@
      </telecom>
     </contact>
     <description value="FHIR Body Height Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -27558,7 +27637,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -27624,7 +27703,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -28362,7 +28443,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -28558,7 +28639,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -29256,7 +29337,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -29295,7 +29376,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -29647,7 +29728,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -30081,7 +30162,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="bodylength"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'8306-3'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'cm', or '[in_i]'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'8306-3'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'cm', or '[in_i]'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/bodylength"></url>
     <name value="Vital Signs Profile"></name>
@@ -30097,7 +30178,7 @@
      </telecom>
     </contact>
     <description value="FHIR Body Length Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -30202,7 +30283,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -30268,7 +30349,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -31006,7 +31089,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -31202,7 +31285,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -31900,7 +31983,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -31939,7 +32022,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -32291,7 +32374,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -32725,7 +32808,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="headcircum"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'8287-5'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'cm', or '[in_i]'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'8287-5'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'cm', or '[in_i]'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/headcircum"></url>
     <name value="Vital Signs Profile"></name>
@@ -32741,7 +32824,7 @@
      </telecom>
     </contact>
     <description value="FHIR Head Circumference Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -32846,7 +32929,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -32912,7 +32995,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -33650,7 +33735,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -33846,7 +33931,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -34544,7 +34629,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -34583,7 +34668,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -34935,7 +35020,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -35369,7 +35454,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="oxygensat"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="&quot;####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'59408-5'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'%'** &quot;"></valueMarkdown>
+     <valueMarkdown value="&quot;####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'59408-5'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'%'**
&quot;"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/oxygensat"></url>
     <name value="Vital Signs Profile"></name>
@@ -35385,7 +35470,7 @@
      </telecom>
     </contact>
     <description value="FHIR Oxygen Saturation Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -35490,7 +35575,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -35556,7 +35641,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -36294,7 +36381,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -36490,7 +36577,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -37179,7 +37266,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -37218,7 +37305,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -37570,7 +37657,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -37998,7 +38085,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="bmi"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **'39156-5'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  a fixed`Observation.valueQuantity.code` = **'kg/m2'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **'39156-5'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  a fixed`Observation.valueQuantity.code` = **'kg/m2'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/bmi"></url>
     <name value="Vital Signs Profile"></name>
@@ -38014,7 +38101,7 @@
      </telecom>
     </contact>
     <description value="FHIR Body Mass Index (BMI) Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -38119,7 +38206,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -38185,7 +38272,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -38923,7 +39012,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -39119,7 +39208,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -39808,7 +39897,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -39847,7 +39936,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -40199,7 +40288,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -40627,7 +40716,7 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="bp"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have     -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**     -   a fixed  `Observation.code.coding.code`= **85354-9'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 2.  One  `Observation.component.code`  which must have     -   a fixed `Observation.component.code.coding.system`=**'http://loinc.org'**     -   fixed  `Observation.component.code.coding.code`= **'8480-6'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 3.   One  `Observation.component.code`  which must have     -   a fixed `Observation.component.code.coding.system`=**'http://loinc.org'**     -   fixed  `Observation.component.code.coding.code`= **'8462-4'**     -   Other additional codes are allowed - e.g. more specific LOINC         Codes, SNOMED CT concepts, system specific codes. All codes         SHALL have an system value 4.  fixed`Observation.component.valueQuantity.code` = **'mm[Hg]'**"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **85354-9'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  One  `Observation.component.code`  which must have
    -   a fixed `Observation.component.code.coding.system`=**'http://loinc.org'**
    -   fixed  `Observation.component.code.coding.code`= **'8480-6'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
3.   One  `Observation.component.code`  which must have
    -   a fixed `Observation.component.code.coding.system`=**'http://loinc.org'**
    -   fixed  `Observation.component.code.coding.code`= **'8462-4'**
    -   Other additional codes are allowed - e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
4.  fixed`Observation.component.valueQuantity.code` = **'mm[Hg]'**"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/bp"></url>
     <name value="Vital Signs Profile"></name>
@@ -40643,7 +40732,7 @@
      </telecom>
     </contact>
     <description value="FHIR Blood Pressure Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -40748,7 +40837,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -40814,7 +40903,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -41552,7 +41643,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -41748,7 +41839,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="0"></max>
@@ -42436,7 +42527,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -42475,7 +42566,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -42883,7 +42974,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -43741,7 +43832,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -44636,7 +44727,16 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="vitalspanel"></id>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-summary">
-     <valueMarkdown value="####Complete Summary of the Mandatory Requirements  1.  One code in `Observation.code` which must have  -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**  -   a fixed  `Observation.code.coding.code`= **'85353-1'**  -   Other additional codes are allowed - e.g. more specific LOINC   Codes, SNOMED CT concepts, system specific codes. All codes   SHALL have an system value 1.  No value in `Observation.value[x]` 1.  At Least one Vitals Sign Observation reference in `Observation.related`"></valueMarkdown>
+     <valueMarkdown value="####Complete Summary of the Mandatory Requirements
+
+1.  One code in `Observation.code` which must have
+ -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
+ -   a fixed  `Observation.code.coding.code`= **'85353-1'**
+ -   Other additional codes are allowed - e.g. more specific LOINC
+  Codes, SNOMED CT concepts, system specific codes. All codes
+  SHALL have an system value
+1.  No value in `Observation.value[x]`
+1.  At Least one Vitals Sign Observation reference in `Observation.related`"></valueMarkdown>
     </extension>
     <url value="http://hl7.org/fhir/StructureDefinition/vitalspanel"></url>
     <name value="Vital Signs Profile"></name>
@@ -44652,7 +44752,7 @@
      </telecom>
     </contact>
     <description value="FHIR Vital Signs Panel Profile"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -44757,7 +44857,7 @@
        <key value="vs-2"></key>
        <severity value="error"></severity>
        <human value="If there is no component or related element then either a value[x] or a data absent reason must be present"></human>
-       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason or value)"></expression>
+       <expression value="(component.empty() and related.empty()) implies (dataAbsentReason.exists() or value.exists())"></expression>
        <xpath value="exists(f:component) or exists(f:related) or exists(f:*[starts-with(local-name(.), 'value')]) or exists(f:dataAbsentReason)"></xpath>
        <source value="Observation"></source>
       </constraint>
@@ -44823,7 +44923,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -45561,7 +45663,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -45757,7 +45859,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Vital Sign Value recorded with UCUM"></short>
       <definition value="Vital Sign Value recorded with UCUM."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="9. SHALL contain exactly one [1..1] value with @xsi:type=&quot;PQ&quot; (CONF:7305)."></requirements>
       <min value="0"></min>
       <max value="0"></max>
@@ -46445,7 +46547,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -46484,7 +46586,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -46836,7 +46938,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -47285,7 +47387,7 @@
      </telecom>
     </contact>
     <description value="Lipid Lab Report"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -47420,7 +47522,9 @@
       <path value="DiagnosticReport.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -48744,7 +48848,7 @@
      </telecom>
     </contact>
     <description value="Describes how the lab report is used for a standard Lipid Profile - Cholesterol, Triglyceride and Cholesterol fractions. Uses LOINC codes"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -48907,7 +49011,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -49287,7 +49393,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -49486,7 +49592,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Cholesterol value"></short>
       <definition value="Cholesterol value. If a result is not available, use the comments field."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -50202,7 +50308,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -50241,7 +50347,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -50588,7 +50694,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -50957,7 +51063,7 @@
      </telecom>
     </contact>
     <description value="Triglyceride Result"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -51120,7 +51226,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -51499,7 +51607,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -51698,7 +51806,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="Triglyceride value"></short>
       <definition value="Triglyceride value. If a result is not available, use the comments field."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -52183,7 +52291,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -52222,7 +52330,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -52569,7 +52677,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -52882,7 +52990,7 @@
      </telecom>
     </contact>
     <description value="HDL Cholesterol Result"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -53045,7 +53153,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -53425,7 +53535,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -53624,7 +53734,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="HDL Cholesterol value"></short>
       <definition value="HDL Cholesterol value. If a result is not available, use the comments field."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -54140,7 +54250,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -54179,7 +54289,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -54526,7 +54636,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -54847,7 +54957,7 @@
      </telecom>
     </contact>
     <description value="LDL Cholesterol Result"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -55010,7 +55120,9 @@
       <path value="Observation.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -55383,7 +55495,7 @@
       <path value="Observation.subject"></path>
       <short value="Who and/or what this is about"></short>
       <definition value="The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed.  Comments: Indirect characteristics may be those of a specimen, fetus, donor,  other observer (for example a relative or EMT), or any observation made about the subject."></definition>
-      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.  If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
+      <comment value="One would expect this element to be a cardinality  of 1..1.  The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

If the target of the observation is different than the subject, the general extension [observation-focal-subject](extension-observation-focal-subject.html).  may be used.  However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code."></comment>
       <requirements value="Observations have no value if you don't know who or what they're about."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -55582,7 +55694,7 @@
       <path value="Observation.valueQuantity"></path>
       <short value="LDL Cholesterol value"></short>
       <definition value="LDL Cholesterol value. If a result is not available, use the comments field."></definition>
-      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).   If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
+      <comment value="Normally, an observation will have either a single value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is derived). If a value is present, the datatype for this element should be determined by Observation.code. This element has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueString, valueBoolean, valueRange, valueRatio, valueSampledData, valueAttachment, valueTime, valueDateTime, or valuePeriod. (The name format is &quot;'value' + the type name&quot; with a capital on the first letter of the type).


If the data element is usually coded or if the type associated with the Observation.value defines a coded value, use CodeableConcept instead of string datatype even if the value is uncoded text.  A value set is bound to the ValueCodeableConcept element.    For further discussion and examples see the  [notes section](observation.html#notes) below."></comment>
       <requirements value="An observation exists to have a value, though it may not if it is in error, or if it represents a group of observations."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -56097,7 +56209,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -56136,7 +56248,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 260245000 |Findings values| OR   &lt; 365860008 |General clinical state finding|  OR  &lt; 250171008 |Clinical history or observation findings| OR   &lt; 415229000 |Racial group| OR  &lt; 365400002 |Finding of puberty stage| OR &lt; 443938003 |Procedure carried out on subject|"></map>
+       <map value="&lt; 260245000 |Findings values| OR  
&lt; 365860008 |General clinical state finding| 
OR 
&lt; 250171008 |Clinical history or observation findings| OR  
&lt; 415229000 |Racial group| OR 
&lt; 365400002 |Finding of puberty stage| OR
&lt; 443938003 |Procedure carried out on subject|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -56483,7 +56595,7 @@
       </binding>
       <mapping>
        <identity value="sct-concept"></identity>
-       <map value="&lt; 363787002 |Observable entity| OR  &lt; 386053000 |Evaluation procedure|"></map>
+       <map value="&lt; 363787002 |Observable entity| OR 
&lt; 386053000 |Evaluation procedure|"></map>
       </mapping>
       <mapping>
        <identity value="v2"></identity>
@@ -56801,7 +56913,7 @@
      </telecom>
     </contact>
     <description value="Describes how the DiagnosticReport resource is used to report structured genetic test results"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -56936,7 +57048,9 @@
       <path value="DiagnosticReport.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -58130,7 +58244,7 @@
      </telecom>
     </contact>
     <description value="Describes how the HLA genotyping results"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -58265,7 +58379,9 @@
       <path value="DiagnosticReport.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -58489,8 +58605,8 @@
      <element id="DiagnosticReport.extension:method">
       <path value="DiagnosticReport.extension"></path>
       <sliceName value="method"></sliceName>
-      <short value="The platform, methodology and software applied at the time of the genotyping"></short>
-      <definition value="The platform, methodology and software applied at the time of the genotyping."></definition>
+      <short value="The platform, methodology and software applied at the time of the
genotyping"></short>
+      <definition value="The platform, methodology and software applied at the time of the
genotyping."></definition>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -59466,8 +59582,8 @@
      <element id="DiagnosticReport.extension:method">
       <path value="DiagnosticReport.extension"></path>
       <sliceName value="method"></sliceName>
-      <short value="The platform, methodology and software applied at the time of the genotyping"></short>
-      <definition value="The platform, methodology and software applied at the time of the genotyping."></definition>
+      <short value="The platform, methodology and software applied at the time of the
genotyping"></short>
+      <definition value="The platform, methodology and software applied at the time of the
genotyping."></definition>
       <min value="0"></min>
       <max value="1"></max>
       <type>
@@ -59497,7 +59613,7 @@
      </telecom>
     </contact>
     <description value="The base Composition is a general resource for compositions or documents about any kind of subject that might be encountered in healthcare including such things as guidelines, medicines, etc. A clinical document is focused on documents related to the provision of care process, where the subject is a patient, a group of patients, or a closely related concept. A clinical document has additional reqiurements around confidentiality that do not apply in the same way to other kinds of documents"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -59617,7 +59733,9 @@
       <path value="Composition.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -59791,7 +59909,9 @@
       <path value="Composition.status"></path>
       <short value="preliminary | final | amended | entered-in-error"></short>
       <definition value="The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document."></definition>
-      <comment value="If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag &quot;entered-in-error&quot; is why this element is labeled as a modifier of other elements.   Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required."></comment>
+      <comment value="If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag &quot;entered-in-error&quot; is why this element is labeled as a modifier of other elements. 
+
+Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required."></comment>
       <requirements value="Need to be able to mark interim, amended, or withdrawn compositions or documents."></requirements>
       <min value="1"></min>
       <max value="1"></max>
@@ -60086,7 +60206,9 @@
       <path value="Composition.confidentiality"></path>
       <short value="As defined by affinity domain"></short>
       <definition value="The code specifying the level of confidentiality of the Composition."></definition>
-      <comment value="The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section).  This element is labeled as a modifier because highly confidential documents must not be treated as if they are not."></comment>
+      <comment value="The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section).
+
+This element is labeled as a modifier because highly confidential documents must not be treated as if they are not."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -61112,7 +61234,7 @@
      </telecom>
     </contact>
     <description value="Identifies how the ElementDefinition data type is used when it appears within a data element"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="dex"></identity>
      <uri value="http://wiki.ihe.net/index.php?title=Data_Element_Exchange"></uri>
@@ -61231,9 +61353,9 @@
       <constraint>
        <key value="eld-16"></key>
        <severity value="error"></severity>
-       <human value="sliceName must be a proper token"></human>
-       <expression value="sliceName.empty() or sliceName.matches('^[a-zA-Z0-9\\-\\_]+$')"></expression>
-       <xpath value="not(exists(f:sliceName/@value)) or matches(f:sliceName/@value, '^[a-zA-Z0-9\\-\\_]+$')"></xpath>
+       <human value="sliceName must be composed of proper tokens separated by &quot;/&quot;"></human>
+       <expression value="sliceName.empty() or sliceName.matches('^[a-zA-Z0-9\\/\\-\\_]+$')"></expression>
+       <xpath value="not(exists(f:sliceName/@value)) or matches(f:sliceName/@value, '^[a-zA-Z0-9\\/\\-\\_]+$')"></xpath>
        <source value="ElementDefinition"></source>
       </constraint>
       <constraint>
@@ -62710,7 +62832,8 @@
       <path value="ElementDefinition.defaultValue[x]"></path>
       <short value="Specified value if missing from instance"></short>
       <definition value="The value that should be used if there is no value stated in the instance (e.g. 'if not otherwise specified, the abstract is false')."></definition>
-      <comment value="Default values can only be specified on a resource, data type, or extension definition, and never in a profile that applies to one of these. Specifying a default value means that the property can never been unknown - it must always have a value. Further, the default value can never be changed. For these reasons, default values are (and should be) used extremely sparingly. This element should only be used on child elements of complex data elements."></comment>
+      <comment value="Default values can only be specified on a resource, data type, or extension definition, and never in a profile that applies to one of these. Specifying a default value means that the property can never been unknown - it must always have a value. Further, the default value can never be changed. For these reasons, default values are (and should be) used extremely sparingly.
+This element should only be used on child elements of complex data elements."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -62846,7 +62969,8 @@
       <path value="ElementDefinition.meaningWhenMissing"></path>
       <short value="Implicit meaning when this element is missing"></short>
       <definition value="The Implicit meaning that is to be understood when this element is missing (e.g. 'when this element is missing, the period is ongoing'."></definition>
-      <comment value="Implicit meanings for missing values can only be specified on a resource, data type, or extension definition, and never in a profile that applies to one of these. An implicit meaning for a missing value can never be changed, and specifying one has the consequence that constraining its use in profiles eliminates use cases as possibilities, not merely moving them out of scope. This element should only be used on child elements of complex data elements."></comment>
+      <comment value="Implicit meanings for missing values can only be specified on a resource, data type, or extension definition, and never in a profile that applies to one of these. An implicit meaning for a missing value can never be changed, and specifying one has the consequence that constraining its use in profiles eliminates use cases as possibilities, not merely moving them out of scope.
+This element should only be used on child elements of complex data elements."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -63744,7 +63868,9 @@
       <path value="ElementDefinition.constraint.xpath"></path>
       <short value="XPath expression of constraint"></short>
       <definition value="An XPath expression of constraint that can be executed to see if this constraint is met."></definition>
-      <comment value="Elements SHALL use &quot;f&quot; as the namespace prefix for the FHIR namespace, and &quot;x&quot; for the xhtml namespace, and SHALL NOT use any other prefixes.   Note: we are considering deprecating the xpath element. Implementer feedback is welcome."></comment>
+      <comment value="Elements SHALL use &quot;f&quot; as the namespace prefix for the FHIR namespace, and &quot;x&quot; for the xhtml namespace, and SHALL NOT use any other prefixes. 
+
+Note: we are considering deprecating the xpath element. Implementer feedback is welcome."></comment>
       <requirements value="Used in Schematron tests of the validity of the resource."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -63787,7 +63913,11 @@
       <path value="ElementDefinition.mustSupport"></path>
       <short value="If the element must supported"></short>
       <definition value="If true, implementations that produce or consume resources SHALL provide &quot;support&quot; for the element in some meaningful way.  If false, the element may be ignored and not supported."></definition>
-      <comment value="&quot;Something useful&quot; is context dependent and impossible to describe in the base FHIR specification. For this reason, tue mustSupport flag is never set to true by the FHIR specification itself - it is only set to true in profiles.   This is done in [Resource Profiles](profiling.html#mustsupport), where the profile labels an element as mustSupport=true. When a profile does this, it SHALL also make clear exactly what kind of &quot;support&quot; is required, as this can mean many things.  Note that an element that has the property IsModifier is not necessarily a &quot;key&quot; element (e.g. one of the important elements to make use of the resource), nor is it automatically mustSupport - however both of these things are more likely to be true for IsModifier elements than for other elements."></comment>
+      <comment value="&quot;Something useful&quot; is context dependent and impossible to describe in the base FHIR specification. For this reason, tue mustSupport flag is never set to true by the FHIR specification itself - it is only set to true in profiles. 
+
+This is done in [Resource Profiles](profiling.html#mustsupport), where the profile labels an element as mustSupport=true. When a profile does this, it SHALL also make clear exactly what kind of &quot;support&quot; is required, as this can mean many things.
+
+Note that an element that has the property IsModifier is not necessarily a &quot;key&quot; element (e.g. one of the important elements to make use of the resource), nor is it automatically mustSupport - however both of these things are more likely to be true for IsModifier elements than for other elements."></comment>
       <requirements value="Allows a profile to set expectations for system capabilities beyond merely respecting cardinality constraints."></requirements>
       <min value="0"></min>
       <max value="1"></max>
@@ -63891,13 +64021,6 @@
        <xpath value="@value|f:*|h:div"></xpath>
        <source value="Element"></source>
       </constraint>
-      <constraint>
-       <key value="eld-10"></key>
-       <severity value="error"></severity>
-       <human value="provide either a reference or a description (or both)"></human>
-       <expression value="valueSet.exists() or description.exists()"></expression>
-       <xpath value="(exists(f:valueSetUri) or exists(f:valueSetReference)) or exists(f:description)"></xpath>
-      </constraint>
       <constraint>
        <key value="eld-12"></key>
        <severity value="error"></severity>
@@ -64034,7 +64157,6 @@
       <type>
        <code value="string"></code>
       </type>
-      <condition value="eld-10"></condition>
       <isSummary value="true"></isSummary>
       <mapping>
        <identity value="rim"></identity>
@@ -64064,7 +64186,6 @@
        <code value="Reference"></code>
        <targetProfile value="http://hl7.org/fhir/StructureDefinition/ValueSet"></targetProfile>
       </type>
-      <condition value="eld-10"></condition>
       <condition value="eld-12"></condition>
       <isSummary value="true"></isSummary>
       <mapping>
@@ -64382,7 +64503,7 @@
      </telecom>
     </contact>
     <description value="Defines the elements to be supported within the AuditEvent resource in order to conform with the Electronic Health Record System Functional Model Record Lifecycle Event standard"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -64512,7 +64633,9 @@
       <path value="AuditEvent.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -64912,7 +65035,8 @@
       </binding>
       <mapping>
        <identity value="rim"></identity>
-       <map value="* .reasonCode [ControlActReason when Act.class = CACT Control Act] *.outboundRelationship[typeCode=RSON].target"></map>
+       <map value="* .reasonCode [ControlActReason when Act.class = CACT Control Act]
+*.outboundRelationship[typeCode=RSON].target"></map>
       </mapping>
       <mapping>
        <identity value="dicom"></identity>
@@ -64935,7 +65059,9 @@
       <path value="AuditEvent.agent"></path>
       <short value="Actor involved in the event"></short>
       <definition value="An actor taking an active role in the event or activity that is logged."></definition>
-      <comment value="Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.  For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity."></comment>
+      <comment value="Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.
+
+For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity."></comment>
       <requirements value="An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility."></requirements>
       <alias value="ActiveParticipant"></alias>
       <min value="1"></min>
@@ -65295,7 +65421,10 @@
       <mustSupport value="true"></mustSupport>
       <mapping>
        <identity value="rim"></identity>
-       <map value="* Role.Class =SDLOC *Role.Code = ServiceDeliveryLocationRoleType *Entity.Code  = PlaceEntityType = df.Types of places for  Entity.Class = PLC *EntityClass = PLC = df.A physical place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant."></map>
+       <map value="* Role.Class =SDLOC
+*Role.Code = ServiceDeliveryLocationRoleType
+*Entity.Code  = PlaceEntityType = df.Types of places for  Entity.Class = PLC
+*EntityClass = PLC = df.A physical place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant."></map>
       </mapping>
       <mapping>
        <identity value="w3c.prov"></identity>
@@ -65582,7 +65711,9 @@
       </binding>
       <mapping>
        <identity value="rim"></identity>
-       <map value="*.reasonCode [ActHealthInformationPurposeOfUseReason codes/v:PurposeOfUse (2.16.840.1.113883.1.11.20448) * .outboundRelationship[typeCode=RSON or SUBJ].target"></map>
+       <map value="*.reasonCode [ActHealthInformationPurposeOfUseReason codes/v:PurposeOfUse
+(2.16.840.1.113883.1.11.20448)
+* .outboundRelationship[typeCode=RSON or SUBJ].target"></map>
       </mapping>
       <mapping>
        <identity value="w3c.prov"></identity>
@@ -66556,7 +66687,7 @@
      </telecom>
     </contact>
     <description value="Defines the elements to be supported within the Provenance resource in order to conform with the Electronic Health Record System Functional Model Record Lifecycle Event standard"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -66684,7 +66815,9 @@
       <path value="Provenance.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -67619,7 +67752,7 @@
      </telecom>
     </contact>
     <description value="A questionnaire with the ability to specify behavior associated with questions or groups of questions"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -67750,7 +67883,9 @@
       <path value="Questionnaire.implicitRules"></path>
       <short value="A set of rules under which this content was created"></short>
       <definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content."></definition>
-      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.   This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
+      <comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 
+
+This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -68055,7 +68190,8 @@
       <path value="Questionnaire.status"></path>
       <short value="draft | active | retired | unknown"></short>
       <definition value="The status of this questionnaire. Enables tracking the life-cycle of the content."></definition>
-      <comment value="Allows filtering of questionnaires that are appropriate for use vs. not.   This is labeled as &quot;Is Modifier&quot; because applications should not use a retired questionnaire without due consideration."></comment>
+      <comment value="Allows filtering of questionnaires that are appropriate for use vs. not.  
+This is labeled as &quot;Is Modifier&quot; because applications should not use a retired questionnaire without due consideration."></comment>
       <min value="1"></min>
       <max value="1"></max>
       <base>
@@ -68751,7 +68887,16 @@
      <element id="Questionnaire.item.definition">
       <path value="Questionnaire.item.definition"></path>
       <short value="ElementDefinition - details for the item"></short>
-      <definition value="A reference to an [ElementDefinition](elementdefinition.html) that provides the details for the item. If a definition is provided, then the following element values can be inferred from the definition:   * code (ElementDefinition.code) * type (ElementDefinition.type) * required (ElementDefinition.min) * repeats (ElementDefinition.max) * maxLength (ElementDefinition.maxLength) * options (ElementDefinition.binding)  Any information provided in these elements on a Questionnaire Item overrides the information from the definition."></definition>
+      <definition value="A reference to an [ElementDefinition](elementdefinition.html) that provides the details for the item. If a definition is provided, then the following element values can be inferred from the definition: 
+
+* code (ElementDefinition.code)
+* type (ElementDefinition.type)
+* required (ElementDefinition.min)
+* repeats (ElementDefinition.max)
+* maxLength (ElementDefinition.maxLength)
+* options (ElementDefinition.binding)
+
+Any information provided in these elements on a Questionnaire Item overrides the information from the definition."></definition>
       <comment value="the URI refers to an ElementDefinition in either a [StructureDefinition](structuredefinition.html#) or a [DataElement](dataelement.html#), and always starts with the canonical URL for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition. Note that [LOINC codes](loinc.html#dataelements) implicitly define DataElement resources."></comment>
       <requirements value="A common pattern is to define a set of data elements and then build multiple questionnaires for different circumstances to gather the data. This element provides traceability to the common definition and allows the content for the question to come from the underlying definition."></requirements>
       <min value="0"></min>
@@ -68806,7 +68951,11 @@
       <path value="Questionnaire.item.prefix"></path>
       <short value="E.g. &quot;1(a)&quot;, &quot;2.5.3&quot;"></short>
       <definition value="A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing the questionnaire."></definition>
-      <comment value="These are generally unique within a questionnaire, though this is not guaranteed. Some questionnaires may have multiple questions with the same label with logic to control which gets exposed.  Typically these won't be used for &quot;display&quot; items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire."></comment>
+      <comment value="These are generally unique within a questionnaire, though this is not guaranteed. Some questionnaires may have multiple questions with the same label with logic to control which gets exposed.
+
+Typically these won't be used for &quot;display&quot; items, though such use is not prohibited.
+
+Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire."></comment>
       <requirements value="Separating the label from the question text allows improved rendering.  Also, instructions will often refer to specific prefixes, so there's a need for the questionnaire design to have control over what labels are used."></requirements>
       <alias value="label"></alias>
       <min value="0"></min>
@@ -68879,7 +69028,9 @@
       <path value="Questionnaire.item.enableWhen"></path>
       <short value="Only allow data when"></short>
       <definition value="A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true."></definition>
-      <comment value="If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat &quot;enableWhen&quot;s as being joined by an &quot;or&quot; clause.  This element is a modifier because if enableWhen is present for an item, &quot;required&quot; is ignored unless one of the enableWhen conditions is met."></comment>
+      <comment value="If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat &quot;enableWhen&quot;s as being joined by an &quot;or&quot; clause.
+
+This element is a modifier because if enableWhen is present for an item, &quot;required&quot; is ignored unless one of the enableWhen conditions is met."></comment>
       <requirements value="Allows questionnaires to adapt based on answers to other questions. E.g. If physical gender is specified as a male, no need to capture pregnancy history.  Also allows conditional display of instructions or groups of questions."></requirements>
       <min value="0"></min>
       <max value="*"></max>
@@ -69025,7 +69176,11 @@
       <path value="Questionnaire.item.enableWhen.answer[x]"></path>
       <short value="Value question must have"></short>
       <definition value="An answer that the referenced question must match in order for the item to be enabled."></definition>
-      <comment value="Multiple answers are treated as &quot;or&quot;.  E.g. Enable if question 1 = A, C or E.    Components not specified in the answer do not need to match.  For example, if enableWhen specifies code + system for a Coding, it is ok if the answer has a &quot;display&quot; element.  I.e. treat the answer as a 'pattern'.  The dataType of this element must be the same as the data type of the question being referenced."></comment>
+      <comment value="Multiple answers are treated as &quot;or&quot;.  E.g. Enable if question 1 = A, C or E.  
+
+Components not specified in the answer do not need to match.  For example, if enableWhen specifies code + system for a Coding, it is ok if the answer has a &quot;display&quot; element.  I.e. treat the answer as a 'pattern'.
+
+The dataType of this element must be the same as the data type of the question being referenced."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <base>
@@ -69381,7 +69536,9 @@
       <path value="Questionnaire.item.initial[x]"></path>
       <short value="Default value when item is first rendered"></short>
       <definition value="The value that should be defaulted when initially rendering the questionnaire for user input."></definition>
-      <comment value="The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that default values can influence results.  The data type of initial[x] must agree with the item.type."></comment>
+      <comment value="The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that default values can influence results.
+
+The data type of initial[x] must agree with the item.type."></comment>
       <requirements value="In some workflows, having defaults saves time."></requirements>
       <min value="0"></min>
       <max value="1"></max>
diff --git a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-resources.xml b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-resources.xml
index 09b962bb400..095072184c2 100644
--- a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-resources.xml
+++ b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-resources.xml
@@ -1,7 +1,7 @@
 <Bundle xmlns="http://hl7.org/fhir">
  <id value="resources"></id>
  <meta>
-  <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+  <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
  </meta>
  <type value="collection"></type>
  <entry>
@@ -10,14 +10,14 @@
    <CapabilityStatement xmlns="http://hl7.org/fhir">
     <id value="base"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/CapabilityStatement/base"></url>
-    <version value="3.0.1-11918"></version>
+    <version value="3.0.2-11200"></version>
     <name value="Base FHIR Capability Statement (Full)"></name>
     <status value="draft"></status>
     <experimental value="true"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="FHIR Project Team"></publisher>
     <contact>
      <telecom>
@@ -30,7 +30,7 @@
     <software>
      <name value="Insert your softwware name here..."></name>
     </software>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <acceptUnknown value="both"></acceptUnknown>
     <format value="xml"></format>
     <format value="json"></format>
@@ -14847,14 +14847,14 @@ Requires the near-distance parameter to be provided also"></documentation>
    <CapabilityStatement xmlns="http://hl7.org/fhir">
     <id value="base2"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/CapabilityStatement/base2"></url>
-    <version value="3.0.1-11918"></version>
+    <version value="3.0.2-11200"></version>
     <name value="Base FHIR Capability Statement (Empty)"></name>
     <status value="draft"></status>
     <experimental value="true"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="FHIR Project Team"></publisher>
     <contact>
      <telecom>
@@ -14867,7 +14867,7 @@ Requires the near-distance parameter to be provided also"></documentation>
     <software>
      <name value="Insert your softwware name here..."></name>
     </software>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <acceptUnknown value="no"></acceptUnknown>
     <format value="xml"></format>
     <format value="json"></format>
@@ -14903,13 +14903,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <CompartmentDefinition xmlns="http://hl7.org/fhir">
     <id value="device"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/CompartmentDefinition/device"></url>
     <name value="Base FHIR compartment definition for Device"></name>
     <status value="draft"></status>
     <experimental value="true"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="FHIR Project Team"></publisher>
     <contact>
      <telecom>
@@ -15321,13 +15321,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <CompartmentDefinition xmlns="http://hl7.org/fhir">
     <id value="encounter"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/CompartmentDefinition/encounter"></url>
     <name value="Base FHIR compartment definition for Encounter"></name>
     <status value="draft"></status>
     <experimental value="true"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="FHIR Project Team"></publisher>
     <contact>
      <telecom>
@@ -15716,13 +15716,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <CompartmentDefinition xmlns="http://hl7.org/fhir">
     <id value="patient"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/CompartmentDefinition/patient"></url>
     <name value="Base FHIR compartment definition for Patient"></name>
     <status value="draft"></status>
     <experimental value="true"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="FHIR Project Team"></publisher>
     <contact>
      <telecom>
@@ -16193,13 +16193,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <CompartmentDefinition xmlns="http://hl7.org/fhir">
     <id value="practitioner"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/CompartmentDefinition/practitioner"></url>
     <name value="Base FHIR compartment definition for Practitioner"></name>
     <status value="draft"></status>
     <experimental value="true"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="FHIR Project Team"></publisher>
     <contact>
      <telecom>
@@ -16659,13 +16659,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <CompartmentDefinition xmlns="http://hl7.org/fhir">
     <id value="relatedPerson"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/CompartmentDefinition/relatedPerson"></url>
     <name value="Base FHIR compartment definition for RelatedPerson"></name>
     <status value="draft"></status>
     <experimental value="true"></experimental>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="FHIR Project Team"></publisher>
     <contact>
      <telecom>
@@ -17072,13 +17072,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ActivityDefinition-apply"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ActivityDefinition-apply"></url>
     <name value="Apply"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17198,13 +17198,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ActivityDefinition-data-requirements"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ActivityDefinition-data-requirements"></url>
     <name value="Data Requirements"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17240,13 +17240,13 @@ Requires the near-distance parameter to be provided also"></documentation>
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="CapabilityStatement-conforms"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/CapabilityStatement-conforms"></url>
     <name value="Test if a server implements a client's required operations"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17326,13 +17326,13 @@ If the capability statements can be successfully compared, then the return value
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="CapabilityStatement-implements"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/CapabilityStatement-implements"></url>
     <name value="Test if a server implements a client's required operations"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17401,13 +17401,13 @@ If the capability statements match by these rules, then the return value is a 20
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="CapabilityStatement-subset"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/CapabilityStatement-subset"></url>
     <name value="Fetch a subset of the CapabilityStatement resource"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17458,13 +17458,13 @@ If the capability statements match by these rules, then the return value is a 20
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="CodeSystem-compose"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/CodeSystem-compose"></url>
     <name value="Code Composition based on supplied properties"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17653,13 +17653,13 @@ The compose operation is still preliminary. The interface can be expected to cha
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="CodeSystem-lookup"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/CodeSystem-lookup"></url>
     <name value="Concept Look Up &amp; Decomposition"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17860,13 +17860,13 @@ The compose operation is still preliminary. The interface can be expected to cha
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="CodeSystem-subsumes"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/CodeSystem-subsumes"></url>
     <name value="Subsumption Testing"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17949,13 +17949,13 @@ The compose operation is still preliminary. The interface can be expected to cha
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Composition-document"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Composition-document"></url>
     <name value="Generate a Document"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -17991,13 +17991,13 @@ The compose operation is still preliminary. The interface can be expected to cha
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ConceptMap-closure"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ConceptMap-closure"></url>
     <name value="Closure Table Maintenance"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18056,13 +18056,13 @@ The compose operation is still preliminary. The interface can be expected to cha
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ConceptMap-translate"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ConceptMap-translate"></url>
     <name value="Concept Translation"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18258,13 +18258,13 @@ The operation returns a set of parameters including a 'result' for whether there
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Encounter-everything"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Encounter-everything"></url>
     <name value="Fetch Encounter Record"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18300,13 +18300,13 @@ The operation returns a set of parameters including a 'result' for whether there
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Library-data-requirements"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Library-data-requirements"></url>
     <name value="Data Requirements"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18350,13 +18350,13 @@ The operation returns a set of parameters including a 'result' for whether there
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="List-find"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/List-find"></url>
     <name value="Find a functional list"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18400,13 +18400,13 @@ The operation returns a set of parameters including a 'result' for whether there
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Measure-data-requirements"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Measure-data-requirements"></url>
     <name value="Data Requirements"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18458,13 +18458,13 @@ The operation returns a set of parameters including a 'result' for whether there
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Measure-evaluate-measure"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Measure-evaluate-measure"></url>
     <name value="Evaluate Measure"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18565,13 +18565,13 @@ The operation returns a set of parameters including a 'result' for whether there
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="MessageHeader-process-message"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message"></url>
     <name value="Process Message"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18631,13 +18631,13 @@ The operation returns a set of parameters including a 'result' for whether there
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Observation-lastn"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Observation-lastn"></url>
     <name value="Last N Observations Query"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18696,13 +18696,13 @@ This operation cannot be performed on observations that the user is not authoriz
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Observation-stats"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Observation-stats"></url>
     <name value="Observation Statistics"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18854,13 +18854,13 @@ The client can request that all the observations on which the statistics are bas
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Patient-everything"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Patient-everything"></url>
     <name value="Fetch Patient Record"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18917,13 +18917,13 @@ It is assumed that the server has identified and secured the context appropriate
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Patient-match"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Patient-match"></url>
     <name value="Find patient matches using MPI based logic"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -18987,13 +18987,13 @@ If the operation was unsuccessful, then an OperationOutcome may be returned alon
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="PlanDefinition-apply"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/PlanDefinition-apply"></url>
     <name value="Apply"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19113,13 +19113,13 @@ If the operation was unsuccessful, then an OperationOutcome may be returned alon
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="PlanDefinition-data-requirements"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/PlanDefinition-data-requirements"></url>
     <name value="Data Requirements"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19155,13 +19155,13 @@ If the operation was unsuccessful, then an OperationOutcome may be returned alon
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Questionnaire-populate"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Questionnaire-populate"></url>
     <name value="Populate Questionnaire"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19272,13 +19272,13 @@ Invoking this operation with the ''content'' parameter may involve the disclosur
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Questionnaire-populatehtml"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Questionnaire-populatehtml"></url>
     <name value="Generate HTML for Questionnaire"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19379,13 +19379,13 @@ Invoking this operation with the ''content'' parameter may involve the disclosur
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Questionnaire-populatelink"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Questionnaire-populatelink"></url>
     <name value="Generate a link to a Questionnaire completion webpage"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19486,13 +19486,13 @@ Invoking this operation with the ''content'' parameter may involve the disclosur
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Resource-meta"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Resource-meta"></url>
     <name value="Access a list of profiles, tags, and security labels"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19532,13 +19532,13 @@ Invoking this operation with the ''content'' parameter may involve the disclosur
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Resource-meta-add"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Resource-meta-add"></url>
     <name value="Add profiles, tags, and security labels to a resource"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19582,13 +19582,13 @@ Invoking this operation with the ''content'' parameter may involve the disclosur
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Resource-meta-delete"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Resource-meta-delete"></url>
     <name value="Delete profiles, tags, and security labels for a resource"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19632,13 +19632,13 @@ Invoking this operation with the ''content'' parameter may involve the disclosur
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="Resource-validate"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/Resource-validate"></url>
     <name value="Validate a resource"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19713,13 +19713,13 @@ This operation returns a 200 OK whether or not the resource is valid. A 4xx or 5
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ServiceDefinition-data-requirements"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ServiceDefinition-data-requirements"></url>
     <name value="Data Requirements"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19763,13 +19763,13 @@ This operation returns a 200 OK whether or not the resource is valid. A 4xx or 5
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ServiceDefinition-evaluate"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ServiceDefinition-evaluate"></url>
     <name value="Evaluate"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -19952,13 +19952,13 @@ This operation returns a 200 OK whether or not the resource is valid. A 4xx or 5
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="StructureDefinition-questionnaire"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/StructureDefinition-questionnaire"></url>
     <name value="Build Questionnaire"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -20027,13 +20027,13 @@ This operation returns a 200 OK whether or not the resource is valid. A 4xx or 5
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="StructureMap-transform"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/StructureMap-transform"></url>
     <name value="Model Instance Transformation"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -20085,13 +20085,13 @@ This operation returns a 200 OK whether or not the resource is valid. A 4xx or 5
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ValueSet-expand"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ValueSet-expand"></url>
     <name value="Value Set Expansion"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -20265,13 +20265,13 @@ When a server cannot correctly expand a value set because it does not fully unde
    <OperationDefinition xmlns="http://hl7.org/fhir">
     <id value="ValueSet-validate-code"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/OperationDefinition/ValueSet-validate-code"></url>
     <name value="Value Set based Validation"></name>
     <status value="draft"></status>
     <kind value="operation"></kind>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 (FHIR Project)"></publisher>
     <contact>
      <telecom>
@@ -20418,7 +20418,7 @@ When a server cannot correctly expand a value set because it does not fully unde
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Resource"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -20429,7 +20429,7 @@ When a server cannot correctly expand a value set because it does not fully unde
     <url value="http://hl7.org/fhir/StructureDefinition/Resource"></url>
     <name value="Resource"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -20444,7 +20444,7 @@ When a server cannot correctly expand a value set because it does not fully unde
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Resource Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -20622,7 +20622,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Account"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -20633,7 +20633,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Account"></url>
     <name value="Account"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -20648,7 +20648,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Account Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -21781,7 +21781,7 @@ A coverage may only be resposible for specific types of charges, and the sequenc
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ActivityDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -21792,7 +21792,7 @@ A coverage may only be resposible for specific types of charges, and the sequenc
     <url value="http://hl7.org/fhir/StructureDefinition/ActivityDefinition"></url>
     <name value="ActivityDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -21807,7 +21807,7 @@ A coverage may only be resposible for specific types of charges, and the sequenc
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ActivityDefinition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -23996,7 +23996,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="AdverseEvent"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -24007,7 +24007,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/AdverseEvent"></url>
     <name value="AdverseEvent"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Regulated Clinical Research Information Management)"></publisher>
     <contact>
      <telecom>
@@ -24022,7 +24022,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for AdverseEvent Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -25224,7 +25224,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="AllergyIntolerance"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -25235,7 +25235,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"></url>
     <name value="AllergyIntolerance"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -25251,7 +25251,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for AllergyIntolerance Resource"></description>
     <purpose value="To record a clinical assessment of a propensity, or potential risk to an individual, of an adverse reaction upon future exposure to the specified substance, or class of substance."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -26794,7 +26794,7 @@ Systems that capture a severity at the condition level are actually representing
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Appointment"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -26805,7 +26805,7 @@ Systems that capture a severity at the condition level are actually representing
     <url value="http://hl7.org/fhir/StructureDefinition/Appointment"></url>
     <name value="Appointment"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -26820,7 +26820,7 @@ Systems that capture a severity at the condition level are actually representing
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Appointment Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -28422,7 +28422,7 @@ This element is labeled as a modifier because the status contains the code enter
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="AppointmentResponse"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -28433,7 +28433,7 @@ This element is labeled as a modifier because the status contains the code enter
     <url value="http://hl7.org/fhir/StructureDefinition/AppointmentResponse"></url>
     <name value="AppointmentResponse"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -28448,7 +28448,7 @@ This element is labeled as a modifier because the status contains the code enter
      </telecom>
     </contact>
     <description value="Base StructureDefinition for AppointmentResponse Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -29163,7 +29163,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="AuditEvent"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -29174,7 +29174,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/AuditEvent"></url>
     <name value="AuditEvent"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Security)"></publisher>
     <contact>
      <telecom>
@@ -29189,7 +29189,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for AuditEvent Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -32220,7 +32220,7 @@ For example, an activity may be initiated by one user for other users or involve
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Basic"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -32231,7 +32231,7 @@ For example, an activity may be initiated by one user for other users or involve
     <url value="http://hl7.org/fhir/StructureDefinition/Basic"></url>
     <name value="Basic"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -32247,7 +32247,7 @@ For example, an activity may be initiated by one user for other users or involve
     </contact>
     <description value="Base StructureDefinition for Basic Resource"></description>
     <purpose value="Need some way to safely (without breaking interoperability) allow implementers to exchange content not supported by the initial set of declared resources."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -32776,7 +32776,7 @@ This element is labeled as a modifier because the it defines the meaning of the
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Binary"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -32787,7 +32787,7 @@ This element is labeled as a modifier because the it defines the meaning of the
     <url value="http://hl7.org/fhir/StructureDefinition/Binary"></url>
     <name value="Binary"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -32803,7 +32803,7 @@ This element is labeled as a modifier because the it defines the meaning of the
     </contact>
     <description value="Base StructureDefinition for Binary Resource"></description>
     <purpose value="There are situations where it is useful or required to handle pure binary content using the same framework as other resources."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -33045,7 +33045,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="BodySite"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -33056,7 +33056,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/BodySite"></url>
     <name value="BodySite"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -33071,7 +33071,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for BodySite Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -33736,7 +33736,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Bundle"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -33747,7 +33747,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Bundle"></url>
     <name value="Bundle"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -33762,7 +33762,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Bundle Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -35114,7 +35114,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="CapabilityStatement"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -35125,7 +35125,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/CapabilityStatement"></url>
     <name value="CapabilityStatement"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -35140,7 +35140,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for CapabilityStatement Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -39337,7 +39337,7 @@ Applications are recommended to accept unknown extensions and elements ('both'),
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="CarePlan"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -39348,7 +39348,7 @@ Applications are recommended to accept unknown extensions and elements ('both'),
     <url value="http://hl7.org/fhir/StructureDefinition/CarePlan"></url>
     <name value="CarePlan"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -39363,7 +39363,7 @@ Applications are recommended to accept unknown extensions and elements ('both'),
      </telecom>
     </contact>
     <description value="Base StructureDefinition for CarePlan Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -41886,7 +41886,7 @@ The unknown code is not to be used to convey other statuses.  The unknown code s
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="CareTeam"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -41897,7 +41897,7 @@ The unknown code is not to be used to convey other statuses.  The unknown code s
     <url value="http://hl7.org/fhir/StructureDefinition/CareTeam"></url>
     <name value="CareTeam"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -41912,7 +41912,7 @@ The unknown code is not to be used to convey other statuses.  The unknown code s
      </telecom>
     </contact>
     <description value="Base StructureDefinition for CareTeam Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -42907,7 +42907,7 @@ Member is optional because some participants may be known only by their role, pa
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ChargeItem"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -42918,7 +42918,7 @@ Member is optional because some participants may be known only by their role, pa
     <url value="http://hl7.org/fhir/StructureDefinition/ChargeItem"></url>
     <name value="ChargeItem"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -42933,7 +42933,7 @@ Member is optional because some participants may be known only by their role, pa
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ChargeItem Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -44603,7 +44603,7 @@ This element is labeled as a modifier because the status contains the code enter
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Claim"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -44614,7 +44614,7 @@ This element is labeled as a modifier because the status contains the code enter
     <url value="http://hl7.org/fhir/StructureDefinition/Claim"></url>
     <name value="Claim"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -44629,7 +44629,7 @@ This element is labeled as a modifier because the status contains the code enter
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Claim Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -49172,7 +49172,7 @@ see information codes"></short>
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ClaimResponse"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -49183,7 +49183,7 @@ see information codes"></short>
     <url value="http://hl7.org/fhir/StructureDefinition/ClaimResponse"></url>
     <name value="ClaimResponse"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -49198,7 +49198,7 @@ see information codes"></short>
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ClaimResponse Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -52437,7 +52437,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ClinicalImpression"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -52448,7 +52448,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ClinicalImpression"></url>
     <name value="ClinicalImpression"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -52463,7 +52463,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ClinicalImpression Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -53777,7 +53777,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="CodeSystem"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -53788,7 +53788,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/CodeSystem"></url>
     <name value="CodeSystem"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Vocabulary)"></publisher>
     <contact>
      <telecom>
@@ -53803,7 +53803,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for CodeSystem Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -55822,7 +55822,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Communication"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -55833,7 +55833,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Communication"></url>
     <name value="Communication"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -55848,7 +55848,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Communication Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -57161,7 +57161,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="CommunicationRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -57172,7 +57172,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/CommunicationRequest"></url>
     <name value="CommunicationRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -57187,7 +57187,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for CommunicationRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -58787,7 +58787,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="CompartmentDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -58798,7 +58798,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/CompartmentDefinition"></url>
     <name value="CompartmentDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -58813,7 +58813,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for CompartmentDefinition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -59779,7 +59779,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Composition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -59790,7 +59790,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Composition"></url>
     <name value="Composition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Structured Documents)"></publisher>
     <contact>
      <telecom>
@@ -59806,7 +59806,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     </contact>
     <description value="Base StructureDefinition for Composition Resource"></description>
     <purpose value="To support documents, and also to capture the EN13606 notion of an attested commit to the patient EHR, and to allow a set of disparate resources at the information/engineering level to be gathered into a clinical statement."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -62060,7 +62060,7 @@ This element is labeled as a modifier because highly confidential documents must
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ConceptMap"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -62071,7 +62071,7 @@ This element is labeled as a modifier because highly confidential documents must
     <url value="http://hl7.org/fhir/StructureDefinition/ConceptMap"></url>
     <name value="ConceptMap"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Vocabulary)"></publisher>
     <contact>
      <telecom>
@@ -62086,7 +62086,7 @@ This element is labeled as a modifier because highly confidential documents must
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ConceptMap Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -63955,7 +63955,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Condition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -63966,7 +63966,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Condition"></url>
     <name value="Condition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -63981,7 +63981,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Condition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="sct-concept"></identity>
      <uri value="http://snomed.info/conceptdomain"></uri>
@@ -64056,7 +64056,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
        <severity value="error"></severity>
        <human value="If condition is abated, then clinicalStatus must be either inactive, resolved, or remission"></human>
        <expression value="abatement.empty() or (abatement as boolean).not()  or clinicalStatus='resolved' or clinicalStatus='remission' or clinicalStatus='inactive'"></expression>
-       <xpath value="not(f:abatementBoolean/@value=true() or (not(exists(f:abatementBoolean)) and exists(*[starts-with(local-name(.), 'abatement')])) or f:clinicalStatus/@value=('resolved', 'remission', 'inactive'))"></xpath>
+       <xpath value="not(exists(*[starts-with(local-name(.), 'abatement')])) or f:clinicalStatus/@value=('resolved', 'remission', 'inactive')"></xpath>
       </constraint>
       <constraint>
        <key value="con-3"></key>
@@ -65073,7 +65073,7 @@ OR &lt; 272379006 |Event|"></map>
        <severity value="error"></severity>
        <human value="If condition is abated, then clinicalStatus must be either inactive, resolved, or remission"></human>
        <expression value="abatement.empty() or (abatement as boolean).not()  or clinicalStatus='resolved' or clinicalStatus='remission' or clinicalStatus='inactive'"></expression>
-       <xpath value="not(f:abatementBoolean/@value=true() or (not(exists(f:abatementBoolean)) and exists(*[starts-with(local-name(.), 'abatement')])) or f:clinicalStatus/@value=('resolved', 'remission', 'inactive'))"></xpath>
+       <xpath value="not(exists(*[starts-with(local-name(.), 'abatement')])) or f:clinicalStatus/@value=('resolved', 'remission', 'inactive')"></xpath>
       </constraint>
       <constraint>
        <key value="con-3"></key>
@@ -65753,7 +65753,7 @@ OR &lt; 272379006 |Event|"></map>
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Consent"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -65764,7 +65764,7 @@ OR &lt; 272379006 |Event|"></map>
     <url value="http://hl7.org/fhir/StructureDefinition/Consent"></url>
     <name value="Consent"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Community Based Collaborative Care)"></publisher>
     <contact>
      <telecom>
@@ -65779,7 +65779,7 @@ OR &lt; 272379006 |Event|"></map>
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Consent Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -68075,7 +68075,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Contract"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -68086,7 +68086,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Contract"></url>
     <name value="Contract"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -68101,7 +68101,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Contract Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -71518,7 +71518,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Coverage"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -71529,7 +71529,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Coverage"></url>
     <name value="Coverage"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -71545,7 +71545,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for Coverage Resource"></description>
     <purpose value="Health care programs and insurers are significant payors of health service costs."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -73185,7 +73185,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DataElement"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -73196,7 +73196,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/DataElement"></url>
     <name value="DataElement"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -73211,7 +73211,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DataElement Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="dex"></identity>
      <uri value="http://wiki.ihe.net/index.php?title=Data_Element_Exchange"></uri>
@@ -74690,7 +74690,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DetectedIssue"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -74701,7 +74701,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/DetectedIssue"></url>
     <name value="DetectedIssue"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -74716,7 +74716,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DetectedIssue Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -75798,7 +75798,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Device"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -75809,7 +75809,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Device"></url>
     <name value="Device"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -75825,7 +75825,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for Device Resource"></description>
     <purpose value="Allows institutions to track their devices."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -77246,7 +77246,7 @@ http://hl7.org/fhir/NamingSystem/iccbba-other"></map>
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DeviceComponent"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -77257,7 +77257,7 @@ http://hl7.org/fhir/NamingSystem/iccbba-other"></map>
     <url value="http://hl7.org/fhir/StructureDefinition/DeviceComponent"></url>
     <name value="DeviceComponent"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Health Care Devices)"></publisher>
     <contact>
      <telecom>
@@ -77272,7 +77272,7 @@ http://hl7.org/fhir/NamingSystem/iccbba-other"></map>
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DeviceComponent Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -78066,7 +78066,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DeviceMetric"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -78077,7 +78077,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/DeviceMetric"></url>
     <name value="DeviceMetric"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Health Care Devices)"></publisher>
     <contact>
      <telecom>
@@ -78092,7 +78092,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DeviceMetric Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -78894,7 +78894,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DeviceRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -78905,7 +78905,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/DeviceRequest"></url>
     <name value="DeviceRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -78920,7 +78920,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DeviceRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -80620,7 +80620,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DeviceUseStatement"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -80631,7 +80631,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/DeviceUseStatement"></url>
     <name value="DeviceUseStatement"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -80646,7 +80646,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DeviceUseStatement Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="quick"></identity>
      <uri value="http://wiki.siframework.org/CQF"></uri>
@@ -81400,7 +81400,7 @@ This element is labeled as a modifier because the status contains the codes that
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DiagnosticReport"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -81411,7 +81411,7 @@ This element is labeled as a modifier because the status contains the codes that
     <url value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"></url>
     <name value="DiagnosticReport"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -81427,7 +81427,7 @@ This element is labeled as a modifier because the status contains the codes that
     </contact>
     <description value="Base StructureDefinition for DiagnosticReport Resource"></description>
     <purpose value="To support reporting for any diagnostic report into a clinical data repository."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -83136,7 +83136,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DocumentManifest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -83147,7 +83147,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/DocumentManifest"></url>
     <name value="DocumentManifest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Structured Documents)"></publisher>
     <contact>
      <telecom>
@@ -83162,7 +83162,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DocumentManifest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -84355,7 +84355,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DocumentReference"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -84366,7 +84366,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/DocumentReference"></url>
     <name value="DocumentReference"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Structured Documents)"></publisher>
     <contact>
      <telecom>
@@ -84381,7 +84381,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DocumentReference Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -86590,7 +86590,7 @@ This element is labeled as a modifier because the status contains the codes that
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DomainResource"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -86601,7 +86601,7 @@ This element is labeled as a modifier because the status contains the codes that
     <url value="http://hl7.org/fhir/StructureDefinition/DomainResource"></url>
     <name value="DomainResource"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -86616,7 +86616,7 @@ This element is labeled as a modifier because the status contains the codes that
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DomainResource Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -86983,7 +86983,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="EligibilityRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -86994,7 +86994,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/EligibilityRequest"></url>
     <name value="EligibilityRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -87009,7 +87009,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for EligibilityRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -87882,7 +87882,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="EligibilityResponse"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -87893,7 +87893,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/EligibilityResponse"></url>
     <name value="EligibilityResponse"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -87908,7 +87908,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for EligibilityResponse Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -89463,7 +89463,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Encounter"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -89474,7 +89474,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Encounter"></url>
     <name value="Encounter"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -89489,7 +89489,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Encounter Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -92199,7 +92199,7 @@ This would be used for a case where an admission starts of as an emergency encou
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Endpoint"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -92210,7 +92210,7 @@ This would be used for a case where an admission starts of as an emergency encou
     <url value="http://hl7.org/fhir/StructureDefinition/Endpoint"></url>
     <name value="Endpoint"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -92225,7 +92225,7 @@ This would be used for a case where an admission starts of as an emergency encou
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Endpoint Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -92968,7 +92968,7 @@ and not &quot;https://pacs.hospital.org/wado-rs/studies/1.2.250.1.59.40211.12345
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="EnrollmentRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -92979,7 +92979,7 @@ and not &quot;https://pacs.hospital.org/wado-rs/studies/1.2.250.1.59.40211.12345
     <url value="http://hl7.org/fhir/StructureDefinition/EnrollmentRequest"></url>
     <name value="EnrollmentRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -92994,7 +92994,7 @@ and not &quot;https://pacs.hospital.org/wado-rs/studies/1.2.250.1.59.40211.12345
      </telecom>
     </contact>
     <description value="Base StructureDefinition for EnrollmentRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -93480,7 +93480,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="EnrollmentResponse"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -93491,7 +93491,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/EnrollmentResponse"></url>
     <name value="EnrollmentResponse"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -93506,7 +93506,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for EnrollmentResponse Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -94034,7 +94034,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="EpisodeOfCare"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -94045,7 +94045,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/EpisodeOfCare"></url>
     <name value="EpisodeOfCare"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -94060,7 +94060,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for EpisodeOfCare Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -95009,7 +95009,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ExpansionProfile"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -95020,7 +95020,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"></url>
     <name value="ExpansionProfile"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Vocabulary)"></publisher>
     <contact>
      <telecom>
@@ -95035,7 +95035,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ExpansionProfile Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -97058,7 +97058,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ExplanationOfBenefit"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -97069,7 +97069,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/ExplanationOfBenefit"></url>
     <name value="ExplanationOfBenefit"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -97084,7 +97084,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ExplanationOfBenefit Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -103977,7 +103977,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="FamilyMemberHistory"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -103988,7 +103988,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/FamilyMemberHistory"></url>
     <name value="FamilyMemberHistory"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -104003,7 +104003,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for FamilyMemberHistory Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -105384,7 +105384,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Flag"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -105395,7 +105395,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Flag"></url>
     <name value="Flag"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -105410,7 +105410,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Flag Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -106133,7 +106133,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Goal"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -106144,7 +106144,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Goal"></url>
     <name value="Goal"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -106159,7 +106159,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Goal Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -107406,7 +107406,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="GraphDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -107417,7 +107417,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/GraphDefinition"></url>
     <name value="GraphDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -107432,7 +107432,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for GraphDefinition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -108900,7 +108900,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Group"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -108911,7 +108911,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Group"></url>
     <name value="Group"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -108926,7 +108926,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Group Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -109999,7 +109999,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="GuidanceResponse"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -110010,7 +110010,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/GuidanceResponse"></url>
     <name value="GuidanceResponse"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -110025,7 +110025,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for GuidanceResponse Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -110706,7 +110706,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="HealthcareService"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -110717,7 +110717,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/HealthcareService"></url>
     <name value="HealthcareService"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -110732,7 +110732,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for HealthcareService Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -112241,7 +112241,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ImagingManifest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -112252,7 +112252,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ImagingManifest"></url>
     <name value="ImagingManifest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Imaging Integration)"></publisher>
     <contact>
      <telecom>
@@ -112267,7 +112267,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ImagingManifest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -113476,7 +113476,7 @@ The value may be derived from the DICOM Standard Part 16, CID-7010 descriptions
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ImagingStudy"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -113487,7 +113487,7 @@ The value may be derived from the DICOM Standard Part 16, CID-7010 descriptions
     <url value="http://hl7.org/fhir/StructureDefinition/ImagingStudy"></url>
     <name value="ImagingStudy"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Imaging Integration)"></publisher>
     <contact>
      <telecom>
@@ -113502,7 +113502,7 @@ The value may be derived from the DICOM Standard Part 16, CID-7010 descriptions
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ImagingStudy Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -115630,7 +115630,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Immunization"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -115641,7 +115641,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Immunization"></url>
     <name value="Immunization"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Public Health and Emergency Response)"></publisher>
     <contact>
      <telecom>
@@ -115656,7 +115656,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Immunization Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -117972,7 +117972,7 @@ This element is labeled as a modifier because the status contains codes that mar
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ImmunizationRecommendation"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -117983,7 +117983,7 @@ This element is labeled as a modifier because the status contains codes that mar
     <url value="http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation"></url>
     <name value="ImmunizationRecommendation"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Public Health and Emergency Response)"></publisher>
     <contact>
      <telecom>
@@ -117998,7 +117998,7 @@ This element is labeled as a modifier because the status contains codes that mar
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ImmunizationRecommendation Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -119279,7 +119279,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ImplementationGuide"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -119290,7 +119290,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ImplementationGuide"></url>
     <name value="ImplementationGuide"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -119306,7 +119306,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for ImplementationGuide Resource"></description>
     <purpose value="An implementation guide is able to define default profiles that must apply to any use of a resource, so validation services may need to take one or more implementation guide resources when validating."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -119777,7 +119777,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      <element id="ImplementationGuide.fhirVersion">
       <path value="ImplementationGuide.fhirVersion"></path>
       <short value="FHIR Version this Implementation Guide targets"></short>
-      <definition value="The version of the FHIR specification on which this ImplementationGuide is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.1 for this version."></definition>
+      <definition value="The version of the FHIR specification on which this ImplementationGuide is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.2 for this version."></definition>
       <comment value="An Implementation Guide should specify the target it applies to, as ImplementationGuides are rarely valid across multiple versions of FHIR."></comment>
       <min value="0"></min>
       <max value="1"></max>
@@ -120737,7 +120737,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      <element id="ImplementationGuide.fhirVersion">
       <path value="ImplementationGuide.fhirVersion"></path>
       <short value="FHIR Version this Implementation Guide targets"></short>
-      <definition value="The version of the FHIR specification on which this ImplementationGuide is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.1 for this version."></definition>
+      <definition value="The version of the FHIR specification on which this ImplementationGuide is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.2 for this version."></definition>
       <comment value="An Implementation Guide should specify the target it applies to, as ImplementationGuides are rarely valid across multiple versions of FHIR."></comment>
       <min value="0"></min>
       <max value="1"></max>
@@ -121101,7 +121101,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Library"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -121112,7 +121112,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Library"></url>
     <name value="Library"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -121127,7 +121127,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Library Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -122453,7 +122453,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Linkage"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -122464,7 +122464,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Linkage"></url>
     <name value="Linkage"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -122479,7 +122479,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Linkage Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -123009,7 +123009,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="List"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -123020,7 +123020,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/List"></url>
     <name value="List"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -123035,7 +123035,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for List Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -124215,7 +124215,7 @@ This element is labeled as a modifier because it indicates that an item is (to b
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Location"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -124226,7 +124226,7 @@ This element is labeled as a modifier because it indicates that an item is (to b
     <url value="http://hl7.org/fhir/StructureDefinition/Location"></url>
     <name value="Location"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -124241,7 +124241,7 @@ This element is labeled as a modifier because it indicates that an item is (to b
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Location Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -125307,7 +125307,7 @@ For searching knowing previous names that the location was known by can be very
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Measure"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -125318,7 +125318,7 @@ For searching knowing previous names that the location was known by can be very
     <url value="http://hl7.org/fhir/StructureDefinition/Measure"></url>
     <name value="Measure"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Quality Information)"></publisher>
     <contact>
      <telecom>
@@ -125333,7 +125333,7 @@ For searching knowing previous names that the location was known by can be very
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Measure Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -127572,7 +127572,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MeasureReport"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -127583,7 +127583,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/MeasureReport"></url>
     <name value="MeasureReport"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Quality Information)"></publisher>
     <contact>
      <telecom>
@@ -127598,7 +127598,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for MeasureReport Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -129047,7 +129047,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Media"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -129058,7 +129058,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Media"></url>
     <name value="Media"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -129073,7 +129073,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Media Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -130326,7 +130326,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Medication"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -130337,7 +130337,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Medication"></url>
     <name value="Medication"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Pharmacy)"></publisher>
     <contact>
      <telecom>
@@ -130352,7 +130352,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Medication Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="script10.6"></identity>
      <uri value="http://ncpdp.org/SCRIPT10_6"></uri>
@@ -131807,7 +131807,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MedicationAdministration"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -131818,7 +131818,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/MedicationAdministration"></url>
     <name value="MedicationAdministration"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Pharmacy)"></publisher>
     <contact>
      <telecom>
@@ -131833,7 +131833,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for MedicationAdministration Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -133769,7 +133769,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MedicationDispense"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -133780,7 +133780,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/MedicationDispense"></url>
     <name value="MedicationDispense"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Pharmacy)"></publisher>
     <contact>
      <telecom>
@@ -133795,7 +133795,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for MedicationDispense Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -135584,7 +135584,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MedicationRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -135595,7 +135595,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/MedicationRequest"></url>
     <name value="MedicationRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Pharmacy)"></publisher>
     <contact>
      <telecom>
@@ -135610,7 +135610,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for MedicationRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -137951,7 +137951,7 @@ This element is labeled as a modifier because the intent alters when and how the
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MedicationStatement"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -137962,7 +137962,7 @@ This element is labeled as a modifier because the intent alters when and how the
     <url value="http://hl7.org/fhir/StructureDefinition/MedicationStatement"></url>
     <name value="MedicationStatement"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Pharmacy)"></publisher>
     <contact>
      <telecom>
@@ -137977,7 +137977,7 @@ This element is labeled as a modifier because the intent alters when and how the
      </telecom>
     </contact>
     <description value="Base StructureDefinition for MedicationStatement Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -139278,7 +139278,7 @@ This element is labeled as a modifier because the status contains codes that mar
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MessageDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -139289,7 +139289,7 @@ This element is labeled as a modifier because the status contains codes that mar
     <url value="http://hl7.org/fhir/StructureDefinition/MessageDefinition"></url>
     <name value="MessageDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Infrastructure And Messaging)"></publisher>
     <contact>
      <telecom>
@@ -139305,7 +139305,7 @@ This element is labeled as a modifier because the status contains codes that mar
     </contact>
     <description value="Base StructureDefinition for MessageDefinition Resource"></description>
     <purpose value="Allows messages to be defined once and re-used across systems."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -140688,7 +140688,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MessageHeader"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -140699,7 +140699,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/MessageHeader"></url>
     <name value="MessageHeader"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Infrastructure And Messaging)"></publisher>
     <contact>
      <telecom>
@@ -140715,7 +140715,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     </contact>
     <description value="Base StructureDefinition for MessageHeader Resource"></description>
     <purpose value="Many implementations are not prepared to use REST and need a messaging based infrastructure."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -142332,7 +142332,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="NamingSystem"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -142343,7 +142343,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/NamingSystem"></url>
     <name value="NamingSystem"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -142358,7 +142358,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for NamingSystem Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -143375,7 +143375,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="NutritionOrder"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -143386,7 +143386,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/NutritionOrder"></url>
     <name value="NutritionOrder"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -143401,7 +143401,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for NutritionOrder Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -145721,7 +145721,7 @@ This element is labeled as a modifier because the status contains codes that mar
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Observation"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -145732,7 +145732,7 @@ This element is labeled as a modifier because the status contains codes that mar
     <url value="http://hl7.org/fhir/StructureDefinition/Observation"></url>
     <name value="Observation"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -145748,7 +145748,7 @@ This element is labeled as a modifier because the status contains codes that mar
     </contact>
     <description value="Base StructureDefinition for Observation Resource"></description>
     <purpose value="Observations are a key aspect of healthcare.  This resource is used to capture those that do not require more sophisticated mechanisms."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -148546,7 +148546,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="OperationDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="4"></valueInteger>
@@ -148557,7 +148557,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/OperationDefinition"></url>
     <name value="OperationDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -148572,7 +148572,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for OperationDefinition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -150360,7 +150360,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="OperationOutcome"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -150371,7 +150371,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/OperationOutcome"></url>
     <name value="OperationOutcome"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -150386,7 +150386,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for OperationOutcome Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -151089,7 +151089,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Organization"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -151100,7 +151100,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Organization"></url>
     <name value="Organization"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -151115,7 +151115,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Organization Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -152213,7 +152213,7 @@ For searching knowing previous names that the organization was known by can be v
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Parameters"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -152224,7 +152224,7 @@ For searching knowing previous names that the organization was known by can be v
     <url value="http://hl7.org/fhir/StructureDefinition/Parameters"></url>
     <name value="Parameters"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -152239,7 +152239,7 @@ For searching knowing previous names that the organization was known by can be v
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Parameters Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -152827,7 +152827,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Patient"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -152838,7 +152838,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Patient"></url>
     <name value="Patient"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -152854,7 +152854,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for Patient Resource"></description>
     <purpose value="Tracking patient is the center of the healthcare process."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -155218,7 +155218,7 @@ This element is labelled as a modifier because it may not be the main Patient re
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="PaymentNotice"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -155229,7 +155229,7 @@ This element is labelled as a modifier because it may not be the main Patient re
     <url value="http://hl7.org/fhir/StructureDefinition/PaymentNotice"></url>
     <name value="PaymentNotice"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -155244,7 +155244,7 @@ This element is labelled as a modifier because it may not be the main Patient re
      </telecom>
     </contact>
     <description value="Base StructureDefinition for PaymentNotice Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -156014,7 +156014,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="PaymentReconciliation"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -156025,7 +156025,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/PaymentReconciliation"></url>
     <name value="PaymentReconciliation"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -156040,7 +156040,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for PaymentReconciliation Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -157215,7 +157215,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Person"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -157226,7 +157226,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Person"></url>
     <name value="Person"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -157242,7 +157242,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for Person Resource"></description>
     <purpose value="Need to track persons potentially across multiple roles."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -158121,7 +158121,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="PlanDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -158132,7 +158132,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/PlanDefinition"></url>
     <name value="PlanDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -158147,7 +158147,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for PlanDefinition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -161327,7 +161327,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Practitioner"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -161338,7 +161338,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Practitioner"></url>
     <name value="Practitioner"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -161354,7 +161354,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     </contact>
     <description value="Base StructureDefinition for Practitioner Resource"></description>
     <purpose value="Need to track doctors, staff, locums etc. for both healthcare practitioners, funders, etc."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -162424,7 +162424,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="PractitionerRole"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -162435,7 +162435,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/PractitionerRole"></url>
     <name value="PractitionerRole"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -162451,7 +162451,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for PractitionerRole Resource"></description>
     <purpose value="Need to track services that a healthcare provider is able to provide at an organization's location, and the services that they can perform there."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -163694,7 +163694,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Procedure"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -163705,7 +163705,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Procedure"></url>
     <name value="Procedure"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -163720,7 +163720,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Procedure Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -165684,7 +165684,7 @@ This element is labeled as a modifier because it indicates that a procedure didn
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ProcedureRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -165695,7 +165695,7 @@ This element is labeled as a modifier because it indicates that a procedure didn
     <url value="http://hl7.org/fhir/StructureDefinition/ProcedureRequest"></url>
     <name value="ProcedureRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -165710,7 +165710,7 @@ This element is labeled as a modifier because it indicates that a procedure didn
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ProcedureRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -166303,7 +166303,7 @@ This element is labeled as a modifier because the status contains codes that mar
         <valueString value="ProcedureRequestCode"></valueString>
        </extension>
        <strength value="example"></strength>
-       <description value="Codes for tests/services that can be performed by procedure or diagnostic services.  For laboratory, LOINC is  (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html)."></description>
+       <description value="Codes for tests/services that can be performed by procedure or diagnostic services.  For laboratory, LOINC is  (preferred)[http://hl7.org/fhir/STU3/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html)."></description>
        <valueSetReference>
         <reference value="http://hl7.org/fhir/ValueSet/procedure-code"></reference>
        </valueSetReference>
@@ -167319,7 +167319,7 @@ This element is labeled as a modifier because the status contains codes that mar
         <valueString value="ProcedureRequestCode"></valueString>
        </extension>
        <strength value="example"></strength>
-       <description value="Codes for tests/services that can be performed by procedure or diagnostic services.  For laboratory, LOINC is  (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html)."></description>
+       <description value="Codes for tests/services that can be performed by procedure or diagnostic services.  For laboratory, LOINC is  (preferred)[http://hl7.org/fhir/STU3/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here](valueset-diagnostic-requests.html)."></description>
        <valueSetReference>
         <reference value="http://hl7.org/fhir/ValueSet/procedure-code"></reference>
        </valueSetReference>
@@ -167923,7 +167923,7 @@ This element is labeled as a modifier because the status contains codes that mar
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ProcessRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -167934,7 +167934,7 @@ This element is labeled as a modifier because the status contains codes that mar
     <url value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"></url>
     <name value="ProcessRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -167949,7 +167949,7 @@ This element is labeled as a modifier because the status contains codes that mar
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ProcessRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -168805,7 +168805,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ProcessResponse"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -168816,7 +168816,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ProcessResponse"></url>
     <name value="ProcessResponse"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -168831,7 +168831,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ProcessResponse Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -169737,7 +169737,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Provenance"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -169748,7 +169748,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Provenance"></url>
     <name value="Provenance"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Security)"></publisher>
     <contact>
      <telecom>
@@ -169763,7 +169763,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Provenance Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -171164,7 +171164,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Questionnaire"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -171175,7 +171175,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Questionnaire"></url>
     <name value="Questionnaire"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -171191,7 +171191,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for Questionnaire Resource"></description>
     <purpose value="To support structured, hierarchical registration of data gathered using digital forms and other questionnaires.  Questionnaires provide greater control over presentation and allow capture of data in a domain-independent way (i.e. capturing information that would otherwise require multiple distinct types of resources)."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -173687,7 +173687,7 @@ The data type of initial[x] must agree with the item.type."></comment>
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="QuestionnaireResponse"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -173698,7 +173698,7 @@ The data type of initial[x] must agree with the item.type."></comment>
     <url value="http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse"></url>
     <name value="QuestionnaireResponse"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -173714,7 +173714,7 @@ The data type of initial[x] must agree with the item.type."></comment>
     </contact>
     <description value="Base StructureDefinition for QuestionnaireResponse Resource"></description>
     <purpose value="To support structured, hierarchical reporting of data gathered using digital forms and other questionnaires."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -175049,7 +175049,7 @@ There is no need for this element if the item pointed to by the linkId has a def
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ReferralRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -175060,7 +175060,7 @@ There is no need for this element if the item pointed to by the linkId has a def
     <url value="http://hl7.org/fhir/StructureDefinition/ReferralRequest"></url>
     <name value="ReferralRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Care)"></publisher>
     <contact>
      <telecom>
@@ -175075,7 +175075,7 @@ There is no need for this element if the item pointed to by the linkId has a def
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ReferralRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -176590,7 +176590,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="RelatedPerson"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -176601,7 +176601,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/RelatedPerson"></url>
     <name value="RelatedPerson"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -176617,7 +176617,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     </contact>
     <description value="Base StructureDefinition for RelatedPerson Resource"></description>
     <purpose value="Need to track persons related to the patient or the healthcare process."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -177393,7 +177393,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="RequestGroup"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -177404,7 +177404,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/RequestGroup"></url>
     <name value="RequestGroup"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -177419,7 +177419,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for RequestGroup Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -179342,7 +179342,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ResearchStudy"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -179353,7 +179353,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ResearchStudy"></url>
     <name value="ResearchStudy"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Regulated Clinical Research Information Management)"></publisher>
     <contact>
      <telecom>
@@ -179368,7 +179368,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ResearchStudy Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -180608,7 +180608,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ResearchSubject"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -180619,7 +180619,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ResearchSubject"></url>
     <name value="ResearchSubject"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Regulated Clinical Research Information Management)"></publisher>
     <contact>
      <telecom>
@@ -180634,7 +180634,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ResearchSubject Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -181170,7 +181170,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="RiskAssessment"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -181181,7 +181181,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/RiskAssessment"></url>
     <name value="RiskAssessment"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -181196,7 +181196,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for RiskAssessment Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -182561,7 +182561,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Schedule"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -182572,7 +182572,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Schedule"></url>
     <name value="Schedule"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -182587,7 +182587,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Schedule Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -183261,7 +183261,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="SearchParameter"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -183272,7 +183272,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/SearchParameter"></url>
     <name value="SearchParameter"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -183287,7 +183287,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for SearchParameter Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -184557,7 +184557,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Sequence"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -184568,7 +184568,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Sequence"></url>
     <name value="Sequence"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Genomics)"></publisher>
     <contact>
      <telecom>
@@ -184583,7 +184583,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Sequence Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
@@ -186448,7 +186448,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ServiceDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -186459,7 +186459,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/ServiceDefinition"></url>
     <name value="ServiceDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Clinical Decision Support)"></publisher>
     <contact>
      <telecom>
@@ -186474,7 +186474,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ServiceDefinition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -187683,7 +187683,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Slot"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -187694,7 +187694,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Slot"></url>
     <name value="Slot"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Patient Administration)"></publisher>
     <contact>
      <telecom>
@@ -187709,7 +187709,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Slot Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -188413,7 +188413,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Specimen"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -188424,7 +188424,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Specimen"></url>
     <name value="Specimen"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -188439,7 +188439,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Specimen Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -190156,7 +190156,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="StructureDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -190167,7 +190167,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/StructureDefinition"></url>
     <name value="StructureDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -190182,7 +190182,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for StructureDefinition Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -190258,7 +190258,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
        <requirements value="Because these 3 fields seem to be have overlapping meaning with the ones in the root of StructureDefinition"></requirements>
        <severity value="error"></severity>
        <human value="In any snapshot or differential, no label, code or requirements on the an element without a &quot;.&quot; in the path (e.g. the first element)"></human>
-       <expression value="children().element.first().label.empty() and children().element.first().code.empty() and children().element.first().requirements.empty()"></expression>
+       <expression value="children().element.where(path.contains('.').not()).label.empty() and children().element.where(path.contains('.').not()).code.empty() and children().element.where(path.contains('.').not()).requirements.empty()"></expression>
        <xpath value="not(exists(f:snapshot/f:element[not(contains(f:path/@value, '.')) and (f:label or f:code or f:requirements)])) and not(exists(f:differential/f:element[not(contains(f:path/@value, '.')) and (f:label or f:code or f:requirements)]))"></xpath>
       </constraint>
       <constraint>
@@ -190293,14 +190293,6 @@ This element is labelled as a modifier because the implicit rules may provide ad
        <expression value="differential.element.id.trace('ids').isDistinct()"></expression>
        <xpath value="count(*/f:element)=count(*/f:element/@id)"></xpath>
       </constraint>
-      <constraint>
-       <key value="sdf-12"></key>
-       <requirements value="Ensure that element.base appears with base or not"></requirements>
-       <severity value="error"></severity>
-       <human value="element.base cannot appear if there is no base on the structure definition"></human>
-       <expression value="snapshot.exists() implies (snapshot.element.base.exists() = baseDefinition.exists())"></expression>
-       <xpath value="f:baseDefinition or not(exists(f:snapshot/f:element/f:base) or exists(f:differential/f:element/f:base))"></xpath>
-      </constraint>
       <constraint>
        <key value="sdf-11"></key>
        <requirements value="Ensure that the type is not inconsistent with the other information in the structure"></requirements>
@@ -190858,7 +190850,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      <element id="StructureDefinition.fhirVersion">
       <path value="StructureDefinition.fhirVersion"></path>
       <short value="FHIR Version this StructureDefinition targets"></short>
-      <definition value="The version of the FHIR specification on which this StructureDefinition is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.1 for this version."></definition>
+      <definition value="The version of the FHIR specification on which this StructureDefinition is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.2 for this version."></definition>
       <comment value="A StructureDefinition does not need to specify the target it applies to,as StructureDefinitions will often be valid across multiple versions of FHIR. FHIR tooling can determine whether a StructureDefinition is consistent with a particular StructureDefinition if desired."></comment>
       <min value="0"></min>
       <max value="1"></max>
@@ -191133,7 +191125,6 @@ If the definition is a constraint, then it can not define new elements, it can o
       <type>
        <code value="code"></code>
       </type>
-      <condition value="sdf-12"></condition>
       <isSummary value="true"></isSummary>
       <binding>
        <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName">
@@ -191169,14 +191160,14 @@ If the definition is a constraint, then it can not define new elements, it can o
        <requirements value="No Type on the root element (snapshot)"></requirements>
        <severity value="error"></severity>
        <human value="The first element in a snapshot has no type"></human>
-       <expression value="element.first().type.empty()"></expression>
+       <expression value="kind!='logical' implies snapshot.element.first().type.empty()"></expression>
        <xpath value="not(f:element[1]/f:type)"></xpath>
       </constraint>
       <constraint>
        <key value="sdf-8"></key>
        <severity value="error"></severity>
        <human value="In any snapshot, all the elements must be in the specified type"></human>
-       <expression value="element.first().path = %resource.type and element.tail().all(path.startsWith(%resource.type&amp;'.'))"></expression>
+       <expression value="(%resource.kind = #39;.logical#39;. or element.first().path = %resource.type) and element.tail().all(path.startsWith(%resource.snapshot.element.first().path&amp;'.'))"></expression>
        <xpath value="f:element[1]/f:path/@value=parent::f:StructureDefinition/f:type/@value and count(f:element[position()!=1])=count(f:element[position()!=1][starts-with(f:path/@value, concat(ancestor::f:StructureDefinition/f:type/@value, '.'))])"></xpath>
       </constraint>
       <constraint>
@@ -191300,7 +191291,7 @@ If the definition is a constraint, then it can not define new elements, it can o
        <requirements value="no slicing on root"></requirements>
        <severity value="error"></severity>
        <human value="No slicing on the root element"></human>
-       <expression value="element.first().slicing.empty()"></expression>
+       <expression value="element.where(path.contains('.').not()).slicing.empty()"></expression>
        <xpath value="not(f:element[1]/f:slicing)"></xpath>
       </constraint>
       <constraint>
@@ -191407,7 +191398,7 @@ If the definition is a constraint, then it can not define new elements, it can o
        <requirements value="Because these 3 fields seem to be have overlapping meaning with the ones in the root of StructureDefinition"></requirements>
        <severity value="error"></severity>
        <human value="In any snapshot or differential, no label, code or requirements on the an element without a &quot;.&quot; in the path (e.g. the first element)"></human>
-       <expression value="children().element.first().label.empty() and children().element.first().code.empty() and children().element.first().requirements.empty()"></expression>
+       <expression value="children().element.where(path.contains('.').not()).label.empty() and children().element.where(path.contains('.').not()).code.empty() and children().element.where(path.contains('.').not()).requirements.empty()"></expression>
        <xpath value="not(exists(f:snapshot/f:element[not(contains(f:path/@value, '.')) and (f:label or f:code or f:requirements)])) and not(exists(f:differential/f:element[not(contains(f:path/@value, '.')) and (f:label or f:code or f:requirements)]))"></xpath>
       </constraint>
       <constraint>
@@ -191442,14 +191433,6 @@ If the definition is a constraint, then it can not define new elements, it can o
        <expression value="differential.element.id.trace('ids').isDistinct()"></expression>
        <xpath value="count(*/f:element)=count(*/f:element/@id)"></xpath>
       </constraint>
-      <constraint>
-       <key value="sdf-12"></key>
-       <requirements value="Ensure that element.base appears with base or not"></requirements>
-       <severity value="error"></severity>
-       <human value="element.base cannot appear if there is no base on the structure definition"></human>
-       <expression value="snapshot.exists() implies (snapshot.element.base.exists() = baseDefinition.exists())"></expression>
-       <xpath value="f:baseDefinition or not(exists(f:snapshot/f:element/f:base) or exists(f:differential/f:element/f:base))"></xpath>
-      </constraint>
       <constraint>
        <key value="sdf-11"></key>
        <requirements value="Ensure that the type is not inconsistent with the other information in the structure"></requirements>
@@ -191823,7 +191806,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      <element id="StructureDefinition.fhirVersion">
       <path value="StructureDefinition.fhirVersion"></path>
       <short value="FHIR Version this StructureDefinition targets"></short>
-      <definition value="The version of the FHIR specification on which this StructureDefinition is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.1 for this version."></definition>
+      <definition value="The version of the FHIR specification on which this StructureDefinition is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.2 for this version."></definition>
       <comment value="A StructureDefinition does not need to specify the target it applies to,as StructureDefinitions will often be valid across multiple versions of FHIR. FHIR tooling can determine whether a StructureDefinition is consistent with a particular StructureDefinition if desired."></comment>
       <min value="0"></min>
       <max value="1"></max>
@@ -192023,7 +192006,6 @@ If the definition is a constraint, then it can not define new elements, it can o
       <type>
        <code value="code"></code>
       </type>
-      <condition value="sdf-12"></condition>
       <isSummary value="true"></isSummary>
       <binding>
        <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName">
@@ -192051,14 +192033,14 @@ If the definition is a constraint, then it can not define new elements, it can o
        <requirements value="No Type on the root element (snapshot)"></requirements>
        <severity value="error"></severity>
        <human value="The first element in a snapshot has no type"></human>
-       <expression value="element.first().type.empty()"></expression>
+       <expression value="kind!='logical' implies snapshot.element.first().type.empty()"></expression>
        <xpath value="not(f:element[1]/f:type)"></xpath>
       </constraint>
       <constraint>
        <key value="sdf-8"></key>
        <severity value="error"></severity>
        <human value="In any snapshot, all the elements must be in the specified type"></human>
-       <expression value="element.first().path = %resource.type and element.tail().all(path.startsWith(%resource.type&amp;'.'))"></expression>
+       <expression value="(%resource.kind = #39;.logical#39;. or element.first().path = %resource.type) and element.tail().all(path.startsWith(%resource.snapshot.element.first().path&amp;'.'))"></expression>
        <xpath value="f:element[1]/f:path/@value=parent::f:StructureDefinition/f:type/@value and count(f:element[position()!=1])=count(f:element[position()!=1][starts-with(f:path/@value, concat(ancestor::f:StructureDefinition/f:type/@value, '.'))])"></xpath>
       </constraint>
       <constraint>
@@ -192107,7 +192089,7 @@ If the definition is a constraint, then it can not define new elements, it can o
        <requirements value="no slicing on root"></requirements>
        <severity value="error"></severity>
        <human value="No slicing on the root element"></human>
-       <expression value="element.first().slicing.empty()"></expression>
+       <expression value="element.where(path.contains('.').not()).slicing.empty()"></expression>
        <xpath value="not(f:element[1]/f:slicing)"></xpath>
       </constraint>
       <constraint>
@@ -192142,7 +192124,7 @@ If the definition is a constraint, then it can not define new elements, it can o
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="StructureMap"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -192153,7 +192135,7 @@ If the definition is a constraint, then it can not define new elements, it can o
     <url value="http://hl7.org/fhir/StructureDefinition/StructureMap"></url>
     <name value="StructureMap"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -192168,7 +192150,7 @@ If the definition is a constraint, then it can not define new elements, it can o
      </telecom>
     </contact>
     <description value="Base StructureDefinition for StructureMap Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -194964,7 +194946,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Subscription"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="3"></valueInteger>
@@ -194975,7 +194957,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/Subscription"></url>
     <name value="Subscription"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -194990,7 +194972,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Subscription Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -195722,7 +195704,7 @@ This element is labeled as a modifier because the status contains codes that mar
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Substance"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -195733,7 +195715,7 @@ This element is labeled as a modifier because the status contains codes that mar
     <url value="http://hl7.org/fhir/StructureDefinition/Substance"></url>
     <name value="Substance"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -195748,7 +195730,7 @@ This element is labeled as a modifier because the status contains codes that mar
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Substance Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -196684,7 +196666,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="SupplyDelivery"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -196695,7 +196677,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/SupplyDelivery"></url>
     <name value="SupplyDelivery"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -196710,7 +196692,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for SupplyDelivery Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -197686,7 +197668,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="SupplyRequest"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -197697,7 +197679,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/SupplyRequest"></url>
     <name value="SupplyRequest"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -197712,7 +197694,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for SupplyRequest Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -199155,7 +199137,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Task"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -199166,7 +199148,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/Task"></url>
     <name value="Task"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Orders and Observations)"></publisher>
     <contact>
      <telecom>
@@ -199181,7 +199163,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Task Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -201951,7 +201933,7 @@ In most cases, Tasks will have an intent of &quot;order&quot;."></comment>
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="TestReport"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="0"></valueInteger>
@@ -201962,7 +201944,7 @@ In most cases, Tasks will have an intent of &quot;order&quot;."></comment>
     <url value="http://hl7.org/fhir/StructureDefinition/TestReport"></url>
     <name value="TestReport"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -201977,7 +201959,7 @@ In most cases, Tasks will have an intent of &quot;order&quot;."></comment>
      </telecom>
     </contact>
     <description value="Base StructureDefinition for TestReport Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -203776,7 +203758,7 @@ This element is labeled as a modifier because the status contains codes that mar
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="TestScript"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="2"></valueInteger>
@@ -203787,7 +203769,7 @@ This element is labeled as a modifier because the status contains codes that mar
     <url value="http://hl7.org/fhir/StructureDefinition/TestScript"></url>
     <name value="TestScript"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -203802,7 +203784,7 @@ This element is labeled as a modifier because the status contains codes that mar
      </telecom>
     </contact>
     <description value="Base StructureDefinition for TestScript Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -205036,7 +205018,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.fixture.resource"></path>
       <short value="Reference of the resource"></short>
       <definition value="Reference to the resource (containing the contents of the resource needed for operations)."></definition>
-      <comment value="See http://build.fhir.org/resourcelist.html for complete list of resource types."></comment>
+      <comment value="See http://hl7.org/fhir/STU3/resourcelist.html for complete list of resource types."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <type>
@@ -205048,7 +205030,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.profile"></path>
       <short value="Reference of the validation profile"></short>
       <definition value="Reference to the profile to be used for validation."></definition>
-      <comment value="See http://build.fhir.org/resourcelist.html for complete list of resource types."></comment>
+      <comment value="See http://hl7.org/fhir/STU3/resourcelist.html for complete list of resource types."></comment>
       <min value="0"></min>
       <max value="*"></max>
       <type>
@@ -206027,7 +206009,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.setup.action.operation.type"></path>
       <short value="The operation code type that will be executed"></short>
       <definition value="Server interaction or operation type."></definition>
-      <comment value="See http://build.fhir.org/http.html for list of server interactions."></comment>
+      <comment value="See http://hl7.org/fhir/STU3/http.html for list of server interactions."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <type>
@@ -206047,7 +206029,7 @@ The destination indices provided elsewhere in the test script must be one of the
      <element id="TestScript.setup.action.operation.resource">
       <path value="TestScript.setup.action.operation.resource"></path>
       <short value="Resource type"></short>
-      <definition value="The type of the resource.  See http://build.fhir.org/resourcelist.html."></definition>
+      <definition value="The type of the resource.  See http://hl7.org/fhir/STU3/resourcelist.html."></definition>
       <comment value="If &quot;url&quot; element is specified, then &quot;targetId&quot;, &quot;params&quot;, and &quot;resource&quot; elements will be ignored as &quot;url&quot; element will have everything needed for constructing the request url.  If &quot;params&quot; element is specified, then &quot;targetId&quot; element is ignored. For FHIR operations that require a resource (e.g. &quot;read&quot; and &quot;vread&quot; operations), the &quot;resource&quot; element must be specified when &quot;params&quot; element is specified.  If &quot;url&quot; and &quot;params&quot; elements are absent, then the request url will be constructed from &quot;targetId&quot; fixture if present. For &quot;read&quot; operation, the resource and id values will be extracted from &quot;targetId&quot; fixture and used to construct the url. For &quot;vread&quot; and &quot;history&quot; operations, the versionId value will also be used."></comment>
       <min value="0"></min>
       <max value="1"></max>
@@ -206182,7 +206164,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.setup.action.operation.requestHeader"></path>
       <short value="Each operation can have one or more header elements"></short>
       <definition value="Header elements would be used to set HTTP headers."></definition>
-      <comment value="This gives control to test-script writers to set headers explicitly based on test requirements.  It will allow for testing using:  - &quot;If-Modified-Since&quot; and &quot;If-None-Match&quot; headers.  See http://build.fhir.org/http.html#2.1.0.5.1 - &quot;If-Match&quot; header.  See http://build.fhir.org/http.html#2.1.0.11 - Conditional Create using &quot;If-None-Exist&quot;.  See http://build.fhir.org/http.html#2.1.0.13.1 - Invalid &quot;Content-Type&quot; header for negative testing. - etc."></comment>
+      <comment value="This gives control to test-script writers to set headers explicitly based on test requirements.  It will allow for testing using:  - &quot;If-Modified-Since&quot; and &quot;If-None-Match&quot; headers.  See http://hl7.org/fhir/STU3/http.html#2.1.0.5.1 - &quot;If-Match&quot; header.  See http://hl7.org/fhir/STU3/http.html#2.1.0.11 - Conditional Create using &quot;If-None-Exist&quot;.  See http://hl7.org/fhir/STU3/http.html#2.1.0.13.1 - Invalid &quot;Content-Type&quot; header for negative testing. - etc."></comment>
       <min value="0"></min>
       <max value="*"></max>
       <type>
@@ -206655,8 +206637,8 @@ The destination indices provided elsewhere in the test script must be one of the
      <element id="TestScript.setup.action.assert.resource">
       <path value="TestScript.setup.action.assert.resource"></path>
       <short value="Resource type"></short>
-      <definition value="The type of the resource.  See http://build.fhir.org/resourcelist.html."></definition>
-      <comment value="This will be expected resource type in response body e.g. in read, vread, search, etc.  See http://build.fhir.org/resourcelist.html for complete list of resource types; e.g. &lt;assert &gt; &lt;resourceType value=&quot;Patient&quot; &lt;/assert&gt;."></comment>
+      <definition value="The type of the resource.  See http://hl7.org/fhir/STU3/resourcelist.html."></definition>
+      <comment value="This will be expected resource type in response body e.g. in read, vread, search, etc.  See http://hl7.org/fhir/STU3/resourcelist.html for complete list of resource types; e.g. &lt;assert &gt; &lt;resourceType value=&quot;Patient&quot; &lt;/assert&gt;."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <type>
@@ -208248,7 +208230,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.fixture.resource"></path>
       <short value="Reference of the resource"></short>
       <definition value="Reference to the resource (containing the contents of the resource needed for operations)."></definition>
-      <comment value="See http://build.fhir.org/resourcelist.html for complete list of resource types."></comment>
+      <comment value="See http://hl7.org/fhir/STU3/resourcelist.html for complete list of resource types."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <type>
@@ -208260,7 +208242,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.profile"></path>
       <short value="Reference of the validation profile"></short>
       <definition value="Reference to the profile to be used for validation."></definition>
-      <comment value="See http://build.fhir.org/resourcelist.html for complete list of resource types."></comment>
+      <comment value="See http://hl7.org/fhir/STU3/resourcelist.html for complete list of resource types."></comment>
       <min value="0"></min>
       <max value="*"></max>
       <type>
@@ -208564,7 +208546,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.setup.action.operation.type"></path>
       <short value="The operation code type that will be executed"></short>
       <definition value="Server interaction or operation type."></definition>
-      <comment value="See http://build.fhir.org/http.html for list of server interactions."></comment>
+      <comment value="See http://hl7.org/fhir/STU3/http.html for list of server interactions."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <type>
@@ -208584,7 +208566,7 @@ The destination indices provided elsewhere in the test script must be one of the
      <element id="TestScript.setup.action.operation.resource">
       <path value="TestScript.setup.action.operation.resource"></path>
       <short value="Resource type"></short>
-      <definition value="The type of the resource.  See http://build.fhir.org/resourcelist.html."></definition>
+      <definition value="The type of the resource.  See http://hl7.org/fhir/STU3/resourcelist.html."></definition>
       <comment value="If &quot;url&quot; element is specified, then &quot;targetId&quot;, &quot;params&quot;, and &quot;resource&quot; elements will be ignored as &quot;url&quot; element will have everything needed for constructing the request url.  If &quot;params&quot; element is specified, then &quot;targetId&quot; element is ignored. For FHIR operations that require a resource (e.g. &quot;read&quot; and &quot;vread&quot; operations), the &quot;resource&quot; element must be specified when &quot;params&quot; element is specified.  If &quot;url&quot; and &quot;params&quot; elements are absent, then the request url will be constructed from &quot;targetId&quot; fixture if present. For &quot;read&quot; operation, the resource and id values will be extracted from &quot;targetId&quot; fixture and used to construct the url. For &quot;vread&quot; and &quot;history&quot; operations, the versionId value will also be used."></comment>
       <min value="0"></min>
       <max value="1"></max>
@@ -208719,7 +208701,7 @@ The destination indices provided elsewhere in the test script must be one of the
       <path value="TestScript.setup.action.operation.requestHeader"></path>
       <short value="Each operation can have one or more header elements"></short>
       <definition value="Header elements would be used to set HTTP headers."></definition>
-      <comment value="This gives control to test-script writers to set headers explicitly based on test requirements.  It will allow for testing using:  - &quot;If-Modified-Since&quot; and &quot;If-None-Match&quot; headers.  See http://build.fhir.org/http.html#2.1.0.5.1 - &quot;If-Match&quot; header.  See http://build.fhir.org/http.html#2.1.0.11 - Conditional Create using &quot;If-None-Exist&quot;.  See http://build.fhir.org/http.html#2.1.0.13.1 - Invalid &quot;Content-Type&quot; header for negative testing. - etc."></comment>
+      <comment value="This gives control to test-script writers to set headers explicitly based on test requirements.  It will allow for testing using:  - &quot;If-Modified-Since&quot; and &quot;If-None-Match&quot; headers.  See http://hl7.org/fhir/STU3/http.html#2.1.0.5.1 - &quot;If-Match&quot; header.  See http://hl7.org/fhir/STU3/http.html#2.1.0.11 - Conditional Create using &quot;If-None-Exist&quot;.  See http://hl7.org/fhir/STU3/http.html#2.1.0.13.1 - Invalid &quot;Content-Type&quot; header for negative testing. - etc."></comment>
       <min value="0"></min>
       <max value="*"></max>
       <type>
@@ -209042,8 +209024,8 @@ The destination indices provided elsewhere in the test script must be one of the
      <element id="TestScript.setup.action.assert.resource">
       <path value="TestScript.setup.action.assert.resource"></path>
       <short value="Resource type"></short>
-      <definition value="The type of the resource.  See http://build.fhir.org/resourcelist.html."></definition>
-      <comment value="This will be expected resource type in response body e.g. in read, vread, search, etc.  See http://build.fhir.org/resourcelist.html for complete list of resource types; e.g. &lt;assert &gt; &lt;resourceType value=&quot;Patient&quot; &lt;/assert&gt;."></comment>
+      <definition value="The type of the resource.  See http://hl7.org/fhir/STU3/resourcelist.html."></definition>
+      <comment value="This will be expected resource type in response body e.g. in read, vread, search, etc.  See http://hl7.org/fhir/STU3/resourcelist.html for complete list of resource types; e.g. &lt;assert &gt; &lt;resourceType value=&quot;Patient&quot; &lt;/assert&gt;."></comment>
       <min value="0"></min>
       <max value="1"></max>
       <type>
@@ -209426,7 +209408,7 @@ The destination indices provided elsewhere in the test script must be one of the
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ValueSet"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="5"></valueInteger>
@@ -209437,7 +209419,7 @@ The destination indices provided elsewhere in the test script must be one of the
     <url value="http://hl7.org/fhir/StructureDefinition/ValueSet"></url>
     <name value="ValueSet"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Vocabulary)"></publisher>
     <contact>
      <telecom>
@@ -209452,7 +209434,7 @@ The destination indices provided elsewhere in the test script must be one of the
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ValueSet Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -212091,7 +212073,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="VisionPrescription"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
      <valueInteger value="1"></valueInteger>
@@ -212102,7 +212084,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
     <url value="http://hl7.org/fhir/StructureDefinition/VisionPrescription"></url>
     <name value="VisionPrescription"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (Financial Management)"></publisher>
     <contact>
      <telecom>
@@ -212117,7 +212099,7 @@ This is labeled as &quot;Is Modifier&quot; because applications should not use a
      </telecom>
     </contact>
     <description value="Base StructureDefinition for VisionPrescription Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="workflow"></identity>
      <uri value="http://hl7.org/fhir/workflow"></uri>
@@ -213269,7 +213251,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="MetadataResource"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
      <valueCode value="fhir"></valueCode>
@@ -213277,7 +213259,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
     <url value="http://hl7.org/fhir/StructureDefinition/MetadataResource"></url>
     <name value="MetadataResource"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="Health Level Seven International (FHIR Infrastructure)"></publisher>
     <contact>
      <telecom>
@@ -213292,7 +213274,7 @@ This element is labelled as a modifier because the implicit rules may provide ad
      </telecom>
     </contact>
     <description value="Base StructureDefinition for MetadataResource Resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="w5"></identity>
      <uri value="http://hl7.org/fhir/w5"></uri>
diff --git a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-types.xml b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-types.xml
index b3c4c4481df..adaccec5277 100644
--- a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-types.xml
+++ b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/profile/profiles-types.xml
@@ -1,7 +1,7 @@
 <Bundle xmlns="http://hl7.org/fhir">
  <id value="types"></id>
  <meta>
-  <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+  <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
  </meta>
  <type value="collection"></type>
  <entry>
@@ -10,12 +10,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Element"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Element"></url>
     <name value="Element"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -24,7 +24,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Element Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -164,12 +164,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="BackboneElement"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/BackboneElement"></url>
     <name value="BackboneElement"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -178,7 +178,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for BackboneElement Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -323,12 +323,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="base64Binary"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/base64Binary"></url>
     <name value="base64Binary"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -337,7 +337,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for base64Binary Type: A stream of bytes"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="base64Binary"></type>
@@ -401,7 +401,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -433,7 +432,6 @@
       <definition value="Primitive value for base64Binary"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -458,12 +456,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="boolean"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/boolean"></url>
     <name value="boolean"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -472,7 +470,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for boolean Type: Value of &quot;true&quot; or &quot;false&quot;"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="boolean"></type>
@@ -535,7 +533,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -566,7 +563,6 @@
       <definition value="Primitive value for boolean"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -591,12 +587,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="code"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/code"></url>
     <name value="code"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -605,7 +601,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for code type: A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="code"></type>
@@ -678,7 +674,6 @@
        <min value="0"></min>
        <max value="1"></max>
       </base>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[^\s]+([\s]?[^\s]+)*"></valueString>
@@ -712,7 +707,6 @@
       <definition value="Primitive value for code"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[^\s]+([\s]?[^\s]+)*"></valueString>
@@ -740,12 +734,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="date"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/date"></url>
     <name value="date"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -754,7 +748,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for date Type: A date or partial date (e.g. just year or year + month). There is no time zone. The format is a union of the schema types gYear, gYearMonth and date.  Dates SHALL be valid dates."></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="date"></type>
@@ -817,7 +811,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="-?[0-9]{4}(-(0[1-9]|1[0-2])(-(0[0-9]|[1-2][0-9]|3[0-1]))?)?"></valueString>
@@ -851,7 +844,6 @@
       <definition value="Primitive value for date"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="-?[0-9]{4}(-(0[1-9]|1[0-2])(-(0[0-9]|[1-2][0-9]|3[0-1]))?)?"></valueString>
@@ -879,12 +871,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="dateTime"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/dateTime"></url>
     <name value="dateTime"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -893,7 +885,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for dateTime Type: A date, date-time or partial date (e.g. just year or year + month).  If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored.                 Dates SHALL be valid dates."></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="dateTime"></type>
@@ -956,10 +948,9 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
-        <valueString value="-?[0-9]{4}(-(0[1-9]|1[0-2])(-(0[0-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?"></valueString>
+        <valueString value="-?([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\.[0-9]+)?(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?"></valueString>
        </extension>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -990,10 +981,9 @@
       <definition value="Primitive value for dateTime"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
-        <valueString value="-?[0-9]{4}(-(0[1-9]|1[0-2])(-(0[0-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?"></valueString>
+        <valueString value="-?([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\.[0-9]+)?(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?"></valueString>
        </extension>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -1018,12 +1008,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="decimal"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/decimal"></url>
     <name value="decimal"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -1032,7 +1022,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for decimal Type: A rational number with implicit precision"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="decimal"></type>
@@ -1096,7 +1086,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="-?([0]|([1-9][0-9]*))(\.[0-9]+)?"></valueString>
@@ -1131,7 +1120,6 @@
       <definition value="Primitive value for decimal"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="-?([0]|([1-9][0-9]*))(\.[0-9]+)?"></valueString>
@@ -1159,12 +1147,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="id"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/id"></url>
     <name value="id"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -1173,7 +1161,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for id type: Any combination of letters, numerals, &quot;-&quot; and &quot;.&quot;, with a length limit of 64 characters.  (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.)  Ids are case-insensitive."></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="id"></type>
@@ -1247,7 +1235,6 @@
        <min value="0"></min>
        <max value="1"></max>
       </base>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[A-Za-z0-9\-\.]{1,64}"></valueString>
@@ -1282,7 +1269,6 @@
       <definition value="Primitive value for id"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[A-Za-z0-9\-\.]{1,64}"></valueString>
@@ -1310,12 +1296,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="instant"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/instant"></url>
     <name value="instant"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -1324,7 +1310,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for instant Type: An instant in time - known at least to the second"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="instant"></type>
@@ -1388,8 +1374,10 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
+       <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
+        <valueString value="([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1])T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\.[0-9]+)?(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))"></valueString>
+       </extension>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
          <valueString value="string"></valueString>
@@ -1420,8 +1408,10 @@
       <definition value="Primitive value for instant"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
+       <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
+        <valueString value="([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1])T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\.[0-9]+)?(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))"></valueString>
+       </extension>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
          <valueString value="string"></valueString>
@@ -1445,12 +1435,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="integer"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/integer"></url>
     <name value="integer"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -1459,7 +1449,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for integer Type: A whole number"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="integer"></type>
@@ -1523,7 +1513,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="-?([0]|([1-9][0-9]*))"></valueString>
@@ -1560,7 +1549,6 @@
       <definition value="Primitive value for integer"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="-?([0]|([1-9][0-9]*))"></valueString>
@@ -1590,12 +1578,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="markdown"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/markdown"></url>
     <name value="markdown"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -1604,7 +1592,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for markdown type: A string that may contain markdown syntax for optional processing by a mark down presentation engine"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="markdown"></type>
@@ -1678,7 +1666,6 @@
        <min value="0"></min>
        <max value="1"></max>
       </base>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -1710,7 +1697,6 @@
       <definition value="Primitive value for markdown"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -1735,12 +1721,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="oid"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/oid"></url>
     <name value="oid"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -1749,7 +1735,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for oid type: An OID represented as a URI"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="oid"></type>
@@ -1823,7 +1809,6 @@
        <min value="0"></min>
        <max value="1"></max>
       </base>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="urn:oid:(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))*"></valueString>
@@ -1858,7 +1843,6 @@
       <definition value="Primitive value for oid"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="urn:oid:(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))*"></valueString>
@@ -1886,12 +1870,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="positiveInt"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/positiveInt"></url>
     <name value="positiveInt"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -1900,7 +1884,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for positiveInt type: An integer with a value that is positive (e.g. &gt;0)"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="positiveInt"></type>
@@ -1973,7 +1957,6 @@
        <min value="0"></min>
        <max value="1"></max>
       </base>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[1-9][0-9]*"></valueString>
@@ -2007,7 +1990,6 @@
       <definition value="Primitive value for positiveInt"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[1-9][0-9]*"></valueString>
@@ -2035,12 +2017,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="string"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/string"></url>
     <name value="string"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -2049,7 +2031,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for string Type: A sequence of Unicode characters"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="string"></type>
@@ -2113,7 +2095,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -2146,7 +2127,6 @@
       <definition value="Primitive value for string"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -2172,12 +2152,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="time"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/time"></url>
     <name value="time"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -2186,7 +2166,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for time Type: A time during the day, with no date specified"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="time"></type>
@@ -2249,7 +2229,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?"></valueString>
@@ -2283,7 +2262,6 @@
       <definition value="Primitive value for time"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?"></valueString>
@@ -2311,12 +2289,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="unsignedInt"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/unsignedInt"></url>
     <name value="unsignedInt"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -2325,7 +2303,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for unsignedInt type: An integer with a value that is not negative (e.g. &gt;= 0)"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="unsignedInt"></type>
@@ -2398,7 +2376,6 @@
        <min value="0"></min>
        <max value="1"></max>
       </base>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[0]|([1-9][0-9]*)"></valueString>
@@ -2432,7 +2409,6 @@
       <definition value="Primitive value for unsignedInt"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="[0]|([1-9][0-9]*)"></valueString>
@@ -2460,12 +2436,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="uri"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/uri"></url>
     <name value="uri"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -2474,7 +2450,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for uri Type: String of characters used to identify a name or a resource"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="uri"></type>
@@ -2538,7 +2514,6 @@
       <definition value="The actual value"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -2570,7 +2545,6 @@
       <definition value="Primitive value for uri"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -2595,12 +2569,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="uuid"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/uuid"></url>
     <name value="uuid"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -2609,7 +2583,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for uuid type: A UUID, represented as a URI"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="uuid"></type>
@@ -2683,7 +2657,6 @@
        <min value="0"></min>
        <max value="1"></max>
       </base>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}"></valueString>
@@ -2718,7 +2691,6 @@
       <definition value="Primitive value for uuid"></definition>
       <min value="0"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-regex">
         <valueString value="urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}"></valueString>
@@ -2746,12 +2718,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="xhtml"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/xhtml"></url>
     <name value="xhtml"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -2760,7 +2732,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for xhtml Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <kind value="primitive-type"></kind>
     <abstract value="false"></abstract>
     <type value="xhtml"></type>
@@ -2815,7 +2787,6 @@
       <definition value="Actual xhtml"></definition>
       <min value="1"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -2850,7 +2821,6 @@
       <definition value="Actual xhtml"></definition>
       <min value="1"></min>
       <max value="1"></max>
-      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML, JSON and RDF types provided by extension -->
       <type>
        <code>
         <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
@@ -2875,12 +2845,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Address"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Address"></url>
     <name value="Address"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -2890,7 +2860,7 @@
     </contact>
     <description value="Base StructureDefinition for Address Type"></description>
     <purpose value="Need to be able to record postal addresses, along with notes about their use."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -3664,12 +3634,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Age"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Age"></url>
     <name value="Age"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -3678,7 +3648,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Age Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -3954,12 +3924,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Annotation"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Annotation"></url>
     <name value="Annotation"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -3968,7 +3938,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Annotation Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -4228,12 +4198,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Attachment"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Attachment"></url>
     <name value="Attachment"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -4243,7 +4213,7 @@
     </contact>
     <description value="Base StructureDefinition for Attachment Type"></description>
     <purpose value="Many models need to include data defined in other specifications that is complex and opaque to the healthcare model. This includes documents, media recordings, structured data, etc."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -4763,12 +4733,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="CodeableConcept"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/CodeableConcept"></url>
     <name value="CodeableConcept"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -4778,7 +4748,7 @@
     </contact>
     <description value="Base StructureDefinition for CodeableConcept Type"></description>
     <purpose value="This is a common pattern in healthcare - a concept that may be defined by one or more codes from formal definitions including LOINC and SNOMED CT, and/or defined by the provision of text that captures a human sense of the concept."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -5021,12 +4991,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Coding"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Coding"></url>
     <name value="Coding"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -5036,7 +5006,7 @@
     </contact>
     <description value="Base StructureDefinition for Coding Type"></description>
     <purpose value="References to codes are very common in healthcare models."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -5423,12 +5393,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ContactDetail"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/ContactDetail"></url>
     <name value="ContactDetail"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -5438,7 +5408,7 @@
     </contact>
     <description value="Base StructureDefinition for ContactDetail Type"></description>
     <purpose value="Need to track contact information in the same way across multiple resources."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -5585,12 +5555,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ContactPoint"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/ContactPoint"></url>
     <name value="ContactPoint"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -5600,7 +5570,7 @@
     </contact>
     <description value="Base StructureDefinition for ContactPoint Type"></description>
     <purpose value="Need to track phone, fax, mobile, sms numbers, email addresses, twitter tags, etc."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -6025,12 +5995,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Contributor"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Contributor"></url>
     <name value="Contributor"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -6040,7 +6010,7 @@
     </contact>
     <description value="Base StructureDefinition for Contributor Type"></description>
     <purpose value="Need to track contributor information in the same way across multiple resources."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -6227,12 +6197,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Count"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Count"></url>
     <name value="Count"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -6242,7 +6212,7 @@
     </contact>
     <description value="Base StructureDefinition for Count Type"></description>
     <purpose value="Need to able to capture all sorts of measured values, even if the measured value are not precisely quantified. Values include exact measures such as 3.51g, customary units such as 3 tablets, and currencies such as $100.32USD."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -6519,12 +6489,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="DataRequirement"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/DataRequirement"></url>
     <name value="DataRequirement"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -6533,7 +6503,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for DataRequirement Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -7060,12 +7030,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Distance"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Distance"></url>
     <name value="Distance"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -7074,7 +7044,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Distance Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -7350,12 +7320,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Dosage"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Dosage"></url>
     <name value="Dosage"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -7364,7 +7334,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Dosage Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -8065,12 +8035,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Duration"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Duration"></url>
     <name value="Duration"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -8079,7 +8049,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Duration Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -8355,12 +8325,12 @@
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ElementDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/ElementDefinition"></url>
     <name value="ElementDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -8369,7 +8339,7 @@
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ElementDefinition Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="dex"></identity>
      <uri value="http://wiki.ihe.net/index.php?title=Data_Element_Exchange"></uri>
@@ -8475,9 +8445,9 @@
       <constraint>
        <key value="eld-16"></key>
        <severity value="error"></severity>
-       <human value="sliceName must be a proper token"></human>
-       <expression value="sliceName.empty() or sliceName.matches('^[a-zA-Z0-9\\-\\_]+$')"></expression>
-       <xpath value="not(exists(f:sliceName/@value)) or matches(f:sliceName/@value, '^[a-zA-Z0-9\\-\\_]+$')"></xpath>
+       <human value="sliceName must be composed of proper tokens separated by &quot;/&quot;"></human>
+       <expression value="sliceName.empty() or sliceName.matches('^[a-zA-Z0-9\\/\\-\\_]+$')"></expression>
+       <xpath value="not(exists(f:sliceName/@value)) or matches(f:sliceName/@value, '^[a-zA-Z0-9\\/\\-\\_]+$')"></xpath>
       </constraint>
       <constraint>
        <key value="eld-15"></key>
@@ -10637,13 +10607,6 @@ Note that an element that has the property IsModifier is not necessarily a &quot
        <xpath value="@value|f:*|h:div"></xpath>
        <source value="Element"></source>
       </constraint>
-      <constraint>
-       <key value="eld-10"></key>
-       <severity value="error"></severity>
-       <human value="provide either a reference or a description (or both)"></human>
-       <expression value="valueSet.exists() or description.exists()"></expression>
-       <xpath value="(exists(f:valueSetUri) or exists(f:valueSetReference)) or exists(f:description)"></xpath>
-      </constraint>
       <constraint>
        <key value="eld-12"></key>
        <severity value="error"></severity>
@@ -10770,7 +10733,6 @@ Note that an element that has the property IsModifier is not necessarily a &quot
       <type>
        <code value="string"></code>
       </type>
-      <condition value="eld-10"></condition>
       <isSummary value="true"></isSummary>
       <mapping>
        <identity value="rim"></identity>
@@ -10795,7 +10757,6 @@ Note that an element that has the property IsModifier is not necessarily a &quot
        <code value="Reference"></code>
        <targetProfile value="http://hl7.org/fhir/StructureDefinition/ValueSet"></targetProfile>
       </type>
-      <condition value="eld-10"></condition>
       <condition value="eld-12"></condition>
       <isSummary value="true"></isSummary>
       <mapping>
@@ -11042,9 +11003,9 @@ Note that an element that has the property IsModifier is not necessarily a &quot
       <constraint>
        <key value="eld-16"></key>
        <severity value="error"></severity>
-       <human value="sliceName must be a proper token"></human>
-       <expression value="sliceName.empty() or sliceName.matches('^[a-zA-Z0-9\\-\\_]+$')"></expression>
-       <xpath value="not(exists(f:sliceName/@value)) or matches(f:sliceName/@value, '^[a-zA-Z0-9\\-\\_]+$')"></xpath>
+       <human value="sliceName must be composed of proper tokens separated by &quot;/&quot;"></human>
+       <expression value="sliceName.empty() or sliceName.matches('^[a-zA-Z0-9\\/\\-\\_]+$')"></expression>
+       <xpath value="not(exists(f:sliceName/@value)) or matches(f:sliceName/@value, '^[a-zA-Z0-9\\/\\-\\_]+$')"></xpath>
       </constraint>
       <constraint>
        <key value="eld-15"></key>
@@ -12794,13 +12755,6 @@ Note that an element that has the property IsModifier is not necessarily a &quot
        <code value="Element"></code>
       </type>
       <condition value="eld-11"></condition>
-      <constraint>
-       <key value="eld-10"></key>
-       <severity value="error"></severity>
-       <human value="provide either a reference or a description (or both)"></human>
-       <expression value="valueSet.exists() or description.exists()"></expression>
-       <xpath value="(exists(f:valueSetUri) or exists(f:valueSetReference)) or exists(f:description)"></xpath>
-      </constraint>
       <constraint>
        <key value="eld-12"></key>
        <severity value="error"></severity>
@@ -12877,7 +12831,6 @@ Note that an element that has the property IsModifier is not necessarily a &quot
       <type>
        <code value="string"></code>
       </type>
-      <condition value="eld-10"></condition>
       <isSummary value="true"></isSummary>
       <mapping>
        <identity value="rim"></identity>
@@ -12902,7 +12855,6 @@ Note that an element that has the property IsModifier is not necessarily a &quot
        <code value="Reference"></code>
        <targetProfile value="http://hl7.org/fhir/StructureDefinition/ValueSet"></targetProfile>
       </type>
-      <condition value="eld-10"></condition>
       <condition value="eld-12"></condition>
       <isSummary value="true"></isSummary>
       <mapping>
@@ -13034,12 +12986,12 @@ Note that an element that has the property IsModifier is not necessarily a &quot
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Extension"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Extension"></url>
     <name value="Extension"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -13049,7 +13001,7 @@ Note that an element that has the property IsModifier is not necessarily a &quot
     </contact>
     <description value="Base StructureDefinition for Extension Type"></description>
     <purpose value="The ability to add extensions in a structured way is what keeps FHIR resources simple."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -13454,12 +13406,12 @@ Note that an element that has the property IsModifier is not necessarily a &quot
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="HumanName"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/HumanName"></url>
     <name value="HumanName"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -13469,7 +13421,7 @@ Note that an element that has the property IsModifier is not necessarily a &quot
     </contact>
     <description value="Base StructureDefinition for HumanName Type"></description>
     <purpose value="Need to be able to record names, along with notes about their use."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -13960,12 +13912,12 @@ Note that an element that has the property IsModifier is not necessarily a &quot
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Identifier"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Identifier"></url>
     <name value="Identifier"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -13975,7 +13927,7 @@ Note that an element that has the property IsModifier is not necessarily a &quot
     </contact>
     <description value="Base StructureDefinition for Identifier Type"></description>
     <purpose value="Need to be able to identify things with confidence and be sure that the identification is not subject to misinterpretation."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -14159,7 +14111,7 @@ Where the system is known, a type is unnecessary because the type is always part
       </type>
       <example>
        <label value="General"></label>
-       <valueUri value="http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri"></valueUri>
+       <valueUri value="http://www.acme.com/identifiers/patient"></valueUri>
       </example>
       <isSummary value="true"></isSummary>
       <mapping>
@@ -14352,7 +14304,7 @@ Where the system is known, a type is unnecessary because the type is always part
       </type>
       <example>
        <label value="General"></label>
-       <valueUri value="http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri"></valueUri>
+       <valueUri value="http://www.acme.com/identifiers/patient"></valueUri>
       </example>
       <isSummary value="true"></isSummary>
       <mapping>
@@ -14454,12 +14406,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Meta"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Meta"></url>
     <name value="Meta"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -14468,7 +14420,7 @@ Where the system is known, a type is unnecessary because the type is always part
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Meta Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -14743,12 +14695,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Money"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Money"></url>
     <name value="Money"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -14757,7 +14709,7 @@ Where the system is known, a type is unnecessary because the type is always part
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Money Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -15033,12 +14985,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Narrative"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Narrative"></url>
     <name value="Narrative"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -15047,7 +14999,7 @@ Where the system is known, a type is unnecessary because the type is always part
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Narrative Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -15262,12 +15214,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="ParameterDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/ParameterDefinition"></url>
     <name value="ParameterDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -15276,7 +15228,7 @@ Where the system is known, a type is unnecessary because the type is always part
      </telecom>
     </contact>
     <description value="Base StructureDefinition for ParameterDefinition Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -15579,12 +15531,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Period"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Period"></url>
     <name value="Period"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -15593,7 +15545,7 @@ Where the system is known, a type is unnecessary because the type is always part
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Period Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -15817,12 +15769,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Quantity"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Quantity"></url>
     <name value="Quantity"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -15832,7 +15784,7 @@ Where the system is known, a type is unnecessary because the type is always part
     </contact>
     <description value="Base StructureDefinition for Quantity Type"></description>
     <purpose value="Need to able to capture all sorts of measured values, even if the measured value are not precisely quantified. Values include exact measures such as 3.51g, customary units such as 3 tablets, and currencies such as $100.32USD."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -16208,12 +16160,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Range"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Range"></url>
     <name value="Range"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -16223,7 +16175,7 @@ Where the system is known, a type is unnecessary because the type is always part
     </contact>
     <description value="Base StructureDefinition for Range Type"></description>
     <purpose value="Need to be able to specify ranges of values."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -16449,12 +16401,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Ratio"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Ratio"></url>
     <name value="Ratio"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -16464,7 +16416,7 @@ Where the system is known, a type is unnecessary because the type is always part
     </contact>
     <description value="Base StructureDefinition for Ratio Type"></description>
     <purpose value="Need to able to capture ratios for some measurements (titers) and some rates (costs)."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -16660,12 +16612,12 @@ Where the system is known, a type is unnecessary because the type is always part
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Reference"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Reference"></url>
     <name value="Reference"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -16674,7 +16626,7 @@ Where the system is known, a type is unnecessary because the type is always part
      </telecom>
     </contact>
     <description value="Base StructureDefinition for Reference Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -16911,12 +16863,12 @@ Applications converting a logical reference to a literal reference may choose to
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="RelatedArtifact"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/RelatedArtifact"></url>
     <name value="RelatedArtifact"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -16926,7 +16878,7 @@ Applications converting a logical reference to a literal reference may choose to
     </contact>
     <description value="Base StructureDefinition for RelatedArtifact Type"></description>
     <purpose value="Knowledge resources must be able to provide enough information for consumers of the content (and/or interventions or results produced by the content) to be able to determine and understand the justification for and evidence in support of the content."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -17189,12 +17141,12 @@ Applications converting a logical reference to a literal reference may choose to
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="SampledData"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/SampledData"></url>
     <name value="SampledData"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -17204,7 +17156,7 @@ Applications converting a logical reference to a literal reference may choose to
     </contact>
     <description value="Base StructureDefinition for SampledData Type"></description>
     <purpose value="There is a need for a concise way to handle the data produced by devices that sample a physical state at a high frequency."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -17544,12 +17496,12 @@ Applications converting a logical reference to a literal reference may choose to
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Signature"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Signature"></url>
     <name value="Signature"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -17559,7 +17511,7 @@ Applications converting a logical reference to a literal reference may choose to
     </contact>
     <description value="Base StructureDefinition for Signature Type"></description>
     <purpose value="There are a number of places where content must be signed in healthcare."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -17934,12 +17886,12 @@ Applications converting a logical reference to a literal reference may choose to
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="Timing"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/Timing"></url>
     <name value="Timing"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -17949,7 +17901,7 @@ Applications converting a logical reference to a literal reference may choose to
     </contact>
     <description value="Base StructureDefinition for Timing Type"></description>
     <purpose value="Need to able to track proposed timing schedules. There are several different ways to do this: one or more specified times, a simple rules like three times a day, or  before/after meals."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
@@ -18935,12 +18887,12 @@ Applications converting a logical reference to a literal reference may choose to
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="TriggerDefinition"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/TriggerDefinition"></url>
     <name value="TriggerDefinition"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -18949,7 +18901,7 @@ Applications converting a logical reference to a literal reference may choose to
      </telecom>
     </contact>
     <description value="Base StructureDefinition for TriggerDefinition Type"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -19178,12 +19130,12 @@ Applications converting a logical reference to a literal reference may choose to
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="UsageContext"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/UsageContext"></url>
     <name value="UsageContext"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -19193,7 +19145,7 @@ Applications converting a logical reference to a literal reference may choose to
     </contact>
     <description value="Base StructureDefinition for UsageContext Type"></description>
     <purpose value="Consumers of the resource must be able to determine the intended applicability for the resource. Ideally, this information would be used programmatically to determine when and how it should be incorporated or exposed."></purpose>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="rim"></identity>
      <uri value="http://hl7.org/v3"></uri>
@@ -19390,12 +19342,12 @@ Applications converting a logical reference to a literal reference may choose to
    <StructureDefinition xmlns="http://hl7.org/fhir">
     <id value="SimpleQuantity"></id>
     <meta>
-     <lastUpdated value="2017-04-17T17:38:22.515-04:00"></lastUpdated>
+     <lastUpdated value="2019-10-24T11:53:00+11:00"></lastUpdated>
     </meta>
     <url value="http://hl7.org/fhir/StructureDefinition/SimpleQuantity"></url>
     <name value="SimpleQuantity"></name>
     <status value="draft"></status>
-    <date value="2017-04-17T17:38:22-04:00"></date>
+    <date value="2019-10-24T11:53:00+11:00"></date>
     <publisher value="HL7 FHIR Standard"></publisher>
     <contact>
      <telecom>
@@ -19404,7 +19356,7 @@ Applications converting a logical reference to a literal reference may choose to
      </telecom>
     </contact>
     <description value="A fixed quantity (no comparator)"></description>
-    <fhirVersion value="3.0.1"></fhirVersion>
+    <fhirVersion value="3.0.2"></fhirVersion>
     <mapping>
      <identity value="v2"></identity>
      <uri value="http://hl7.org/v2"></uri>
diff --git a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v2-tables.xml b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v2-tables.xml
index 5c026f51266..f8721fe1ec7 100644
--- a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v2-tables.xml
+++ b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v2-tables.xml
@@ -15928,7 +15928,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0009"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0009"></id>
+    <id value="v2-0009"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16157,7 +16157,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0240"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0240"></id>
+    <id value="v2-0240"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16266,7 +16266,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0482"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0482"></id>
+    <id value="v2-0482"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16319,7 +16319,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0241"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0241"></id>
+    <id value="v2-0241"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16412,7 +16412,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0483"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0483"></id>
+    <id value="v2-0483"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16529,7 +16529,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0242"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0242"></id>
+    <id value="v2-0242"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16622,7 +16622,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0484"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0484"></id>
+    <id value="v2-0484"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16695,7 +16695,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0480"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0480"></id>
+    <id value="v2-0480"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16753,7 +16753,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0247"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0247"></id>
+    <id value="v2-0247"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -16886,7 +16886,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0489"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0489"></id>
+    <id value="v2-0489"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17000,7 +17000,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0248"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0248"></id>
+    <id value="v2-0248"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17069,7 +17069,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0007"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0007"></id>
+    <id value="v2-0007"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17190,7 +17190,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0008"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0008"></id>
+    <id value="v2-0008"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17299,7 +17299,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0001"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0001"></id>
+    <id value="v2-0001"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17408,7 +17408,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0243"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0243"></id>
+    <id value="v2-0243"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17477,7 +17477,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0485"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0485"></id>
+    <id value="v2-0485"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17648,7 +17648,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0002"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0002"></id>
+    <id value="v2-0002"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -17869,7 +17869,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0003"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0003"></id>
+    <id value="v2-0003"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -21882,7 +21882,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0487"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0487"></id>
+    <id value="v2-0487"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -24248,7 +24248,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0004"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0004"></id>
+    <id value="v2-0004"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -24389,7 +24389,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0488"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0488"></id>
+    <id value="v2-0488"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -24594,7 +24594,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0250"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0250"></id>
+    <id value="v2-0250"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -24671,7 +24671,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0492"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0492"></id>
+    <id value="v2-0492"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -24734,7 +24734,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0251"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0251"></id>
+    <id value="v2-0251"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -24819,7 +24819,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0493"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0493"></id>
+    <id value="v2-0493"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -24899,7 +24899,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0252"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0252"></id>
+    <id value="v2-0252"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25024,7 +25024,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0494"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0494"></id>
+    <id value="v2-0494"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25073,7 +25073,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0253"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0253"></id>
+    <id value="v2-0253"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25150,7 +25150,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0495"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0495"></id>
+    <id value="v2-0495"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25255,7 +25255,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0490"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0490"></id>
+    <id value="v2-0490"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25348,7 +25348,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0491"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0491"></id>
+    <id value="v2-0491"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25401,7 +25401,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0258"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0258"></id>
+    <id value="v2-0258"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25466,7 +25466,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0017"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0017"></id>
+    <id value="v2-0017"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25563,7 +25563,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0259"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0259"></id>
+    <id value="v2-0259"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25808,7 +25808,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0012"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0012"></id>
+    <id value="v2-0012"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -25883,7 +25883,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0254"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0254"></id>
+    <id value="v2-0254"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -26943,7 +26943,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0496"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0496"></id>
+    <id value="v2-0496"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -27939,7 +27939,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0255"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0255"></id>
+    <id value="v2-0255"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28208,7 +28208,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0497"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0497"></id>
+    <id value="v2-0497"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28269,7 +28269,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0256"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0256"></id>
+    <id value="v2-0256"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28658,7 +28658,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0498"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0498"></id>
+    <id value="v2-0498"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28743,7 +28743,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0257"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0257"></id>
+    <id value="v2-0257"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28804,7 +28804,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0499"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0499"></id>
+    <id value="v2-0499"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28857,7 +28857,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0229"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0229"></id>
+    <id value="v2-0229"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28944,7 +28944,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0460"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0460"></id>
+    <id value="v2-0460"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -28993,7 +28993,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0220"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0220"></id>
+    <id value="v2-0220"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -29082,7 +29082,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0225"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0225"></id>
+    <id value="v2-0225"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -29143,7 +29143,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0468"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0468"></id>
+    <id value="v2-0468"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -29200,7 +29200,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0227"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0227"></id>
+    <id value="v2-0227"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -29800,7 +29800,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0469"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0469"></id>
+    <id value="v2-0469"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -29861,7 +29861,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0228"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0228"></id>
+    <id value="v2-0228"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -29994,7 +29994,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0223"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0223"></id>
+    <id value="v2-0223"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30113,7 +30113,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0465"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0465"></id>
+    <id value="v2-0465"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30166,7 +30166,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0224"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0224"></id>
+    <id value="v2-0224"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30227,7 +30227,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0466"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0466"></id>
+    <id value="v2-0466"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30291,7 +30291,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0470"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0470"></id>
+    <id value="v2-0470"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30368,7 +30368,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0230"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0230"></id>
+    <id value="v2-0230"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30453,7 +30453,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0472"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0472"></id>
+    <id value="v2-0472"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30523,7 +30523,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0231"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0231"></id>
+    <id value="v2-0231"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30584,7 +30584,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0473"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0473"></id>
+    <id value="v2-0473"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30653,7 +30653,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0236"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0236"></id>
+    <id value="v2-0236"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30722,7 +30722,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0478"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0478"></id>
+    <id value="v2-0478"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30791,7 +30791,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0237"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0237"></id>
+    <id value="v2-0237"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30892,7 +30892,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0238"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0238"></id>
+    <id value="v2-0238"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -30961,7 +30961,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0239"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0239"></id>
+    <id value="v2-0239"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -31030,7 +31030,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0391/2.4"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="2.4"></id>
+    <id value="v2-2.4-0391"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -31098,7 +31098,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0232"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0232"></id>
+    <id value="v2-0232"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -31159,7 +31159,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0474"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0474"></id>
+    <id value="v2-0474"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -31258,7 +31258,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0391/2.6"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="2.6"></id>
+    <id value="v2-2.6-0391"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -31715,7 +31715,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0475"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0475"></id>
+    <id value="v2-0475"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -31792,7 +31792,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0234"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0234"></id>
+    <id value="v2-0234"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -31909,7 +31909,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0235"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0235"></id>
+    <id value="v2-0235"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -32026,7 +32026,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0477"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0477"></id>
+    <id value="v2-0477"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -32105,7 +32105,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0283"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0283"></id>
+    <id value="v2-0283"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -32174,7 +32174,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0284"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0284"></id>
+    <id value="v2-0284"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -32243,7 +32243,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0043"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0043"></id>
+    <id value="v2-0043"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -32982,7 +32982,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0286"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0286"></id>
+    <id value="v2-0286"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -33051,7 +33051,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0280"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0280"></id>
+    <id value="v2-0280"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -33112,7 +33112,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0281"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0281"></id>
+    <id value="v2-0281"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -33193,7 +33193,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0282"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0282"></id>
+    <id value="v2-0282"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -33262,7 +33262,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0287"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0287"></id>
+    <id value="v2-0287"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -33379,7 +33379,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0048"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0048"></id>
+    <id value="v2-0048"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -33994,7 +33994,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0052"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0052"></id>
+    <id value="v2-0052"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -34063,7 +34063,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0294"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0294"></id>
+    <id value="v2-0294"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -34199,7 +34199,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0290"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0290"></id>
+    <id value="v2-0290"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -35022,7 +35022,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0291"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0291"></id>
+    <id value="v2-0291"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -35264,7 +35264,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0292"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0292"></id>
+    <id value="v2-0292"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -36665,7 +36665,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0298"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0298"></id>
+    <id value="v2-0298"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -36718,7 +36718,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0299"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0299"></id>
+    <id value="v2-0299"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -36786,7 +36786,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0261"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0261"></id>
+    <id value="v2-0261"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -36887,7 +36887,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0262"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0262"></id>
+    <id value="v2-0262"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -36972,7 +36972,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0263"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0263"></id>
+    <id value="v2-0263"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37065,7 +37065,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0260"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0260"></id>
+    <id value="v2-0260"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37166,7 +37166,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0027"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0027"></id>
+    <id value="v2-0027"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37263,7 +37263,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0269"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0269"></id>
+    <id value="v2-0269"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37316,7 +37316,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0023"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0023"></id>
+    <id value="v2-0023"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37511,7 +37511,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0265"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0265"></id>
+    <id value="v2-0265"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37756,7 +37756,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0267"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0267"></id>
+    <id value="v2-0267"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37849,7 +37849,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0268"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0268"></id>
+    <id value="v2-0268"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -37910,7 +37910,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0272"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0272"></id>
+    <id value="v2-0272"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -38049,7 +38049,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0273"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0273"></id>
+    <id value="v2-0273"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -38134,7 +38134,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0033"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0033"></id>
+    <id value="v2-0033"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -38621,7 +38621,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0275"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0275"></id>
+    <id value="v2-0275"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -38706,7 +38706,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0270"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0270"></id>
+    <id value="v2-0270"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -38855,7 +38855,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0271"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0271"></id>
+    <id value="v2-0271"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -38976,7 +38976,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0038"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0038"></id>
+    <id value="v2-0038"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39121,7 +39121,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0034"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0034"></id>
+    <id value="v2-0034"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39196,7 +39196,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0276"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0276"></id>
+    <id value="v2-0276"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39276,7 +39276,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0277"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0277"></id>
+    <id value="v2-0277"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39337,7 +39337,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0278"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0278"></id>
+    <id value="v2-0278"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39465,7 +39465,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0279"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0279"></id>
+    <id value="v2-0279"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39534,7 +39534,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0091"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0091"></id>
+    <id value="v2-0091"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39595,7 +39595,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0085"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0085"></id>
+    <id value="v2-0085"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39803,7 +39803,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0083"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0083"></id>
+    <id value="v2-0083"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39856,7 +39856,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0098"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0098"></id>
+    <id value="v2-0098"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39917,7 +39917,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0092"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0092"></id>
+    <id value="v2-0092"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -39969,7 +39969,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0063"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0063"></id>
+    <id value="v2-0063"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -40390,7 +40390,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0065"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0065"></id>
+    <id value="v2-0065"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -40533,7 +40533,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0066"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0066"></id>
+    <id value="v2-0066"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -40716,7 +40716,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0061"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0061"></id>
+    <id value="v2-0061"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -40804,7 +40804,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0062"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0062"></id>
+    <id value="v2-0062"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -40901,7 +40901,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0069"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0069"></id>
+    <id value="v2-0069"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -40978,7 +40978,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0080"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0080"></id>
+    <id value="v2-0080"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -41099,7 +41099,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0074"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0074"></id>
+    <id value="v2-0074"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -41666,7 +41666,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0076"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0076"></id>
+    <id value="v2-0076"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -43615,7 +43615,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0070"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0070"></id>
+    <id value="v2-0070"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -45718,7 +45718,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0078"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0078"></id>
+    <id value="v2-0078"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46290,7 +46290,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/4000"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="4000"></id>
+    <id value="v2-4000"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46369,7 +46369,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0806"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0806"></id>
+    <id value="v2-0806"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46418,7 +46418,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0818"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0818"></id>
+    <id value="v2-0818"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46471,7 +46471,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0618"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0618"></id>
+    <id value="v2-0618"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46520,7 +46520,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0615"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0615"></id>
+    <id value="v2-0615"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46571,7 +46571,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0616"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0616"></id>
+    <id value="v2-0616"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46636,7 +46636,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0617"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0617"></id>
+    <id value="v2-0617"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46694,7 +46694,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0834"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0834"></id>
+    <id value="v2-0834"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46762,7 +46762,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0409"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0409"></id>
+    <id value="v2-0409"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46823,7 +46823,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0406"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0406"></id>
+    <id value="v2-0406"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46916,7 +46916,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0401"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0401"></id>
+    <id value="v2-0401"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -46969,7 +46969,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0402"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0402"></id>
+    <id value="v2-0402"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47030,7 +47030,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0403"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0403"></id>
+    <id value="v2-0403"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47107,7 +47107,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0404"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0404"></id>
+    <id value="v2-0404"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47192,7 +47192,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0881"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0881"></id>
+    <id value="v2-0881"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47241,7 +47241,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0882"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0882"></id>
+    <id value="v2-0882"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47286,7 +47286,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0642"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0642"></id>
+    <id value="v2-0642"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47344,7 +47344,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0416"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0416"></id>
+    <id value="v2-0416"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47421,7 +47421,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0417"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0417"></id>
+    <id value="v2-0417"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47510,7 +47510,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0659"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0659"></id>
+    <id value="v2-0659"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47567,7 +47567,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0418"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0418"></id>
+    <id value="v2-0418"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47644,7 +47644,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0360/2.3.1"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="2.3.1"></id>
+    <id value="v2-2.3.1-0360"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47913,7 +47913,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0415"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0415"></id>
+    <id value="v2-0415"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -47958,7 +47958,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0657"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0657"></id>
+    <id value="v2-0657"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48007,7 +48007,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0651"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0651"></id>
+    <id value="v2-0651"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48052,7 +48052,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0894"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0894"></id>
+    <id value="v2-0894"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48097,7 +48097,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0411"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0411"></id>
+    <id value="v2-0411"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48392,7 +48392,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0653"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0653"></id>
+    <id value="v2-0653"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48471,7 +48471,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0895"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0895"></id>
+    <id value="v2-0895"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48552,7 +48552,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0625"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0625"></id>
+    <id value="v2-0625"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48610,7 +48610,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0868"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0868"></id>
+    <id value="v2-0868"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48682,7 +48682,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0634"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0634"></id>
+    <id value="v2-0634"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48723,7 +48723,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0871"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0871"></id>
+    <id value="v2-0871"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48837,7 +48837,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0207"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0207"></id>
+    <id value="v2-0207"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48914,7 +48914,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0208"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0208"></id>
+    <id value="v2-0208"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -48983,7 +48983,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0209"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0209"></id>
+    <id value="v2-0209"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -49084,7 +49084,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0440"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0440"></id>
+    <id value="v2-0440"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -50176,7 +50176,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0682"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0682"></id>
+    <id value="v2-0682"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -50227,7 +50227,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0203"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0203"></id>
+    <id value="v2-0203"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -51494,7 +51494,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0445"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0445"></id>
+    <id value="v2-0445"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -51547,7 +51547,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0204"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0204"></id>
+    <id value="v2-0204"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -51632,7 +51632,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0205"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0205"></id>
+    <id value="v2-0205"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -51725,7 +51725,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0206"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0206"></id>
+    <id value="v2-0206"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -51806,7 +51806,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0441"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0441"></id>
+    <id value="v2-0441"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -51879,7 +51879,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0200"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0200"></id>
+    <id value="v2-0200"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -52236,7 +52236,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0442"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0442"></id>
+    <id value="v2-0442"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -52289,7 +52289,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0201"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0201"></id>
+    <id value="v2-0201"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -52439,7 +52439,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0443"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0443"></id>
+    <id value="v2-0443"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -52741,7 +52741,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0202"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0202"></id>
+    <id value="v2-0202"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -52886,7 +52886,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0444"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0444"></id>
+    <id value="v2-0444"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -52947,7 +52947,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0450"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0450"></id>
+    <id value="v2-0450"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -52992,7 +52992,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0214"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0214"></id>
+    <id value="v2-0214"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53069,7 +53069,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0456"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0456"></id>
+    <id value="v2-0456"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53196,7 +53196,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0215"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0215"></id>
+    <id value="v2-0215"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53265,7 +53265,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0457"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0457"></id>
+    <id value="v2-0457"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53322,7 +53322,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0216"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0216"></id>
+    <id value="v2-0216"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53375,7 +53375,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0217"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0217"></id>
+    <id value="v2-0217"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53436,7 +53436,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0459"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0459"></id>
+    <id value="v2-0459"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53489,7 +53489,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0210"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0210"></id>
+    <id value="v2-0210"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53541,7 +53541,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0211"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0211"></id>
+    <id value="v2-0211"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53836,7 +53836,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0213"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0213"></id>
+    <id value="v2-0213"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53897,7 +53897,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0455"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0455"></id>
+    <id value="v2-0455"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -53968,7 +53968,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0427"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0427"></id>
+    <id value="v2-0427"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54065,7 +54065,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0669"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0669"></id>
+    <id value="v2-0669"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54130,7 +54130,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0428"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0428"></id>
+    <id value="v2-0428"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54191,7 +54191,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0429"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0429"></id>
+    <id value="v2-0429"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54316,7 +54316,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0423"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0423"></id>
+    <id value="v2-0423"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54357,7 +54357,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0424"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0424"></id>
+    <id value="v2-0424"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54418,7 +54418,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0425"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0425"></id>
+    <id value="v2-0425"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54511,7 +54511,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0667"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0667"></id>
+    <id value="v2-0667"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54562,7 +54562,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0426"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0426"></id>
+    <id value="v2-0426"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54659,7 +54659,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0421"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0421"></id>
+    <id value="v2-0421"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54720,7 +54720,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0422"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0422"></id>
+    <id value="v2-0422"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54805,7 +54805,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0438"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0438"></id>
+    <id value="v2-0438"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -54898,7 +54898,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0434"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0434"></id>
+    <id value="v2-0434"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55007,7 +55007,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0435"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0435"></id>
+    <id value="v2-0435"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55060,7 +55060,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0436"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0436"></id>
+    <id value="v2-0436"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55137,7 +55137,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0437"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0437"></id>
+    <id value="v2-0437"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55206,7 +55206,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0430"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0430"></id>
+    <id value="v2-0430"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55327,7 +55327,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0431"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0431"></id>
+    <id value="v2-0431"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55448,7 +55448,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0432"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0432"></id>
+    <id value="v2-0432"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55553,7 +55553,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0433"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0433"></id>
+    <id value="v2-0433"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55686,7 +55686,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0121"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0121"></id>
+    <id value="v2-0121"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55783,7 +55783,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0363"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0363"></id>
+    <id value="v2-0363"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -55994,7 +55994,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0126"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0126"></id>
+    <id value="v2-0126"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -56103,7 +56103,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0368"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0368"></id>
+    <id value="v2-0368"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -56314,7 +56314,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0127"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0127"></id>
+    <id value="v2-0127"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -56431,7 +56431,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0369"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0369"></id>
+    <id value="v2-0369"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -56556,7 +56556,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0128"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0128"></id>
+    <id value="v2-0128"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -56637,7 +56637,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0122"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0122"></id>
+    <id value="v2-0122"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -56770,7 +56770,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0364"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0364"></id>
+    <id value="v2-0364"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -56871,7 +56871,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0123"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0123"></id>
+    <id value="v2-0123"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -57040,7 +57040,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0365"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0365"></id>
+    <id value="v2-0365"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -57215,7 +57215,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0124"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0124"></id>
+    <id value="v2-0124"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -57300,7 +57300,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0366"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0366"></id>
+    <id value="v2-0366"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -57379,7 +57379,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0367"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0367"></id>
+    <id value="v2-0367"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -57486,7 +57486,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0371"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0371"></id>
+    <id value="v2-0371"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -57933,7 +57933,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0130"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0130"></id>
+    <id value="v2-0130"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58002,7 +58002,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0372"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0372"></id>
+    <id value="v2-0372"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58071,7 +58071,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0131"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0131"></id>
+    <id value="v2-0131"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58277,7 +58277,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0373"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0373"></id>
+    <id value="v2-0373"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58346,7 +58346,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0374"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0374"></id>
+    <id value="v2-0374"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58391,7 +58391,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0370"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0370"></id>
+    <id value="v2-0370"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58492,7 +58492,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0137"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0137"></id>
+    <id value="v2-0137"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58589,7 +58589,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0133"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0133"></id>
+    <id value="v2-0133"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58772,7 +58772,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0375"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0375"></id>
+    <id value="v2-0375"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58817,7 +58817,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0376"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0376"></id>
+    <id value="v2-0376"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -58973,7 +58973,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0135"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0135"></id>
+    <id value="v2-0135"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59046,7 +59046,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0377"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0377"></id>
+    <id value="v2-0377"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59091,7 +59091,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0136"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0136"></id>
+    <id value="v2-0136"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59152,7 +59152,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0108"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0108"></id>
+    <id value="v2-0108"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59259,7 +59259,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0109"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0109"></id>
+    <id value="v2-0109"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59334,7 +59334,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0104"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0104"></id>
+    <id value="v2-0104"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59559,7 +59559,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0105"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0105"></id>
+    <id value="v2-0105"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59632,7 +59632,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0106"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0106"></id>
+    <id value="v2-0106"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59719,7 +59719,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0107"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0107"></id>
+    <id value="v2-0107"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59794,7 +59794,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0100"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0100"></id>
+    <id value="v2-0100"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59891,7 +59891,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0102"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0102"></id>
+    <id value="v2-0102"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -59966,7 +59966,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0344"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0344"></id>
+    <id value="v2-0344"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -60195,7 +60195,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0103"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0103"></id>
+    <id value="v2-0103"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -60268,7 +60268,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0119"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0119"></id>
+    <id value="v2-0119"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -61025,7 +61025,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0350"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0350"></id>
+    <id value="v2-0350"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -61704,7 +61704,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0351"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0351"></id>
+    <id value="v2-0351"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -61851,7 +61851,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0357"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0357"></id>
+    <id value="v2-0357"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -62094,7 +62094,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0116"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0116"></id>
+    <id value="v2-0116"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -62206,7 +62206,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0359"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0359"></id>
+    <id value="v2-0359"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -62300,7 +62300,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0354"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0354"></id>
+    <id value="v2-0354"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -65223,7 +65223,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0355"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0355"></id>
+    <id value="v2-0355"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -65287,7 +65287,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0356"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0356"></id>
+    <id value="v2-0356"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -65357,7 +65357,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0162"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0162"></id>
+    <id value="v2-0162"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -65934,7 +65934,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0163"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0163"></id>
+    <id value="v2-0163"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -66649,7 +66649,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0164"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0164"></id>
+    <id value="v2-0164"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -66790,7 +66790,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0165"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0165"></id>
+    <id value="v2-0165"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67007,7 +67007,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0160"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0160"></id>
+    <id value="v2-0160"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67104,7 +67104,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0161"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0161"></id>
+    <id value="v2-0161"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67177,7 +67177,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0166"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0166"></id>
+    <id value="v2-0166"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67238,7 +67238,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0167"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0167"></id>
+    <id value="v2-0167"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67375,7 +67375,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0168"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0168"></id>
+    <id value="v2-0168"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67496,7 +67496,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0169"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0169"></id>
+    <id value="v2-0169"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67557,7 +67557,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0173"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0173"></id>
+    <id value="v2-0173"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67618,7 +67618,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0174"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0174"></id>
+    <id value="v2-0174"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -67730,7 +67730,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0175"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0175"></id>
+    <id value="v2-0175"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68039,7 +68039,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0170"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0170"></id>
+    <id value="v2-0170"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68112,7 +68112,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0177"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0177"></id>
+    <id value="v2-0177"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68269,7 +68269,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0178"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0178"></id>
+    <id value="v2-0178"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68330,7 +68330,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0179"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0179"></id>
+    <id value="v2-0179"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68415,7 +68415,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0140"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0140"></id>
+    <id value="v2-0140"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68540,7 +68540,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0141"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0141"></id>
+    <id value="v2-0141"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68631,7 +68631,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0383"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0383"></id>
+    <id value="v2-0383"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68756,7 +68756,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0142"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0142"></id>
+    <id value="v2-0142"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68817,7 +68817,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0384"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0384"></id>
+    <id value="v2-0384"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68912,7 +68912,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0148"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0148"></id>
+    <id value="v2-0148"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -68973,7 +68973,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0149"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0149"></id>
+    <id value="v2-0149"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69038,7 +69038,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0144"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0144"></id>
+    <id value="v2-0144"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69159,7 +69159,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0145"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0145"></id>
+    <id value="v2-0145"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69268,7 +69268,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0387"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0387"></id>
+    <id value="v2-0387"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69348,7 +69348,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0146"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0146"></id>
+    <id value="v2-0146"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69448,7 +69448,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0388"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0388"></id>
+    <id value="v2-0388"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69501,7 +69501,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0147"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0147"></id>
+    <id value="v2-0147"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69590,7 +69590,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0389"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0389"></id>
+    <id value="v2-0389"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69643,7 +69643,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0393"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0393"></id>
+    <id value="v2-0393"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69696,7 +69696,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0394"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0394"></id>
+    <id value="v2-0394"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -69757,7 +69757,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0153"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0153"></id>
+    <id value="v2-0153"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -70480,7 +70480,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0395"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0395"></id>
+    <id value="v2-0395"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -70533,7 +70533,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0396"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0396"></id>
+    <id value="v2-0396"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -72380,7 +72380,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0360/2.7"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="2.7"></id>
+    <id value="v2-2.7-0360"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -72664,7 +72664,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0150"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0150"></id>
+    <id value="v2-0150"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -72737,7 +72737,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0392"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0392"></id>
+    <id value="v2-0392"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -72806,7 +72806,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0159"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0159"></id>
+    <id value="v2-0159"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -72879,7 +72879,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0155"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0155"></id>
+    <id value="v2-0155"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -72964,7 +72964,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0397"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0397"></id>
+    <id value="v2-0397"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73041,7 +73041,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0156"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0156"></id>
+    <id value="v2-0156"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73196,7 +73196,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0398"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0398"></id>
+    <id value="v2-0398"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73249,7 +73249,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0157"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0157"></id>
+    <id value="v2-0157"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73388,7 +73388,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0158"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0158"></id>
+    <id value="v2-0158"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73495,7 +73495,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0190"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0190"></id>
+    <id value="v2-0190"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73761,7 +73761,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0185"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0185"></id>
+    <id value="v2-0185"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73870,7 +73870,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0187"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0187"></id>
+    <id value="v2-0187"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -73931,7 +73931,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0180"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0180"></id>
+    <id value="v2-0180"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74028,7 +74028,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0181"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0181"></id>
+    <id value="v2-0181"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74089,7 +74089,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0183"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0183"></id>
+    <id value="v2-0183"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74150,7 +74150,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0189"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0189"></id>
+    <id value="v2-0189"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74211,7 +74211,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0191"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0191"></id>
+    <id value="v2-0191"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74402,7 +74402,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0193"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0193"></id>
+    <id value="v2-0193"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74493,7 +74493,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0006/2.1"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="2.1"></id>
+    <id value="v2-2.1-0006"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74566,7 +74566,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0006/2.4"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="2.4"></id>
+    <id value="v2-2.4-0006"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74947,7 +74947,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0926"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0926"></id>
+    <id value="v2-0926"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -74999,7 +74999,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0927"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0927"></id>
+    <id value="v2-0927"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75048,7 +75048,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0922"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0922"></id>
+    <id value="v2-0922"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75097,7 +75097,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0923"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0923"></id>
+    <id value="v2-0923"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75146,7 +75146,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0924"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0924"></id>
+    <id value="v2-0924"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75213,7 +75213,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0925"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0925"></id>
+    <id value="v2-0925"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75302,7 +75302,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0920"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0920"></id>
+    <id value="v2-0920"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75353,7 +75353,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0921"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0921"></id>
+    <id value="v2-0921"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75402,7 +75402,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0933"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0933"></id>
+    <id value="v2-0933"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75494,7 +75494,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0935"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0935"></id>
+    <id value="v2-0935"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75570,7 +75570,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0904"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0904"></id>
+    <id value="v2-0904"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75622,7 +75622,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0905"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0905"></id>
+    <id value="v2-0905"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75683,7 +75683,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0906"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0906"></id>
+    <id value="v2-0906"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75780,7 +75780,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0907"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0907"></id>
+    <id value="v2-0907"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75873,7 +75873,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0909"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0909"></id>
+    <id value="v2-0909"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -75952,7 +75952,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0916"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0916"></id>
+    <id value="v2-0916"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76015,7 +76015,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0917"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0917"></id>
+    <id value="v2-0917"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76060,7 +76060,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0918"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0918"></id>
+    <id value="v2-0918"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76109,7 +76109,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0912"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0912"></id>
+    <id value="v2-0912"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76330,7 +76330,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0914"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0914"></id>
+    <id value="v2-0914"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76402,7 +76402,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0919"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0919"></id>
+    <id value="v2-0919"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76457,7 +76457,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0728"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0728"></id>
+    <id value="v2-0728"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76514,7 +76514,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0725"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0725"></id>
+    <id value="v2-0725"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76656,7 +76656,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0739"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0739"></id>
+    <id value="v2-0739"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76705,7 +76705,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0731"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0731"></id>
+    <id value="v2-0731"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76762,7 +76762,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0734"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0734"></id>
+    <id value="v2-0734"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -76839,7 +76839,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0702"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0702"></id>
+    <id value="v2-0702"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77049,7 +77049,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0717"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0717"></id>
+    <id value="v2-0717"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77138,7 +77138,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0719"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0719"></id>
+    <id value="v2-0719"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77203,7 +77203,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0527"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0527"></id>
+    <id value="v2-0527"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77304,7 +77304,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0528"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0528"></id>
+    <id value="v2-0528"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77393,7 +77393,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0529"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0529"></id>
+    <id value="v2-0529"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77508,7 +77508,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0523"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0523"></id>
+    <id value="v2-0523"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77561,7 +77561,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0524"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0524"></id>
+    <id value="v2-0524"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77628,7 +77628,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0761"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0761"></id>
+    <id value="v2-0761"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77685,7 +77685,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0520"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0520"></id>
+    <id value="v2-0520"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77734,7 +77734,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0763"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0763"></id>
+    <id value="v2-0763"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77783,7 +77783,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0538"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0538"></id>
+    <id value="v2-0538"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77840,7 +77840,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0534"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0534"></id>
+    <id value="v2-0534"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77929,7 +77929,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0776"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0776"></id>
+    <id value="v2-0776"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -77987,7 +77987,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0535"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0535"></id>
+    <id value="v2-0535"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78040,7 +78040,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0536"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0536"></id>
+    <id value="v2-0536"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78113,7 +78113,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0778"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0778"></id>
+    <id value="v2-0778"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78170,7 +78170,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0530"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0530"></id>
+    <id value="v2-0530"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78237,7 +78237,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0508"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0508"></id>
+    <id value="v2-0508"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78318,7 +78318,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0504"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0504"></id>
+    <id value="v2-0504"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78371,7 +78371,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0505"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0505"></id>
+    <id value="v2-0505"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78424,7 +78424,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0506"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0506"></id>
+    <id value="v2-0506"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78496,7 +78496,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0507"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0507"></id>
+    <id value="v2-0507"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78567,7 +78567,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0749"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0749"></id>
+    <id value="v2-0749"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78620,7 +78620,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0500"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0500"></id>
+    <id value="v2-0500"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78681,7 +78681,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0742"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0742"></id>
+    <id value="v2-0742"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78746,7 +78746,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0501"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0501"></id>
+    <id value="v2-0501"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78807,7 +78807,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0502"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0502"></id>
+    <id value="v2-0502"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78868,7 +78868,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0503"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0503"></id>
+    <id value="v2-0503"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78920,7 +78920,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0757"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0757"></id>
+    <id value="v2-0757"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -78969,7 +78969,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0516"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0516"></id>
+    <id value="v2-0516"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79046,7 +79046,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0517"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0517"></id>
+    <id value="v2-0517"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79099,7 +79099,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0759"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0759"></id>
+    <id value="v2-0759"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79152,7 +79152,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0518"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0518"></id>
+    <id value="v2-0518"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79210,7 +79210,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0511"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0511"></id>
+    <id value="v2-0511"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79271,7 +79271,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0513"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0513"></id>
+    <id value="v2-0513"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79328,7 +79328,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0755"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0755"></id>
+    <id value="v2-0755"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79377,7 +79377,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0514"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0514"></id>
+    <id value="v2-0514"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79490,7 +79490,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0510"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0510"></id>
+    <id value="v2-0510"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79604,7 +79604,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0329"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0329"></id>
+    <id value="v2-0329"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79657,7 +79657,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0561"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0561"></id>
+    <id value="v2-0561"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79731,7 +79731,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0324"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0324"></id>
+    <id value="v2-0324"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79864,7 +79864,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0566"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0566"></id>
+    <id value="v2-0566"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -79929,7 +79929,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0325"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0325"></id>
+    <id value="v2-0325"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80022,7 +80022,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0326"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0326"></id>
+    <id value="v2-0326"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80083,7 +80083,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0569"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0569"></id>
+    <id value="v2-0569"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80135,7 +80135,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0562"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0562"></id>
+    <id value="v2-0562"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80208,7 +80208,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0321"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0321"></id>
+    <id value="v2-0321"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80277,7 +80277,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0322"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0322"></id>
+    <id value="v2-0322"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80346,7 +80346,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0564"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0564"></id>
+    <id value="v2-0564"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80411,7 +80411,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0323"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0323"></id>
+    <id value="v2-0323"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80502,7 +80502,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0565"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0565"></id>
+    <id value="v2-0565"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80559,7 +80559,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0339"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0339"></id>
+    <id value="v2-0339"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80624,7 +80624,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0570"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0570"></id>
+    <id value="v2-0570"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80704,7 +80704,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0571"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0571"></id>
+    <id value="v2-0571"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80776,7 +80776,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0330"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0330"></id>
+    <id value="v2-0330"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80861,7 +80861,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0572"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0572"></id>
+    <id value="v2-0572"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -80906,7 +80906,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0335"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0335"></id>
+    <id value="v2-0335"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81194,7 +81194,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0336"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0336"></id>
+    <id value="v2-0336"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81263,7 +81263,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0337"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0337"></id>
+    <id value="v2-0337"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81316,7 +81316,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0338"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0338"></id>
+    <id value="v2-0338"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81452,7 +81452,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0331"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0331"></id>
+    <id value="v2-0331"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81521,7 +81521,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0332"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0332"></id>
+    <id value="v2-0332"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81574,7 +81574,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0334"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0334"></id>
+    <id value="v2-0334"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81655,7 +81655,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0548"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0548"></id>
+    <id value="v2-0548"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81724,7 +81724,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0309"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0309"></id>
+    <id value="v2-0309"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81793,7 +81793,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0544"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0544"></id>
+    <id value="v2-0544"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -81999,7 +81999,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0305"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0305"></id>
+    <id value="v2-0305"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -82116,7 +82116,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0547"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0547"></id>
+    <id value="v2-0547"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -82173,7 +82173,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0540"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0540"></id>
+    <id value="v2-0540"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -82234,7 +82234,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0301"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0301"></id>
+    <id value="v2-0301"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -82503,7 +82503,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0317"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0317"></id>
+    <id value="v2-0317"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -82560,7 +82560,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0559"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0559"></id>
+    <id value="v2-0559"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -82609,7 +82609,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0790"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0790"></id>
+    <id value="v2-0790"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -82654,7 +82654,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0550"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0550"></id>
+    <id value="v2-0550"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84489,7 +84489,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0555"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0555"></id>
+    <id value="v2-0555"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84581,7 +84581,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0556"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0556"></id>
+    <id value="v2-0556"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84626,7 +84626,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0315"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0315"></id>
+    <id value="v2-0315"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84703,7 +84703,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0557"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0557"></id>
+    <id value="v2-0557"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84768,7 +84768,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0316"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0316"></id>
+    <id value="v2-0316"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84861,7 +84861,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0558"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0558"></id>
+    <id value="v2-0558"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84914,7 +84914,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0793"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0793"></id>
+    <id value="v2-0793"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -84955,7 +84955,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0311"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0311"></id>
+    <id value="v2-0311"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -85040,7 +85040,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0553"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0553"></id>
+    <id value="v2-0553"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
@@ -85160,7 +85160,7 @@
   <fullUrl value="http://hl7.org/fhir/v2/0554"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="0554"></id>
+    <id value="v2-0554"></id>
     <meta>
      <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"></profile>
     </meta>
diff --git a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v3-codesystems.xml b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v3-codesystems.xml
index ca30c000c04..27f839f32f7 100644
--- a/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v3-codesystems.xml
+++ b/hapi-fhir-validation-resources-dstu3/src/main/resources/org/hl7/fhir/dstu3/model/valueset/v3-codesystems.xml
@@ -215,15 +215,15 @@
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Codes for the Role class hierarchy.  The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role.  Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains:    RoleClassOntological
-is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.   RoleClassPartitive
-collects roles in which the playing entity is in some sense a &quot;part&quot; of the scoping entity.   RoleClassAssociative
-collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:    RoleClassPassive
-which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.   RoleClassMutualRelationship
-which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto
-behavior.  Thus, this sub-domain is further divided into:    RoleClassRelationshipFormal
-in which the relationship is formally defined, frequently by a contract or agreement.   Personal relationship
-which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the  &quot;Personal relationship&quot; which is a leaf concept.  OpenIssue:
+    <description value=" Codes for the Role class hierarchy.  The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role.  Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains:    RoleClassOntological
+is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.   RoleClassPartitive
+collects roles in which the playing entity is in some sense a &quot;part&quot; of the scoping entity.   RoleClassAssociative
+collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:    RoleClassPassive
+which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.   RoleClassMutualRelationship
+which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto
+behavior.  Thus, this sub-domain is further divided into:    RoleClassRelationshipFormal
+in which the relationship is formally defined, frequently by a contract or agreement.   Personal relationship
+which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the  &quot;Personal relationship&quot; which is a leaf concept.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -424,7 +424,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Types of security policies that further specify the ActClassPolicy value set.  Examples:
+    <description value=" Types of security policies that further specify the ActClassPolicy value set.  Examples:
 encrypt prohibit redisclosure without consent directive"></description>
     <immutable value="false"></immutable>
     <compose>
@@ -1114,9 +1114,9 @@ encrypt prohibit redisclosure without consent directive"></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A set of codes specifying the modality by which the Entity playing the Role is participating in the Act.  Examples:
-Physically present, over the telephone, written communication.  Rationale:
-Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically.  Open Issue:
+    <description value=" A set of codes specifying the modality by which the Entity playing the Role is participating in the Act.  Examples:
+Physically present, over the telephone, written communication.  Rationale:
+Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically.  Open Issue:
 There needs to be a reexamination of the hierarchies as there seems to be some muddling between ELECTRONIC and other concepts that involve electronic communication that are in other hierarchies."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -1247,7 +1247,7 @@ There needs to be a reexamination of the hierarchies as there seems to be some m
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 A set of codes advising a system or user which name in a set of names to select for a given purpose."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -1369,7 +1369,7 @@ A set of codes advising a system or user which name in a set of names to select
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances.  Examples:
+    <description value=" Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances.  Examples:
 prohibit redisclosure without consent directive"></description>
     <immutable value="false"></immutable>
     <compose>
@@ -2055,7 +2055,7 @@ prohibit redisclosure without consent directive"></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Defines the timing and grouping of the response instances.  OpenIssue:
+    <description value=" Defines the timing and grouping of the response instances.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -2149,7 +2149,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity.  The kind of device is identified by the code attribute inherited from Entity.  Usage:
+    <description value=" A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity.  The kind of device is identified by the code attribute inherited from Entity.  Usage:
 This includes durable (reusable) medical equipment as well as disposable equipment."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -2409,7 +2409,7 @@ This includes durable (reusable) medical equipment as well as disposable equipme
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Concepts that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -2448,7 +2448,7 @@ Concepts that define the telecommunication capabilities of a particular device.
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing description."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -2728,7 +2728,7 @@ Missing description."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -2770,11 +2770,11 @@ Codes to specify the scope in which the identifier applies to the object with wh
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
-An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. Thecode
-attribute of Observation and thevalue
-attribute of Observation must be considered in combination to determine the semantics of the observation.  Discussion:
-Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a  variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter. As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology. An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations. Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation.  Examples:
+    <description value="  Description:
+An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. Thecode
+attribute of Observation and thevalue
+attribute of Observation must be considered in combination to determine the semantics of the observation.  Discussion:
+Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a  variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter. As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology. An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations. Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation.  Examples:
  Recording the results of a Family History Assessment  Laboratory test and associated result  Physical exam test and associated result  Device temperature  Soil lead level"></description>
     <immutable value="true"></immutable>
     <compose>
@@ -2818,7 +2818,7 @@ Structurally, many observations are name-value-pairs, where the Observation.code
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Definition:
+    <description value="  Definition:
 Defines the units associated with the magnitude of the maximum size limit of a query response that can be accepted by the requesting application."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -2861,7 +2861,7 @@ Defines the units associated with the magnitude of the maximum size limit of a q
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing Description"></description>
     <immutable value="true"></immutable>
     <compose>
@@ -3243,7 +3243,7 @@ Missing Description"></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type.  OpenIssue:
+    <description value=" This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be corrected.."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -3362,7 +3362,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Indicates that the receiver has messages for the sender  OpenIssue:
+    <description value=" Indicates that the receiver has messages for the sender  OpenIssue:
 Description does not make sense relative to name of coding system.  Must be reviewed and improved."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -3665,7 +3665,7 @@ Description does not make sense relative to name of coding system.  Must be revi
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Identifies allowed codes for HL7aTMs v3 conformance property."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -3757,8 +3757,8 @@ Identifies allowed codes for HL7aTMs v3 conformance property."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A value representing the level of proficiency in a language.  Example:
-Excellent, good, fair, poor.  OpenIssue:
+    <description value=" A value representing the level of proficiency in a language.  Example:
+Excellent, good, fair, poor.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -3800,7 +3800,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A code specifying the particular kind of Act that the Act-instance represents within its class.  Constraints:
+    <description value=" A code specifying the particular kind of Act that the Act-instance represents within its class.  Constraints:
 The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems.  The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code &quot;potassium&quot; together with and Act.classCode for &quot;laboratory observation&quot; to somehow mean &quot;potassium laboratory observation&quot; and then use the same Act.code for &quot;potassium&quot; together with Act.classCode for &quot;medication&quot; to mean &quot;substitution of potassium&quot;. This mutually modifying use of Act.code and Act.classCode is not permitted."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -3926,7 +3926,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing description."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -4103,8 +4103,8 @@ Missing description."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A value representing the method of expression of the language.  Example:
-Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.  OpenIssue:
+    <description value=" A value representing the method of expression of the language.  Example:
+Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -4190,7 +4190,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Definition:
+    <description value="  Definition:
 Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties."></description>
     <immutable value="false"></immutable>
     <compose>
@@ -4571,8 +4571,8 @@ Set of codes indicating the type of insurance policy or program that pays for th
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
-Used to enumerate the typical confidentiality constraints placed upon a clinical document.  Usage Note:
+    <description value="  Description:
+Used to enumerate the typical confidentiality constraints placed upon a clinical document.  Usage Note:
 x_BasicConfidentialityKind is a subset of Confidentiality codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization; that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject; or that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject."></description>
     <immutable value="false"></immutable>
     <compose>
@@ -4699,8 +4699,8 @@ x_BasicConfidentialityKind is a subset of Confidentiality codes that are used as
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Definition:
-A person playing the role of program eligible under a program based on military status.  Discussion:
+    <description value="  Definition:
+A person playing the role of program eligible under a program based on military status.  Discussion:
 This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot; or &quot;subscriber&quot; and the person's status as a member of the military meets jurisdictional or program criteria"></description>
     <immutable value="false"></immutable>
     <compose>
@@ -4747,7 +4747,7 @@ This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Definition:
+    <description value="  Definition:
 The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose  health information  for purposes such as research."></description>
     <immutable value="false"></immutable>
     <compose>
@@ -4795,7 +4795,7 @@ The type of consent directive, e.g., to consent or dissent to collect, access, o
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" This attribute contains an acknowledgement code as described in the HL7 message processing rules.  OpenIssue:
+    <description value=" This attribute contains an acknowledgement code as described in the HL7 message processing rules.  OpenIssue:
 Description was copied from attribute and needs to be improved to be appropriate for a code system."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -4838,9 +4838,9 @@ Description was copied from attribute and needs to be improved to be appropriate
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
-Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models)  and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms.  All affiliate realm codes may automatically be used as both binding realms and namespace realms.  Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms.  (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.)  All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm.  For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types.  It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes.  However, tooling does not currently support namepace realm codes greater than 2 characters.  Open Issue:
-The name of the concept property &quot;owningAffiliate&quot; should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code.  Open Issue:
+    <description value="  Description:
+Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models)  and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms.  All affiliate realm codes may automatically be used as both binding realms and namespace realms.  Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms.  (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.)  All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm.  For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types.  It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes.  However, tooling does not currently support namepace realm codes greater than 2 characters.  Open Issue:
+The name of the concept property &quot;owningAffiliate&quot; should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code.  Open Issue:
 In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -4934,7 +4934,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A named tag set for metadata used to populate a security category label field that &quot;segments&quot; an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System)  Usage Note:
+    <description value=" A named tag set for metadata used to populate a security category label field that &quot;segments&quot; an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System)  Usage Note:
 This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program.  Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment -  &quot;A division of data into isolated blocks with separate security controls for the purpose of reducing risk.&quot;"></description>
     <immutable value="false"></immutable>
     <compose>
@@ -5324,7 +5324,7 @@ This is the healthcare analog to the US Intelligence Community's concept of a Sp
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Types of personal relationships between two living subjects.  Example:
+    <description value=" Types of personal relationships between two living subjects.  Example:
 Parent, sibling, unrelated friend, neighbor"></description>
     <immutable value="false"></immutable>
     <compose>
@@ -5504,7 +5504,7 @@ Parent, sibling, unrelated friend, neighbor"></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Needs description"></description>
     <immutable value="true"></immutable>
     <compose>
@@ -5644,7 +5644,7 @@ Needs description"></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type &quot;has reason&quot; linking to another Act.  Examples:
+    <description value=" A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type &quot;has reason&quot; linking to another Act.  Examples:
 Example reasons that might qualify for being coded in this field might be: &quot;routine requirement&quot;, &quot;infectious disease reporting requirement&quot;, &quot;on patient request&quot;, &quot;required by law&quot;."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -5771,8 +5771,8 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A code identifying the specific message to be provided.  Discussion:
-A textual value may be specified as the print name, or for non-coded messages, as the original text.  Examples:
+    <description value=" A code identifying the specific message to be provided.  Discussion:
+A textual value may be specified as the print name, or for non-coded messages, as the original text.  Examples:
 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'"></description>
     <immutable value="true"></immutable>
     <compose>
@@ -5941,8 +5941,8 @@ A textual value may be specified as the print name, or for non-coded messages, a
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A code that provides additional detail about the means or technique used to ascertain the observation.  Examples:
-Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.  OpenIssue:
+    <description value=" A code that provides additional detail about the means or technique used to ascertain the observation.  Examples:
+Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified.  Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description.  Needs to be improved."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -6373,7 +6373,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Code that specifies whether an address part names the street, city, country, postal code, post box, etc. Discussion: The hierarchical nature of these concepts shows composition.  E.g. &quot;Street Name&quot; is part of &quot;Street Address Line&quot;"></description>
     <immutable value="true"></immutable>
     <compose>
@@ -6715,7 +6715,7 @@ Code that specifies whether an address part names the street, city, country, pos
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Identifies the order in which content should be processed."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -7212,7 +7212,7 @@ Identifies the order in which content should be processed."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -7309,7 +7309,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.  Examples:
+    <description value=" An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.  Examples:
 : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -7558,7 +7558,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 A task or action that a user may perform in a clinical information system."></description>
     <immutable value="false"></immutable>
     <compose>
@@ -7655,7 +7655,7 @@ A task or action that a user may perform in a clinical information system."></de
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" One or more codes specifying a rough qualitative interpretation of the observation, such as &quot;normal&quot;, &quot;abnormal&quot;, &quot;below normal&quot;, &quot;change up&quot;, &quot;resistant&quot;, &quot;susceptible&quot;, etc.  OpenIssue:
+    <description value=" One or more codes specifying a rough qualitative interpretation of the observation, such as &quot;normal&quot;, &quot;abnormal&quot;, &quot;below normal&quot;, &quot;change up&quot;, &quot;resistant&quot;, &quot;susceptible&quot;, etc.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified.  Note also that this might be identical to the V2 code system of interpretation codes (formerly Abnormal Flags in older versions)."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -7781,7 +7781,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may bede facto
+    <description value=" A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may bede facto
 behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children)."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -7831,7 +7831,7 @@ behavior (e.g. friends) or may be an incidental involvement with each other (e.g
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" * * * No description supplied * * *  Open Issue:
+    <description value=" * * * No description supplied * * *  Open Issue:
 The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -8000,7 +8000,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 A code specifying the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints to what kinds of Transmission objects can be related and in which way."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -8043,7 +8043,7 @@ A code specifying the meaning and purpose of every TransmissionRelationship inst
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -8082,7 +8082,7 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing description."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -8124,8 +8124,8 @@ Missing description."></description>
       <value value="http://www.hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Conveys the mandated workflow action that an information custodian, receiver, or user must perform.  Examples:
-encrypt  Usage Note:
+    <description value=" Conveys the mandated workflow action that an information custodian, receiver, or user must perform.  Examples:
+encrypt  Usage Note:
 Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision."></description>
     <immutable value="false"></immutable>
     <compose>
@@ -8261,7 +8261,7 @@ Per OASIS XACML, an obligation is an operation specified in a policy or policy t
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed.  Examples:
+    <description value=" A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed.  Examples:
 A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.)"></description>
     <immutable value="true"></immutable>
     <compose>
@@ -8430,7 +8430,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Indicates whether the name part is a given name, family name, prefix, suffix, etc."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -8699,7 +8699,7 @@ Indicates whether the name part is a given name, family name, prefix, suffix, et
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A jurisdictional mandate in the US relating to privacy.   Deprecation Comment:
+    <description value=" A jurisdictional mandate in the US relating to privacy.   Deprecation Comment:
 Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
     <immutable value="true"></immutable>
     <compose>
@@ -8756,7 +8756,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ActStatus"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActStatus"></id>
+    <id value="v3-ActStatus"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -8845,7 +8845,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
   <fullUrl value="http://hl7.org/fhir/v3/RelationalOperator"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RelationalOperator"></id>
+    <id value="v3-RelationalOperator"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -8924,7 +8924,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ModifyIndicator"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ModifyIndicator"></id>
+    <id value="v3-ModifyIndicator"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -8973,7 +8973,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ExposureMode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ExposureMode"></id>
+    <id value="v3-ExposureMode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -9047,7 +9047,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
   <fullUrl value="http://hl7.org/fhir/v3/PaymentTerms"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="PaymentTerms"></id>
+    <id value="v3-PaymentTerms"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -9106,7 +9106,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ContentProcessingMode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ContentProcessingMode"></id>
+    <id value="v3-ContentProcessingMode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -9133,7 +9133,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Identifies the order in which content should be processed."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ContentProcessingMode"></valueSet>
@@ -9156,7 +9156,7 @@ Identifies the order in which content should be processed."></description>
   <fullUrl value="http://hl7.org/fhir/v3/Charset"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="Charset"></id>
+    <id value="v3-Charset"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -9245,7 +9245,7 @@ Identifies the order in which content should be processed."></description>
   <fullUrl value="http://hl7.org/fhir/v3/DocumentStorage"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="DocumentStorage"></id>
+    <id value="v3-DocumentStorage"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -9304,7 +9304,7 @@ Identifies the order in which content should be processed."></description>
   <fullUrl value="http://hl7.org/fhir/v3/orderableDrugForm"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="orderableDrugForm"></id>
+    <id value="v3-orderableDrugForm"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -9331,7 +9331,7 @@ Identifies the order in which content should be processed."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing description."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-orderableDrugForm"></valueSet>
@@ -10213,7 +10213,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ProcessingMode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ProcessingMode"></id>
+    <id value="v3-ProcessingMode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -10272,7 +10272,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/TelecommunicationCapabilities"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TelecommunicationCapabilities"></id>
+    <id value="v3-TelecommunicationCapabilities"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -10299,7 +10299,7 @@ Missing description."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Concepts that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-TelecommunicationCapabilities"></valueSet>
@@ -10337,7 +10337,7 @@ Concepts that define the telecommunication capabilities of a particular device.
   <fullUrl value="http://hl7.org/fhir/v3/ObservationMethod"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ObservationMethod"></id>
+    <id value="v3-ObservationMethod"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -10364,8 +10364,8 @@ Concepts that define the telecommunication capabilities of a particular device.
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A code that provides additional detail about the means or technique used to ascertain the observation.  Examples:
-Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.  OpenIssue:
+    <description value=" A code that provides additional detail about the means or technique used to ascertain the observation.  Examples:
+Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified.  Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description.  Needs to be improved."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ObservationMethod"></valueSet>
@@ -10496,7 +10496,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
      <concept>
       <code value="VDOC"></code>
       <display value="document verification"></display>
-      <definition value="Verification by means of document.
+      <definition value="Verification by means of document.
 
         
          Example: Fax, letter, attachment to e-mail."></definition>
@@ -10504,7 +10504,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
      <concept>
       <code value="VREG"></code>
       <display value="registry verification"></display>
-      <definition value="verification by means of  a response to an electronic query
+      <definition value="verification by means of  a response to an electronic query
 
         
          Example: query message to a Covered Party registry application or Coverage Administrator."></definition>
@@ -10512,7 +10512,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
      <concept>
       <code value="VTOKEN"></code>
       <display value="electronic token verification"></display>
-      <definition value="Verification by means of electronic token.
+      <definition value="Verification by means of electronic token.
 
         
          Example: smartcard, magnetic swipe card, RFID device."></definition>
@@ -10520,7 +10520,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
      <concept>
       <code value="VVOICE"></code>
       <display value="voice-based verification"></display>
-      <definition value="Verification by means of voice.
+      <definition value="Verification by means of voice.
 
         
          Example: By speaking with or calling the Coverage Administrator or Covered Party"></definition>
@@ -11159,9 +11159,9 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
     <concept>
      <code value="0128"></code>
      <display value="Nucleic acid probe with amplification"></display>
-     <definition value="Molecular, Nucleic acid probe with amplification
+     <definition value="Molecular, Nucleic acid probe with amplification
 
-        
+        
 
         Rationale: Duplicate of code 0126. Use code 0126 instead."></definition>
     </concept>
@@ -11946,7 +11946,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
   <fullUrl value="http://hl7.org/fhir/v3/AddressPartType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AddressPartType"></id>
+    <id value="v3-AddressPartType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -11973,7 +11973,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note th
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Code that specifies whether an address part names the street, city, country, postal code, post box, etc. Discussion: The hierarchical nature of these concepts shows composition.  E.g. &quot;Street Name&quot; is part of &quot;Street Address Line&quot;"></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-AddressPartType"></valueSet>
@@ -12210,7 +12210,7 @@ Code that specifies whether an address part names the street, city, country, pos
   <fullUrl value="http://hl7.org/fhir/v3/RoleClass"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RoleClass"></id>
+    <id value="v3-RoleClass"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -12237,15 +12237,15 @@ Code that specifies whether an address part names the street, city, country, pos
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Codes for the Role class hierarchy.  The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role.  Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains:    RoleClassOntological
-is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.   RoleClassPartitive
-collects roles in which the playing entity is in some sense a &quot;part&quot; of the scoping entity.   RoleClassAssociative
-collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:    RoleClassPassive
-which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.   RoleClassMutualRelationship
-which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto
-behavior.  Thus, this sub-domain is further divided into:    RoleClassRelationshipFormal
-in which the relationship is formally defined, frequently by a contract or agreement.   Personal relationship
-which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the  &quot;Personal relationship&quot; which is a leaf concept.  OpenIssue:
+    <description value=" Codes for the Role class hierarchy.  The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role.  Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains:    RoleClassOntological
+is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.   RoleClassPartitive
+collects roles in which the playing entity is in some sense a &quot;part&quot; of the scoping entity.   RoleClassAssociative
+collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:    RoleClassPassive
+which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.   RoleClassMutualRelationship
+which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto
+behavior.  Thus, this sub-domain is further divided into:    RoleClassRelationshipFormal
+in which the relationship is formally defined, frequently by a contract or agreement.   Personal relationship
+which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the  &quot;Personal relationship&quot; which is a leaf concept.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-RoleClass"></valueSet>
@@ -12300,7 +12300,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="AFFL"></code>
          <display value="affiliate"></display>
-         <definition value="Player of the Affiliate role has a business/professional relationship with scoper.  Player and scoper may be persons or organization.  The Affiliate relationship does not imply membership in a group, nor does it exist for resource scheduling purposes.
+         <definition value="Player of the Affiliate role has a business/professional relationship with scoper.  Player and scoper may be persons or organization.  The Affiliate relationship does not imply membership in a group, nor does it exist for resource scheduling purposes.
 
         
          Example: A healthcare provider is affiliated with another provider as a business associate."></definition>
@@ -12353,24 +12353,24 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="COVPTY"></code>
          <display value="covered party"></display>
-         <definition value="A role class played by a person who receives benefit coverage under the terms of a particular insurance policy.  The underwriter of that policy is the scoping entity.  The covered party receives coverage because of some contractual or other relationship with the holder of that policy.
+         <definition value="A role class played by a person who receives benefit coverage under the terms of a particular insurance policy.  The underwriter of that policy is the scoping entity.  The covered party receives coverage because of some contractual or other relationship with the holder of that policy.
 
         
-         Discussion:This reason for coverage is captured in 'Role.code' and a relationship link with type code of indirect authority should be included using the policy holder role as the source, and the covered party role as the target.
+         Discussion:This reason for coverage is captured in 'Role.code' and a relationship link with type code of indirect authority should be included using the policy holder role as the source, and the covered party role as the target.
 
         Note that a particular policy may cover several individuals one of whom may be, but need not be, the policy holder.  Thus the notion of covered party is a role that is distinct from that of the policy holder."></definition>
          <concept>
           <code value="CLAIM"></code>
           <display value="claimant"></display>
-          <definition value="Description: A role played by a party making a claim for coverage under a policy or program.  A claimant must be either a person or organization, or a group of persons or organizations.  A claimant is not a named insured or a program eligible.
+          <definition value="Description: A role played by a party making a claim for coverage under a policy or program.  A claimant must be either a person or organization, or a group of persons or organizations.  A claimant is not a named insured or a program eligible.
 
         
-         Discussion: With respect to liability insurance such as property and casualty insurance, a claimant must file a claim requesting indemnification for a loss that the claimant considers covered under the policy of a named insured.  The claims adjuster for the policy underwriter will review the claim to determine whether the loss meets the benefit coverage criteria under a policy, and base any indemnification or coverage payment on that review.  If a third party is liable in whole or part for the loss, the underwriter may pursue third party liability recovery.  A claimant may be involved in civil or criminal legal proceedings involving claims against a defendant party that is indemnified by an insurance policy or to protest the finding of a claims adjustor. With respect to life insurance, a beneficiary designated by a named insured becomes a claimant of the proceeds of coverage, as in the case of a life insurance policy.  However, a claimant for coverage under life insurance is not necessarily a designated beneficiary.
+         Discussion: With respect to liability insurance such as property and casualty insurance, a claimant must file a claim requesting indemnification for a loss that the claimant considers covered under the policy of a named insured.  The claims adjuster for the policy underwriter will review the claim to determine whether the loss meets the benefit coverage criteria under a policy, and base any indemnification or coverage payment on that review.  If a third party is liable in whole or part for the loss, the underwriter may pursue third party liability recovery.  A claimant may be involved in civil or criminal legal proceedings involving claims against a defendant party that is indemnified by an insurance policy or to protest the finding of a claims adjustor. With respect to life insurance, a beneficiary designated by a named insured becomes a claimant of the proceeds of coverage, as in the case of a life insurance policy.  However, a claimant for coverage under life insurance is not necessarily a designated beneficiary.
 
         
-         Note: A claimant is not a named insured.  However, a named insured may make a claim under a policy, e.g., an insured driver may make a claim for an injury under his or her comprehensive automobile insurance policy.  Similarly, a program eligible may make a claim under program, e.g., an unemployed worker may claim benefits under an unemployment insurance program, but parties playing these covered party role classes are not, for purposes of this vocabulary and in an effort to clearly distinguish role classes, considered claimants.
+         Note: A claimant is not a named insured.  However, a named insured may make a claim under a policy, e.g., an insured driver may make a claim for an injury under his or her comprehensive automobile insurance policy.  Similarly, a program eligible may make a claim under program, e.g., an unemployed worker may claim benefits under an unemployment insurance program, but parties playing these covered party role classes are not, for purposes of this vocabulary and in an effort to clearly distinguish role classes, considered claimants.
 
-        In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that either a named insured or an individual insured has filed a claim for a loss.  In the case of a program eligible, a role type code INJWKR (injured worker) subtypes the class to indicate that the covered party in a workers compensation program is an injured worker, and as such, has filed a &quot;claim&quot; under the program for benefits.  Likewise, a covered role type code UNEMP (unemployed worker) subtypes the program eligible class to indicate that the covered party in an unemployment insurance program has filed a claim for unemployment benefits.
+        In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that either a named insured or an individual insured has filed a claim for a loss.  In the case of a program eligible, a role type code INJWKR (injured worker) subtypes the class to indicate that the covered party in a workers compensation program is an injured worker, and as such, has filed a &quot;claim&quot; under the program for benefits.  Likewise, a covered role type code UNEMP (unemployed worker) subtypes the program eligible class to indicate that the covered party in an unemployment insurance program has filed a claim for unemployment benefits.
 
         
          Example: A claimant under automobile policy that is not the named insured."></definition>
@@ -12378,23 +12378,23 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
          <concept>
           <code value="NAMED"></code>
           <display value="named insured"></display>
-          <definition value="Description: A role played by a party to an insurance policy to which the insurer agrees to indemnify for losses, provides benefits for, or renders services.  A named insured may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations.
+          <definition value="Description: A role played by a party to an insurance policy to which the insurer agrees to indemnify for losses, provides benefits for, or renders services.  A named insured may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations.
 
         
-         Discussion: The coded concept NAMED should not be used where a more specific child concept in this Specializable value set applies.  In some cases, the named insured may not be the policy holder, e.g., where a policy holder purchases life insurance policy in which another party is the named insured and the policy holder is the beneficiary of the policy.
+         Discussion: The coded concept NAMED should not be used where a more specific child concept in this Specializable value set applies.  In some cases, the named insured may not be the policy holder, e.g., where a policy holder purchases life insurance policy in which another party is the named insured and the policy holder is the beneficiary of the policy.
 
         
-         Note: The party playing the role of a named insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a named insured may make a claim under a policy, e.g., e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy e.g., if injured in an automobile accident and there is no liable third party.  In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that a named insured has filed a claim for a loss.
+         Note: The party playing the role of a named insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a named insured may make a claim under a policy, e.g., e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy e.g., if injured in an automobile accident and there is no liable third party.  In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that a named insured has filed a claim for a loss.
 
         
          Example: The named insured under a comprehensive automobile, disability, or property and casualty policy that is the named insured and may or may not be the policy holder."></definition>
           <concept>
            <code value="DEPEN"></code>
            <display value="dependent"></display>
-           <definition value="Description: A role played by a person covered under a policy or program based on an association with a subscriber, which is recognized by the policy holder.
+           <definition value="Description: A role played by a person covered under a policy or program based on an association with a subscriber, which is recognized by the policy holder.
 
         
-         Note:  The party playing the role of a dependent is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a dependent may make a claim under a policy, e.g., a dependent under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party.  In the case of a dependent making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the dependent has filed a claim for services covered under the health insurance policy.
+         Note:  The party playing the role of a dependent is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a dependent may make a claim under a policy, e.g., a dependent under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party.  In the case of a dependent making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the dependent has filed a claim for services covered under the health insurance policy.
 
         
          Example: The dependent has an association with the subscriber such as a financial dependency or personal relationship such as that of a spouse, or a natural or adopted child.  The policy holder may be required by law to recognize certain associations or may have discretion about the associations.  For example, a policy holder may dictate the criteria for the dependent status of adult children who are students, such as requiring full time enrollment, or may recognize domestic partners as dependents.  Under certain circumstances, the dependent may be under the indirect authority of a responsible party acting as a surrogate for the subscriber, for example, if the subscriber is differently abled or deceased, a guardian ad Lidem or estate executor may be appointed to assume the subscriberaTMs legal standing in the relationship with the dependent."></definition>
@@ -12402,10 +12402,10 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
           <concept>
            <code value="INDIV"></code>
            <display value="individual"></display>
-           <definition value="Description: A role played by a party covered under a policy as the policy holder.  An individual may be either a person or an organization.
+           <definition value="Description: A role played by a party covered under a policy as the policy holder.  An individual may be either a person or an organization.
 
         
-         Note: The party playing the role of an individual insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a named insured may make a claim under a policy, e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy if injured in an automobile accident and there is no liable third party.  In the case of an individual insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that an individual insured has filed a claim for a loss.
+         Note: The party playing the role of an individual insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a named insured may make a claim under a policy, e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy if injured in an automobile accident and there is no liable third party.  In the case of an individual insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that an individual insured has filed a claim for a loss.
 
         
          Example: The individual insured under a comprehensive automobile, disability, or property and casualty policy that is the policy holder."></definition>
@@ -12413,13 +12413,13 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
           <concept>
            <code value="SUBSCR"></code>
            <display value="subscriber"></display>
-           <definition value="Description: A role played by a person covered under a policy based on association with a sponsor who is the policy holder, and whose association may provide for the eligibility of dependents for coverage.
+           <definition value="Description: A role played by a person covered under a policy based on association with a sponsor who is the policy holder, and whose association may provide for the eligibility of dependents for coverage.
 
         
-         Discussion: The policy holder holds the contract with the policy or program underwriter.  The subscriber holds a certificate of coverage under the contract.  In legal proceedings concerning the policy or program, the terms of the contract takes precedence over the terms of the certificate of coverage if there are any inconsistencies.
+         Discussion: The policy holder holds the contract with the policy or program underwriter.  The subscriber holds a certificate of coverage under the contract.  In legal proceedings concerning the policy or program, the terms of the contract takes precedence over the terms of the certificate of coverage if there are any inconsistencies.
 
         
-         Note: The party playing the role of a subscriber is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a subscriber may make a claim under a policy, e.g., a subscriber under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party.  In the case of a subscriber making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the subscriber has filed a claim for services covered under the health insurance policy.
+         Note: The party playing the role of a subscriber is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However, a subscriber may make a claim under a policy, e.g., a subscriber under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party.  In the case of a subscriber making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the subscriber has filed a claim for services covered under the health insurance policy.
 
         
          Example: An employee or a member of an association."></definition>
@@ -12428,15 +12428,15 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
          <concept>
           <code value="PROG"></code>
           <display value="program eligible"></display>
-          <definition value="Description: A role played by a party that meets the eligibility criteria for coverage under a program.  A program eligible may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations.
+          <definition value="Description: A role played by a party that meets the eligibility criteria for coverage under a program.  A program eligible may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations.
 
         
-         Discussion: A program as typically government administered coverage for parties determined eligible under the terms of the program.
+         Discussion: A program as typically government administered coverage for parties determined eligible under the terms of the program.
 
         
-         Note: The party playing a program eligible is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However a program eligible may make a claim under program, e.g., an unemployed worker may claim benefits under an unemployment insurance program, but parties playing these covered party role classes are not, for purposes of this vocabulary and in an effort to clearly distinguish role classes, considered claimants.
+         Note: The party playing a program eligible is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant).  However a program eligible may make a claim under program, e.g., an unemployed worker may claim benefits under an unemployment insurance program, but parties playing these covered party role classes are not, for purposes of this vocabulary and in an effort to clearly distinguish role classes, considered claimants.
 
-        In the case of a program eligible, a role type code INJWKR (injured worker) subtypes the class to indicate that the covered party in a workers compensation program is an injured worker, and as such, has filed a &quot;claim&quot; under the program for benefits.  Likewise, a covered role type code UNEMP (unemployed worker) subtypes the program eligible class to indicate that the covered party in an unemployment insurance program has filed a claim for unemployment benefits.
+        In the case of a program eligible, a role type code INJWKR (injured worker) subtypes the class to indicate that the covered party in a workers compensation program is an injured worker, and as such, has filed a &quot;claim&quot; under the program for benefits.  Likewise, a covered role type code UNEMP (unemployed worker) subtypes the program eligible class to indicate that the covered party in an unemployment insurance program has filed a claim for unemployment benefits.
 
         
          Example: A party meeting eligibility criteria related to health or financial status, e.g., in the U.S., persons meeting health, demographic, or financial criteria established by state and federal law are eligible for Medicaid."></definition>
@@ -12479,7 +12479,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
          <concept>
           <code value="RESBJ"></code>
           <display value="research subject"></display>
-          <definition value="Definition:Specifies the administrative functionality within a formal experimental design for which the ResearchSubject role was established.
+          <definition value="Definition:Specifies the administrative functionality within a formal experimental design for which the ResearchSubject role was established.
 
         
          Examples: Screening - role is used for pre-enrollment evaluation portion of the design; enrolled - role is used for subjects admitted to the experimental portion of the design."></definition>
@@ -12503,7 +12503,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="PAT"></code>
          <display value="patient"></display>
-         <definition value="A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper).
+         <definition value="A Role of a LivingSubject (player) as an actual or potential recipient of health care services from a healthcare provider organization (scoper).
 
         
          Usage Note: Communication about relationships between patients and specific healthcare practitioners (people) is not done via scoper.  Instead this is generally done using the CareProvision act.  This allows linkage between patient and a particular healthcare practitioner role and also allows description of the type of care involved in the relationship."></definition>
@@ -12521,10 +12521,10 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="POLHOLD"></code>
          <display value="policy holder"></display>
-         <definition value="A role played by a person or organization that holds an insurance policy.  The underwriter of that policy is the scoping entity.
+         <definition value="A role played by a person or organization that holds an insurance policy.  The underwriter of that policy is the scoping entity.
 
         
-         Discussion:The identifier of the policy is captured in 'Role.id' when the Role is a policy holder.
+         Discussion:The identifier of the policy is captured in 'Role.id' when the Role is a policy holder.
 
         A particular policy may cover several individuals one of whom may be, but need not be, the policy holder.  Thus the notion of covered party is a role that is distinct from that of the policy holder."></definition>
         </concept>
@@ -12536,23 +12536,23 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="SPNSR"></code>
          <display value="coverage sponsor"></display>
-         <definition value="A role played by an entity, usually an organization that is the sponsor of an insurance plan or a health program. A sponsor is the party that is ultimately accountable for the coverage by employment contract or by law.  A sponsor can be an employer, union, government agency, or association.  Fully insured sponsors establish the terms of the plan and contract with health insurance plans to assume the risk and to administer the plan.  Self-insured sponsors delegate coverage administration, but not risk, to third-party administrators.  Program sponsors designate services to be covered in accordance with statute.   Program sponsors may administer the coverage themselves, delegate coverage administration, but not risk to third-party administrators, or contract with health insurance plans to assume the risk and administrator a program. Sponsors qualify individuals who may become 
+         <definition value="A role played by an entity, usually an organization that is the sponsor of an insurance plan or a health program. A sponsor is the party that is ultimately accountable for the coverage by employment contract or by law.  A sponsor can be an employer, union, government agency, or association.  Fully insured sponsors establish the terms of the plan and contract with health insurance plans to assume the risk and to administer the plan.  Self-insured sponsors delegate coverage administration, but not risk, to third-party administrators.  Program sponsors designate services to be covered in accordance with statute.   Program sponsors may administer the coverage themselves, delegate coverage administration, but not risk to third-party administrators, or contract with health insurance plans to assume the risk and administrator a program. Sponsors qualify individuals who may become 
 
         
          
-          a policy holder of the plan;
+          a policy holder of the plan;
 
          
          
-          where the sponsor is the policy holder, who may become a subscriber or a dependent to a policy under the plan; or
+          where the sponsor is the policy holder, who may become a subscriber or a dependent to a policy under the plan; or
 
          
          
-          where the sponsor is a government agency, who may become program eligibles under a program. 
+          where the sponsor is a government agency, who may become program eligibles under a program. 
 
          
         
-        The sponsor role may be further qualified by the SponsorRole.code.  Entities playing the sponsor role may also play the role of a Coverage Administrator.
+        The sponsor role may be further qualified by the SponsorRole.code.  Entities playing the sponsor role may also play the role of a Coverage Administrator.
 
         
          Example: An employer, union, government agency, or association."></definition>
@@ -12565,33 +12565,33 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="UNDWRT"></code>
          <display value="underwriter"></display>
-         <definition value="A role played by a person or an organization.  It is the party that 
+         <definition value="A role played by a person or an organization.  It is the party that 
 
         
          
-          accepts fiscal responsibility for insurance plans and the policies created under those plans;
+          accepts fiscal responsibility for insurance plans and the policies created under those plans;
 
          
          
-          administers and accepts fiscal responsibility for a program that provides coverage for services to eligible individuals; and/or
+          administers and accepts fiscal responsibility for a program that provides coverage for services to eligible individuals; and/or
 
          
          
-          has the responsibility to assess the merits of each risk and decide a suitable premium for accepting all or part of the risk.  If played by an organization, this role may be further specified by an appropriate RoleCode.
+          has the responsibility to assess the merits of each risk and decide a suitable premium for accepting all or part of the risk.  If played by an organization, this role may be further specified by an appropriate RoleCode.
 
          
         
         
          Example:
-        
+        
 
         
          
-          A health insurer; 
+          A health insurer; 
 
          
          
-          Medicaid Program;
+          Medicaid Program;
 
          
          
@@ -12611,17 +12611,17 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
        <concept>
         <code value="SELF"></code>
         <display value="self"></display>
-        <definition value="The &quot;same&quot; roleclass asserts an identity between playing and scoping entities: that they are in fact instances of the same entity and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.
+        <definition value="The &quot;same&quot; roleclass asserts an identity between playing and scoping entities: that they are in fact instances of the same entity and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.
 
         
          Usage:
-        
+        
 
-        playing and scoping entities must have same classcode, but need not have identical attributes or values. 
+        playing and scoping entities must have same classcode, but need not have identical attributes or values. 
 
         
          Example: 
-        
+        
 
         a provider registry maintains sets of conflicting demographic data for what is reported to be the same individual."></definition>
         <property>
@@ -12646,30 +12646,30 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
        <concept>
         <code value="ADJY"></code>
         <display value="adjacency"></display>
-        <definition value="A physical association whereby two Entities are in some (even lose) spatial relationship with each other such that they touch each other in some way.
+        <definition value="A physical association whereby two Entities are in some (even lose) spatial relationship with each other such that they touch each other in some way.
 
         
-         Examples: the colon is connected (and therefore adjacent) to the jejunum; the colon is adjacent to the liver (even if not actually connected.)
+         Examples: the colon is connected (and therefore adjacent) to the jejunum; the colon is adjacent to the liver (even if not actually connected.)
 
         
          UsageConstraints: Adjacency is in principle a symmetrical connection, but scoper and player of the role should, where applicable, be assigned to have scoper be the larger, more central Entity and player the smaller, more distant, appendage."></definition>
         <concept>
          <code value="CONC"></code>
          <display value="connection"></display>
-         <definition value="An adjacency of two Entities held together by a bond which attaches to each of the two entities. 
+         <definition value="An adjacency of two Entities held together by a bond which attaches to each of the two entities. 
 
         
-         Examples: biceps brachii muscle connected to the radius bone, port 3 on a network switch connected to port 5 on a patch panel.
+         Examples: biceps brachii muscle connected to the radius bone, port 3 on a network switch connected to port 5 on a patch panel.
 
         
          UsageConstraints: See Adjacency for the assignment of scoper (larger, more central) and player (smaller, more distant)."></definition>
          <concept>
           <code value="BOND"></code>
           <display value="molecular bond"></display>
-          <definition value="A connection between two atoms of a molecule.
+          <definition value="A connection between two atoms of a molecule.
 
         
-         Examples: double bond between first and second C in ethane, peptide bond between two amino-acid, disulfide bridge between two proteins, chelate and ion associations, even the much weaker van-der-Waals bonds can be considered molecular bonds.
+         Examples: double bond between first and second C in ethane, peptide bond between two amino-acid, disulfide bridge between two proteins, chelate and ion associations, even the much weaker van-der-Waals bonds can be considered molecular bonds.
 
         
          UsageConstraints: See connection and adjacency for the assignment of player and scoper."></definition>
@@ -12677,10 +12677,10 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
          <concept>
           <code value="CONY"></code>
           <display value="continuity"></display>
-          <definition value="A connection between two regional parts.
+          <definition value="A connection between two regional parts.
 
         
-         Examples:  the connection between ascending aorta and the aortic arc, connection between descending colon and sigmoid.
+         Examples:  the connection between ascending aorta and the aortic arc, connection between descending colon and sigmoid.
 
         
          UsageConstraints: See connection and adjacency for the assignment of player and scoper."></definition>
@@ -12735,7 +12735,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
        <concept>
         <code value="EXPR"></code>
         <display value="exposed entity"></display>
-        <definition value="A role played by an entity that has been exposed to a person or animal suffering a contagious disease, or with a location from which a toxin has been distributed.  The player of the role is normally a person or animal, but it is possible that other entity types could become exposed.  The role is scoped by the source of the exposure, and it is quite possible for a person playing the role of exposed party to also become the scoper a role played by another person.  That is to say, once a person has become infected, it is possible, perhaps likely, for that person to infect others.
+        <definition value="A role played by an entity that has been exposed to a person or animal suffering a contagious disease, or with a location from which a toxin has been distributed.  The player of the role is normally a person or animal, but it is possible that other entity types could become exposed.  The role is scoped by the source of the exposure, and it is quite possible for a person playing the role of exposed party to also become the scoper a role played by another person.  That is to say, once a person has become infected, it is possible, perhaps likely, for that person to infect others.
 
         Management of exposures and tracking exposed parties is a key function within public health, and within most public health contexts - exposed parties are known as &quot;contacts.&quot;"></definition>
        </concept>
@@ -12777,7 +12777,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
        <concept>
         <code value="RGPR"></code>
         <display value="regulated product"></display>
-        <definition value="A product regulated by some governmentatl orgnization.  The role is played by Material and scoped by Organization.
+        <definition value="A product regulated by some governmentatl orgnization.  The role is played by Material and scoped by Organization.
 
         Rationale: To support an entity clone used to identify the NDC number for a drug product."></definition>
        </concept>
@@ -12809,34 +12809,34 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="EQUIV"></code>
        <display value="equivalent entity"></display>
-       <definition value="Description: Specifies the player Entity (the equivalent Entity) as an Entity that is considered to be equivalent to a reference Entity (scoper).  The equivalence is in principle a symmetric relationship, however, it is expected that the scoper is a reference entity which serves as reference entity for multiple different equivalent entities. 
+       <definition value="Description: Specifies the player Entity (the equivalent Entity) as an Entity that is considered to be equivalent to a reference Entity (scoper).  The equivalence is in principle a symmetric relationship, however, it is expected that the scoper is a reference entity which serves as reference entity for multiple different equivalent entities. 
 
         
          Examples: An innovator's medicine formulation is the reference for &quot;generics&quot;, i.e., formulations manufactured differently but having been proven to be biologically equivalent to the reference medicine. Another example is a reference ingredient that serves as basis for quantity specifications (basis of strength, e.g., metoprolol succinate specified in terms of metoprolol tartrate.)"></definition>
        <concept>
         <code value="SAME"></code>
         <display value="same"></display>
-        <definition value="The &quot;same&quot; role asserts an identity between playing and scoping entities, i.e., that they are in fact two records of the same entity instance, and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.
+        <definition value="The &quot;same&quot; role asserts an identity between playing and scoping entities, i.e., that they are in fact two records of the same entity instance, and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.
 
         
          Usage:
-        
+        
 
-        playing and scoping entities must have same classCode, but need not have identical attributes or values.
+        playing and scoping entities must have same classCode, but need not have identical attributes or values.
 
         
          Example: 
-        
+        
 
         a provider registry maintains sets of conflicting demographic data for what is reported to be the same individual."></definition>
        </concept>
        <concept>
         <code value="SUBY"></code>
         <display value="subsumed by"></display>
-        <definition value="Relates a prevailing record of an Entity (scoper) with another record (player) that it subsumes.
+        <definition value="Relates a prevailing record of an Entity (scoper) with another record (player) that it subsumes.
 
         
-         Examples: Show a correct new Person object (scoper) that subsumes one or more duplicate Person objects that had accidentally been created for the same physical person.
+         Examples: Show a correct new Person object (scoper) that subsumes one or more duplicate Person objects that had accidentally been created for the same physical person.
 
         
          Constraints: Both the player and scoper must have the same classCode."></definition>
@@ -12860,7 +12860,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="SUBS"></code>
        <display value="subsumer"></display>
-       <definition value="An entity that subsumes the identity of another.  Used in the context of merging documented entity instances. Both the player and scoper must have the same classCode.
+       <definition value="An entity that subsumes the identity of another.  Used in the context of merging documented entity instances. Both the player and scoper must have the same classCode.
 
         The use of this code is deprecated in favor of the term SUBY which is its inverse and is more ontologically correct."></definition>
        <property>
@@ -12912,7 +12912,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="ACTIB"></code>
          <display value="active ingredient - basis of strength"></display>
-         <definition value="Description:  Active ingredient, where the ingredient substance (player) is itself the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies exactly the quantity of the player substance in the medicine formulation. 
+         <definition value="Description:  Active ingredient, where the ingredient substance (player) is itself the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies exactly the quantity of the player substance in the medicine formulation. 
 
         
          Examples: Lopressor 50 mg actually contains 50 mg of metoprolol succinate, even though the active moiety is metoprolol,  but also: Tenormin 50 mg contain 50 mg of atenolol, as free base, i.e., where the active ingredient atenolol is also the active moiety."></definition>
@@ -12920,7 +12920,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="ACTIM"></code>
          <display value="active ingredient - moiety is basis of strength"></display>
-         <definition value="Description: Active ingredient, where not the ingredient substance (player), but itaTMs active moiety is the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies the quantity of the player substance's active moiety in the medicine formulation.
+         <definition value="Description: Active ingredient, where not the ingredient substance (player), but itaTMs active moiety is the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies the quantity of the player substance's active moiety in the medicine formulation.
 
         
          Examples: 1 mL of Betopic 5mg/mL eye drops contains 5.6 mg betaxolol hydrochloride equivalent to betaxolol base 5 mg."></definition>
@@ -12928,7 +12928,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
         <concept>
          <code value="ACTIR"></code>
          <display value="active ingredient - reference substance is basis of strength"></display>
-         <definition value="Description: Active ingredient, where not the ingredient substance (player) but another reference substance with the same active moiety, is the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies the quantity of a reference substance, similar but different from the player substance's in the medicine formulation.
+         <definition value="Description: Active ingredient, where not the ingredient substance (player) but another reference substance with the same active moiety, is the &quot;basis of strength&quot;, i.e., where the Role.quantity specifies the quantity of a reference substance, similar but different from the player substance's in the medicine formulation.
 
         
          Examples: Toprol-XL 50 mg contains 47.5 mg of metoprolol succinate equivalent to 50 mg of metoprolol tartrate."></definition>
@@ -12982,7 +12982,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
        <concept>
         <code value="MECH"></code>
         <display value="mechanical ingredient"></display>
-        <definition value="An ingredient (player) of a medication (scoper) that is inseparable from the active ingredients, but has no intended chemical or pharmaceutical effect itself, but which may have some systemic effect on the patient.
+        <definition value="An ingredient (player) of a medication (scoper) that is inseparable from the active ingredients, but has no intended chemical or pharmaceutical effect itself, but which may have some systemic effect on the patient.
 
         An example is a collagen matrix used as a base for transplanting skin cells.  The collagen matrix can be left permanently in the graft site.  Because it is of bovine origin, the patient may exhibit allergies or may have cultural objections to its use."></definition>
        </concept>
@@ -13000,21 +13000,21 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="MBR"></code>
        <display value="member"></display>
-       <definition value="A role played by an entity that is a member of a group.  The group provides the scope for this role.
+       <definition value="A role played by an entity that is a member of a group.  The group provides the scope for this role.
 
         Among other uses, groups as used in insurance (groups of covered individuals) and in scheduling where resources may be grouped for scheduling and logistical purposes."></definition>
       </concept>
       <concept>
        <code value="PART"></code>
        <display value="part"></display>
-       <definition value="Definition:  an association between two Entities where the playing Entity (the part) is a component of the whole (scoper) in the sense of an integral structural component, that is distinct from other parts in the same whole, has a distinct function in the whole, and, as an effect, the full integrity of the whole depends (to some degree) on the presence of this part, even though the part may often be separable from the whole.
+       <definition value="Definition:  an association between two Entities where the playing Entity (the part) is a component of the whole (scoper) in the sense of an integral structural component, that is distinct from other parts in the same whole, has a distinct function in the whole, and, as an effect, the full integrity of the whole depends (to some degree) on the presence of this part, even though the part may often be separable from the whole.
 
         
          Discussion: Part is defined in opposition to (a) ingredient (not separable), (b) content (not a functional component), and (c) member (not functionally distinct from other members)."></definition>
        <concept>
         <code value="ACTM"></code>
         <display value="active moiety"></display>
-        <definition value="The molecule or ion that is responsible for the intended pharmacological action of the drug substance, excluding those appended or associated parts of the molecule that make the molecule an ester, salt (including a salt with hydrogen or coordination bonds), or other noncovalent derivative (such as a complex, chelate, or clathrate).
+        <definition value="The molecule or ion that is responsible for the intended pharmacological action of the drug substance, excluding those appended or associated parts of the molecule that make the molecule an ester, salt (including a salt with hydrogen or coordination bonds), or other noncovalent derivative (such as a complex, chelate, or clathrate).
 
         Examples: heparin-sodium and heparin-potassium have the same active moiety, heparin; the active moiety of morphine-hydrochloride is morphine."></definition>
        </concept>
@@ -13097,7 +13097,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/EntityClass"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityClass"></id>
+    <id value="v3-EntityClass"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13199,7 +13199,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
        <concept>
         <code value="DEV"></code>
         <display value="device"></display>
-        <definition value="A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity.  The kind of device is identified by the code attribute inherited from Entity.
+        <definition value="A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity.  The kind of device is identified by the code attribute inherited from Entity.
 
         
          Usage: This includes durable (reusable) medical equipment as well as disposable equipment."></definition>
@@ -13274,7 +13274,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/AcknowledgementDetailCode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AcknowledgementDetailCode"></id>
+    <id value="v3-AcknowledgementDetailCode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13301,7 +13301,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing description."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailCode"></valueSet>
@@ -13464,7 +13464,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/Calendar"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="Calendar"></id>
+    <id value="v3-Calendar"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13508,7 +13508,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/GenderStatus"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="GenderStatus"></id>
+    <id value="v3-GenderStatus"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13557,7 +13557,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/IdentifierReliability"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="IdentifierReliability"></id>
+    <id value="v3-IdentifierReliability"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13611,7 +13611,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/QueryParameterValue"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="QueryParameterValue"></id>
+    <id value="v3-QueryParameterValue"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13752,7 +13752,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ResponseLevel"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ResponseLevel"></id>
+    <id value="v3-ResponseLevel"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13826,7 +13826,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/LivingArrangement"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="LivingArrangement"></id>
+    <id value="v3-LivingArrangement"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13925,7 +13925,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/DeviceAlertLevel"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="DeviceAlertLevel"></id>
+    <id value="v3-DeviceAlertLevel"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -13984,7 +13984,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/AmericanIndianAlaskaNativeLanguages"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AmericanIndianAlaskaNativeLanguages"></id>
+    <id value="v3-AmericanIndianAlaskaNativeLanguages"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -15688,7 +15688,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ResponseModality"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ResponseModality"></id>
+    <id value="v3-ResponseModality"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -15715,7 +15715,7 @@ Missing description."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Defines the timing and grouping of the response instances.  OpenIssue:
+    <description value=" Defines the timing and grouping of the response instances.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ResponseModality"></valueSet>
@@ -15743,7 +15743,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/ReligiousAffiliation"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ReligiousAffiliation"></id>
+    <id value="v3-ReligiousAffiliation"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -16192,7 +16192,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/AcknowledgementDetailType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AcknowledgementDetailType"></id>
+    <id value="v3-AcknowledgementDetailType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -16219,8 +16219,8 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A code identifying the specific message to be provided.  Discussion:
-A textual value may be specified as the print name, or for non-coded messages, as the original text.  Examples:
+    <description value=" A code identifying the specific message to be provided.  Discussion:
+A textual value may be specified as the print name, or for non-coded messages, as the original text.  Examples:
 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'"></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailType"></valueSet>
@@ -16235,7 +16235,7 @@ A textual value may be specified as the print name, or for non-coded messages, a
     <concept>
      <code value="E"></code>
      <display value="Error"></display>
-     <definition value="Definition:An issue which has prevented, or will prevent (unless a management is provided for the issue by the sender), the successful processing of an interaction.  Response interactions which include an issue which is an Error are a 'rejection', indicating that the request was not successfully processed. 
+     <definition value="Definition:An issue which has prevented, or will prevent (unless a management is provided for the issue by the sender), the successful processing of an interaction.  Response interactions which include an issue which is an Error are a 'rejection', indicating that the request was not successfully processed. 
 
         
          Example:Unable to find specified patient."></definition>
@@ -16243,7 +16243,7 @@ A textual value may be specified as the print name, or for non-coded messages, a
     <concept>
      <code value="I"></code>
      <display value="Information"></display>
-     <definition value="Definition: The message relates to an issue which has no bearing on the successful processing of the request.  Information issues cannot be overridden by specifying a management.
+     <definition value="Definition: The message relates to an issue which has no bearing on the successful processing of the request.  Information issues cannot be overridden by specifying a management.
 
         
          Example: A Patient's coverage will expire in 5 days."></definition>
@@ -16251,11 +16251,11 @@ A textual value may be specified as the print name, or for non-coded messages, a
     <concept>
      <code value="W"></code>
      <display value="Warning"></display>
-     <definition value="Definition: The message relates to an issue which cannot prevent the successful processing of a request, but which could result in the processing not having the ideal or intended effect.  Managing a warning issue is not required for successful processing, but will suppress the warning from being raised. 
+     <definition value="Definition: The message relates to an issue which cannot prevent the successful processing of a request, but which could result in the processing not having the ideal or intended effect.  Managing a warning issue is not required for successful processing, but will suppress the warning from being raised. 
 
         
          Example:
-        
+        
 
         Unexpected additional repetitions of phone number have been ignored."></definition>
     </concept>
@@ -16287,7 +16287,7 @@ A textual value may be specified as the print name, or for non-coded messages, a
   <fullUrl value="http://hl7.org/fhir/v3/TableCellVerticalAlign"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TableCellVerticalAlign"></id>
+    <id value="v3-TableCellVerticalAlign"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -16346,7 +16346,7 @@ A textual value may be specified as the print name, or for non-coded messages, a
   <fullUrl value="http://hl7.org/fhir/v3/ProbabilityDistributionType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ProbabilityDistributionType"></id>
+    <id value="v3-ProbabilityDistributionType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -16430,7 +16430,7 @@ A textual value may be specified as the print name, or for non-coded messages, a
   <fullUrl value="http://hl7.org/fhir/v3/MaritalStatus"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="MaritalStatus"></id>
+    <id value="v3-MaritalStatus"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -16457,7 +16457,7 @@ A textual value may be specified as the print name, or for non-coded messages, a
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" * * * No description supplied * * *  Open Issue:
+    <description value=" * * * No description supplied * * *  Open Issue:
 The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-MaritalStatus"></valueSet>
@@ -16520,7 +16520,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/substanceAdminSubstitution"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="substanceAdminSubstitution"></id>
+    <id value="v3-substanceAdminSubstitution"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -16574,9 +16574,9 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <code value="EC"></code>
        <display value="equivalent composition"></display>
        <definition value="Description: 
-        
+        
 
-        Substitution occurred or is permitted with another product that is a:
+        Substitution occurred or is permitted with another product that is a:
 
         
          pharmaceutical alternative containing the same active ingredient but is formulated with different salt, ester
@@ -16584,7 +16584,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         
         
          Examples: 
-        
+        
 
         
          
@@ -16595,13 +16595,13 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         <code value="BC"></code>
         <display value="brand composition"></display>
         <definition value="Description: 
-        
+        
 
-        Substitution occurred or is permitted between equivalent Brands but not Generics
+        Substitution occurred or is permitted between equivalent Brands but not Generics
 
         
          Examples: 
-        
+        
 
         
          Zestril  for Prinivil
@@ -16610,11 +16610,11 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <concept>
         <code value="G"></code>
         <display value="generic composition"></display>
-        <definition value="Description: Substitution occurred or is permitted between equivalent Generics but not Brands
+        <definition value="Description: Substitution occurred or is permitted between equivalent Generics but not Brands
 
         
          Examples: 
-        
+        
 
         
          Lisnopril (Lupin Corp) for Lisnopril (Wockhardt Corp)"></definition>
@@ -16623,21 +16623,21 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="TE"></code>
        <display value="therapeutic alternative"></display>
-       <definition value="Description: Substitution occurred or is permitted with another product having the same therapeutic objective and safety profile.
+       <definition value="Description: Substitution occurred or is permitted with another product having the same therapeutic objective and safety profile.
 
         
          Examples: 
-        
+        
 
         
          ranitidine for Tagamet"></definition>
        <concept>
         <code value="TB"></code>
         <display value="therapeutic brand"></display>
-        <definition value="Description: Substitution occurred or is permitted between therapeutically equivalent Brands but not Generics
+        <definition value="Description: Substitution occurred or is permitted between therapeutically equivalent Brands but not Generics
 &gt;
          Examples: 
-        
+        
 
         
          Zantac for Tagamet"></definition>
@@ -16645,10 +16645,10 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <concept>
         <code value="TG"></code>
         <display value="therapeutic generic"></display>
-        <definition value="Description: Substitution occurred or is permitted between therapeutically equivalent Generics but not Brands
+        <definition value="Description: Substitution occurred or is permitted between therapeutically equivalent Generics but not Brands
 &gt;
          Examples: 
-        
+        
 
         
          Ranitidine  for cimetidine"></definition>
@@ -16673,7 +16673,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/VaccineManufacturer"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="VaccineManufacturer"></id>
+    <id value="v3-VaccineManufacturer"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -16912,7 +16912,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/Race"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="Race"></id>
+    <id value="v3-Race"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -21556,7 +21556,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/TargetAwareness"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TargetAwareness"></id>
+    <id value="v3-TargetAwareness"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -21625,7 +21625,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/TribalEntityUS"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TribalEntityUS"></id>
+    <id value="v3-TribalEntityUS"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -24518,7 +24518,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/MapRelationship"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="MapRelationship"></id>
+    <id value="v3-MapRelationship"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -24572,7 +24572,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/QueryStatusCode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="QueryStatusCode"></id>
+    <id value="v3-QueryStatusCode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -24636,7 +24636,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/ActRelationshipType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActRelationshipType"></id>
+    <id value="v3-ActRelationshipType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -24683,7 +24683,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
     <concept>
      <code value="ART"></code>
      <display value="act relationship type"></display>
-     <definition value="Description: A directed association between a source Act and a target Act.
+     <definition value="Description: A directed association between a source Act and a target Act.
 
         
          Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute)"></definition>
@@ -24715,18 +24715,18 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <concept>
         <code value="CHRG"></code>
         <display value="has charge"></display>
-        <definition value="A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source).  A clinical act may have a charge associated with the execution or delivery of the service.
+        <definition value="A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source).  A clinical act may have a charge associated with the execution or delivery of the service.
 
-        The financial transaction will define the charge (bill) for delivery or performance of the service.
+        The financial transaction will define the charge (bill) for delivery or performance of the service.
 
         Charges and costs are distinct terms.  A charge defines what is charged or billed to another organization or entity within an organization.  The cost defines what it costs an organization to perform or deliver a service or product."></definition>
        </concept>
        <concept>
         <code value="COST"></code>
         <display value="has cost"></display>
-        <definition value="A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source).  A clinical act may have an inherit cost associated with the execution or delivery of the service.
+        <definition value="A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source).  A clinical act may have an inherit cost associated with the execution or delivery of the service.
 
-        The financial transaction will define the cost of delivery or performance of the service.
+        The financial transaction will define the cost of delivery or performance of the service.
 
         Charges and costs are distinct terms.  A charge defines what is charged or billed to another organization or entity within an organization.  The cost defines what it costs an organization to perform or deliver a service or product."></definition>
        </concept>
@@ -24772,7 +24772,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="RSON"></code>
        <display value="has reason"></display>
-       <definition value="Description: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action.  As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication.  Child concepts may be used to describe types of indication. 
+       <definition value="Description: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action.  As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication.  Child concepts may be used to describe types of indication. 
 
         
          Discussion: In prior releases, the code &quot;SUGG&quot; (suggests) was expressed as &quot;an inversion of the reason link.&quot; That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship."></definition>
@@ -24845,7 +24845,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="TRIG"></code>
        <display value="has trigger"></display>
-       <definition value="A pre-condition that if true should result in the source Act being executed.  The target is in typically in criterion mood.  When reported after the fact (i.e. the criterion has been met) it may be in Event mood.  A delay between the trigger and the triggered action can be specified.
+       <definition value="A pre-condition that if true should result in the source Act being executed.  The target is in typically in criterion mood.  When reported after the fact (i.e. the criterion has been met) it may be in Event mood.  A delay between the trigger and the triggered action can be specified.
 
         
          Discussion: This includes the concept of a  required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded."></definition>
@@ -24870,21 +24870,21 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <concept>
         <code value="ENE"></code>
         <display value="ends near end"></display>
-        <definition value="A relationship in which the source act's effective time ends near the end of the target act's effective time. Near is defined separately as a time interval.
+        <definition value="A relationship in which the source act's effective time ends near the end of the target act's effective time. Near is defined separately as a time interval.
 
         
          Usage Note: Inverse code is ENS"></definition>
         <concept>
          <code value="ECW"></code>
          <display value="ends concurrent with"></display>
-         <definition value="A relationship in which the source act's effective time ends with the end of the target act's effective time.
+         <definition value="A relationship in which the source act's effective time ends with the end of the target act's effective time.
 
         
          UsageNote: This code is reflexive.  Therefore its inverse code is itself."></definition>
          <concept>
           <code value="CONCURRENT"></code>
           <display value="concurrent with"></display>
-          <definition value="A relationship in which the source act's effective time is the same as the target act's effective time.
+          <definition value="A relationship in which the source act's effective time is the same as the target act's effective time.
 
         
          UsageNote: This code is reflexive.  Therefore its inverse code is itself."></definition>
@@ -24892,7 +24892,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          <concept>
           <code value="SBSECWE"></code>
           <display value="starts before start of, ends with"></display>
-          <definition value="The source Act starts before the start of the target Act, and ends with the target Act.
+          <definition value="The source Act starts before the start of the target Act, and ends with the target Act.
 
         
          UsageNote: Inverse code is SASECWE"></definition>
@@ -24902,14 +24902,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <concept>
         <code value="ENS"></code>
         <display value="ends near start"></display>
-        <definition value="A relationship in which the source act's effective time ends near the start of the target act's effective time. Near is defined separately as a time interval.
+        <definition value="A relationship in which the source act's effective time ends near the start of the target act's effective time. Near is defined separately as a time interval.
 
         
          Usage Note: Inverse code is ENE"></definition>
         <concept>
          <code value="ECWS"></code>
          <display value="ends concurrent with start of"></display>
-         <definition value="The source Act ends when the target act starts (i.e. if we say &quot;ActOne ECWS ActTwo&quot;, it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target).
+         <definition value="The source Act ends when the target act starts (i.e. if we say &quot;ActOne ECWS ActTwo&quot;, it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target).
 
         
          UsageNote: Inverse code is SCWE"></definition>
@@ -24918,14 +24918,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <concept>
         <code value="SNE"></code>
         <display value="starts near end"></display>
-        <definition value="A relationship in which the source act's effective time starts near the end of the target act's effective time. Near is defined separately as a time interval.
+        <definition value="A relationship in which the source act's effective time starts near the end of the target act's effective time. Near is defined separately as a time interval.
 
         
          Usage Note: Inverse code is SNS"></definition>
         <concept>
          <code value="SCWE"></code>
          <display value="starts concurrent with end of"></display>
-         <definition value="The source Act starts when the target act ends (i.e. if we say &quot;ActOne SCWE ActTwo&quot;, it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target).
+         <definition value="The source Act starts when the target act ends (i.e. if we say &quot;ActOne SCWE ActTwo&quot;, it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target).
 
         
          UsageNote: Inverse code is SBSECWS"></definition>
@@ -24934,7 +24934,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        <concept>
         <code value="SNS"></code>
         <display value="starts near start"></display>
-        <definition value="A relationship in which the source act's effective time starts near the start of the target act's effective time. Near is defined separately as a time interval.
+        <definition value="A relationship in which the source act's effective time starts near the start of the target act's effective time. Near is defined separately as a time interval.
 
         
          Usage Note: Inverse code is SNE"></definition>
@@ -24944,14 +24944,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          </modifierExtension>
          <code value="SCW"></code>
          <display value="starts concurrent with"></display>
-         <definition value="A relationship in which the source act's effective time starts with the start of the target act's effective time.
+         <definition value="A relationship in which the source act's effective time starts with the start of the target act's effective time.
 
         
          UsageNote: This code is reflexive.  Therefore its inverse code is itself."></definition>
          <concept>
           <code value="SCWSEBE"></code>
           <display value="starts with. ends before end of"></display>
-          <definition value="The source Act starts with.the target Act and ends before the end of the target Act.
+          <definition value="The source Act starts with.the target Act and ends before the end of the target Act.
 
         
          UsageNote: Inverse code is SCWSEAE"></definition>
@@ -24967,14 +24967,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="EAS"></code>
        <display value="ends after start of"></display>
-       <definition value="A relationship in which the source act ends after the target act starts.
+       <definition value="A relationship in which the source act ends after the target act starts.
 
         
          UsageNote: Inverse code is SBE"></definition>
        <concept>
         <code value="EAE"></code>
         <display value="ends after end of"></display>
-        <definition value="A relationship in which the source act ends after the target act ends.
+        <definition value="A relationship in which the source act ends after the target act ends.
 
         
          UsageNote: Inverse code is EBE"></definition>
@@ -24984,7 +24984,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          </modifierExtension>
          <code value="SASEAE"></code>
          <display value="starts after start of, ends after end of"></display>
-         <definition value="The source Act starts after start of the target Act and ends after end of the target Act.
+         <definition value="The source Act starts after start of the target Act and ends after end of the target Act.
 
         
          UsageNote: Inverse code is SBSEBE"></definition>
@@ -24994,14 +24994,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
           </modifierExtension>
           <code value="SBEEAE"></code>
           <display value="contains end of"></display>
-          <definition value="The source Act contains the end of the target Act.
+          <definition value="The source Act contains the end of the target Act.
 
         
          UsageNote: Inverse code is EDU"></definition>
           <concept>
            <code value="SASSBEEAS"></code>
            <display value="start after start of, contains end of"></display>
-           <definition value="The source Act start after the start of the target Act, and contains the end of the target Act.
+           <definition value="The source Act start after the start of the target Act, and contains the end of the target Act.
 
         
          UsageNote: Inverse code is SBSEASEBE"></definition>
@@ -25009,7 +25009,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
           <concept>
            <code value="SBSEAE"></code>
            <display value="contains time of"></display>
-           <definition value="The source Act contains the time of the target Act.
+           <definition value="The source Act contains the time of the target Act.
 
         
          UsageNote: Inverse code is DURING"></definition>
@@ -25023,14 +25023,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         </modifierExtension>
         <code value="SAS"></code>
         <display value="starts after start of"></display>
-        <definition value="The source Act starts after the start of the target Act (i.e. if we say &quot;ActOne SAS ActTwo&quot;, it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).
+        <definition value="The source Act starts after the start of the target Act (i.e. if we say &quot;ActOne SAS ActTwo&quot;, it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).
 
         
          UsageNote: Inverse code is SBS"></definition>
         <concept>
          <code value="SAE"></code>
          <display value="starts after end of"></display>
-         <definition value="A relationship in which the source act starts after the target act ends.
+         <definition value="A relationship in which the source act starts after the target act ends.
 
         
          UsageNote: Inverse code is EBS"></definition>
@@ -25038,7 +25038,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         <concept>
          <code value="DURING"></code>
          <display value="occurs during"></display>
-         <definition value="A relationship in which the source act's effective time is wholly within the target act's effective time (including end points, as defined in the act's effective times)
+         <definition value="A relationship in which the source act's effective time is wholly within the target act's effective time (including end points, as defined in the act's effective times)
 
         
          UsageNote: Inverse code is SBSEAE"></definition>
@@ -25046,7 +25046,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         <concept>
          <code value="SASECWE"></code>
          <display value="starts after start of, ends with"></display>
-         <definition value="The source Act starts after start of the target Act, and ends with the target Act.
+         <definition value="The source Act starts after start of the target Act, and ends with the target Act.
 
         
          UsageNote: Inverse code is SBSECWE"></definition>
@@ -25062,7 +25062,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        </modifierExtension>
        <code value="EASORECWS"></code>
        <display value="ends after or concurrent with start of"></display>
-       <definition value="A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time.
+       <definition value="A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time.
 
         
          Usage Note: Inverse code is EBSORECWS"></definition>
@@ -25075,7 +25075,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         </modifierExtension>
         <code value="EAEORECW"></code>
         <display value="ends after or concurrent with end of"></display>
-        <definition value="A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time.
+        <definition value="A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time.
 
         
          Usage Note: Inverse code is EBEORECW"></definition>
@@ -25084,7 +25084,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="INDEPENDENT"></code>
        <display value="independent of time of"></display>
-       <definition value="The source Act is independent of the time of the target Act.
+       <definition value="The source Act is independent of the time of the target Act.
 
         
          UsageNote: This code is reflexive.  Therefore its inverse code is itself."></definition>
@@ -25098,7 +25098,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        </modifierExtension>
        <code value="SAEORSCWE"></code>
        <display value="starts after or concurrent with end of"></display>
-       <definition value="A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time.
+       <definition value="A relationship in which the source act's effective time starts after or concurrent with the end of the target act's effective time.
 
         
          Usage Note: Inverse code is SBEORSCWE"></definition>
@@ -25112,7 +25112,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
        </modifierExtension>
        <code value="SASORSCW"></code>
        <display value="starts after or concurrent with start of"></display>
-       <definition value="A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time.
+       <definition value="A relationship in which the source act's effective time starts after or concurrent with the start of the target act's effective time.
 
         
          Usage Note: Inverse code is SBSORSCW"></definition>
@@ -25120,7 +25120,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="SBEORSCWE"></code>
        <display value="starts before or concurrent with end of"></display>
-       <definition value="A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time.
+       <definition value="A relationship in which the source act's effective time starts before or concurrent with the end of the target act's effective time.
 
         
          Usage Note: Inverse code is SAEORSCWE"></definition>
@@ -25139,7 +25139,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         </modifierExtension>
         <code value="OVERLAP"></code>
         <display value="overlaps with"></display>
-        <definition value="A relationship in which the source act's effective time overlaps the target act's effective time in any way.
+        <definition value="A relationship in which the source act's effective time overlaps the target act's effective time in any way.
 
         
          UsageNote: This code is reflexive.  Therefore its inverse code is itself."></definition>
@@ -25149,14 +25149,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          </modifierExtension>
          <code value="EDU"></code>
          <display value="ends during"></display>
-         <definition value="A relationship in which the source act ends within the target act's effective time (including end points, as defined in the act's effective times)
+         <definition value="A relationship in which the source act ends within the target act's effective time (including end points, as defined in the act's effective times)
 
         
          UsageNote: Inverse code is SBEEAE"></definition>
          <concept>
           <code value="SBSEASEBE"></code>
           <display value="contains start of, ends before end of"></display>
-          <definition value="The source Act contains the start of the target Act,  and ends before the end of the target Act.
+          <definition value="The source Act contains the start of the target Act,  and ends before the end of the target Act.
 
         
          UsageNote: Inverse code is SASSBEEAS"></definition>
@@ -25174,7 +25174,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          </modifierExtension>
          <code value="SBSEAS"></code>
          <display value="contains start of"></display>
-         <definition value="The source Act contains the start of the target Act.
+         <definition value="The source Act contains the start of the target Act.
 
         
          UsageNote: Inverse code is SDU"></definition>
@@ -25185,7 +25185,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          </modifierExtension>
          <code value="SDU"></code>
          <display value="starts during"></display>
-         <definition value="A relationship in which the source act starts within the target act's effective time (including end points, as defined in the act's effective times)
+         <definition value="A relationship in which the source act starts within the target act's effective time (including end points, as defined in the act's effective times)
 
         
          UsageNote: Inverse code is SBSEAS"></definition>
@@ -25200,14 +25200,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
         </modifierExtension>
         <code value="SBE"></code>
         <display value="starts before end of"></display>
-        <definition value="The source Act starts before the end of the target Act (i.e. if we say &quot;ActOne SBE ActTwo&quot;, it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).
+        <definition value="The source Act starts before the end of the target Act (i.e. if we say &quot;ActOne SBE ActTwo&quot;, it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).
 
         
          UsageNote: Inverse code is EAS"></definition>
         <concept>
          <code value="EBE"></code>
          <display value="ends before end of"></display>
-         <definition value="The source Act ends before the end of the target Act (i.e. if we say &quot;ActOne EBE ActTwo&quot;, it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).
+         <definition value="The source Act ends before the end of the target Act (i.e. if we say &quot;ActOne EBE ActTwo&quot;, it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).
 
         
          UsageNote: Inverse code is EAE"></definition>
@@ -25217,7 +25217,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
           </modifierExtension>
           <code value="SBSEBE"></code>
           <display value="starts before start of, ends before end of"></display>
-          <definition value="The source Act starts before the start of the target Act, and ends before the end of the target Act.
+          <definition value="The source Act starts before the start of the target Act, and ends before the end of the target Act.
 
         
          UsageNote: Inverse code is SASEAE"></definition>
@@ -25227,14 +25227,14 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
            </modifierExtension>
            <code value="EBSORECWS"></code>
            <display value="ends before or concurrent with start of"></display>
-           <definition value="A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time.
+           <definition value="A relationship in which the source act's effective time ends before or concurrent with the start of the target act's effective time.
 
         
          Usage Note: Inverse code is EASORECWS"></definition>
            <concept>
             <code value="EBS"></code>
             <display value="ends before start of"></display>
-            <definition value="A relationship in which the source act ends before the target act starts.
+            <definition value="A relationship in which the source act ends before the target act starts.
 
         
          UsageNote: Inverse code is SAE"></definition>
@@ -25251,7 +25251,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          </modifierExtension>
          <code value="EBEORECW"></code>
          <display value="ends before or concurrent with end of"></display>
-         <definition value="A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time.
+         <definition value="A relationship in which the source act's effective time ends before or concurrent with the end of the target act's effective time.
 
         
          Usage Note: Inverse code is EAEORECW"></definition>
@@ -25262,7 +25262,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
          </modifierExtension>
          <code value="SBSORSCW"></code>
          <display value="starts before or concurrent with start of"></display>
-         <definition value="A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time.
+         <definition value="A relationship in which the source act's effective time starts before or concurrent with the start of the target act's effective time.
 
         
          Usage Note: Inverse code is SASORSCW"></definition>
@@ -25275,7 +25275,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
           </modifierExtension>
           <code value="SBS"></code>
           <display value="starts before start of"></display>
-          <definition value="A relationship in which the source act begins before the target act begins.
+          <definition value="A relationship in which the source act begins before the target act begins.
 
         
          UsageNote: Inverse code is SAS"></definition>
@@ -25292,11 +25292,11 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
      <concept>
       <code value="CAUS"></code>
       <display value="is etiology for"></display>
-      <definition value="Description: An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act.
+      <definition value="Description: An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act.
 
         
          Examples:
-        
+        
 
         
          a growth of Staphylococcus aureus may be considered the cause of an abscess
@@ -25315,19 +25315,19 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="MBR"></code>
        <display value="has member"></display>
-       <definition value="The target Acts are aggregated by the source Act.  Target Acts may have independent existence, participate in multiple ActRelationships, and do not contribute to the meaning of the source.
+       <definition value="The target Acts are aggregated by the source Act.  Target Acts may have independent existence, participate in multiple ActRelationships, and do not contribute to the meaning of the source.
 
         
-         UsageNotes: This explicitly represents the conventional notion of aggregation.  The target Act is part of a collection of Acts (no implication is made of cardinality, a source of Acts may contain zero, one, or more member target Acts).
+         UsageNotes: This explicitly represents the conventional notion of aggregation.  The target Act is part of a collection of Acts (no implication is made of cardinality, a source of Acts may contain zero, one, or more member target Acts).
 
         It is expected that this will be primarily used with _ActClassRecordOrganizer, BATTERY, and LIST"></definition>
        <concept>
         <code value="STEP"></code>
         <display value="has step"></display>
-        <definition value="A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.
+        <definition value="A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.
 
         
-         UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via  ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode.
+         UsageNotes: Sequence of steps may be indicated by use of _ActRelationshipTemporallyPertains, as well as via  ActRelationship.sequenceNumber, ActRelationship.pauseQuantity, Target.priorityCode.
 
         
          OpenIssue: Need Additional guidelines on when each approach should be used."></definition>
@@ -25346,7 +25346,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="PART"></code>
        <display value="has part"></display>
-       <definition value="The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act.
+       <definition value="The source Act is a composite of the target Acts. The target Acts do not have an existence independent of the source Act.
 
         
          UsageNote: In UML 1.1, this is a &quot;composition&quot; defined as: 
@@ -25371,7 +25371,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
      <concept>
       <code value="EVID"></code>
       <display value="provides evidence for"></display>
-      <definition value="Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a 'reason' for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc.
+      <definition value="Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a 'reason' for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc.
 
         
          Rationale: Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies."></definition>
@@ -25389,7 +25389,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
      <concept>
       <code value="INTF"></code>
       <display value="interfered by"></display>
-      <definition value="the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act.
+      <definition value="the target act documents a set of circumstances (events, risks) which prevent successful completion, or degradation of quality of, the source Act.
 
         
          UsageNote: This provides the semantics to document barriers to care"></definition>
@@ -25407,7 +25407,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
      <concept>
       <code value="META"></code>
       <display value="has metadata"></display>
-      <definition value="Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act.
+      <definition value="Definition: Indicates that the attributes and associations of the target act provide metadata (for example, identifiers, authorship, etc.) for the source act.
 
         
          Constraint:  Source act must have either a mood code that is not &quot;EVN&quot; (event) or its &quot;isCriterion&quot; attribute must set to &quot;true&quot;.  Target act must be an Act with a mood code of EVN and with isCriterionInd attribute set to &quot;true&quot;."></definition>
@@ -25473,10 +25473,10 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="USE"></code>
        <display value="uses"></display>
-       <definition value="Indicates that the source act makes use of (or will make use of) the information content of the target act.
+       <definition value="Indicates that the source act makes use of (or will make use of) the information content of the target act.
 
         
-         UsageNotes: A usage relationship only makes sense if the target act is authored and occurs independently of the source act.  Otherwise a simpler relationship such as COMP would be appropriate.
+         UsageNotes: A usage relationship only makes sense if the target act is authored and occurs independently of the source act.  Otherwise a simpler relationship such as COMP would be appropriate.
 
         
          Rationale: There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications.  This is stronger than the assertion of &quot;references&quot;.  References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference."></definition>
@@ -25504,7 +25504,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="BSLN"></code>
        <display value="has baseline"></display>
-       <definition value="Indicates that the target observation(s) provide an initial reference for the source observation or observation group.
+       <definition value="Indicates that the target observation(s) provide an initial reference for the source observation or observation group.
 
         
          UsageConstraints: Both source and target must be Observations or specializations thereof."></definition>
@@ -25512,7 +25512,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="COMPLY"></code>
        <display value="complies with"></display>
-       <definition value="Description:The source act complies with, adheres to, conforms to, or is permissible under (in whole or in part) the policy, contract, agreement, law, conformance criteria, certification guidelines or requirement conveyed by the target act.
+       <definition value="Description:The source act complies with, adheres to, conforms to, or is permissible under (in whole or in part) the policy, contract, agreement, law, conformance criteria, certification guidelines or requirement conveyed by the target act.
 
         Examples for compliance relationships are: audits of adherence with a security policy, certificate of conformance to system certification requirements, or consent directive in compliance with or permissible under a privacy policy."></definition>
       </concept>
@@ -25559,12 +25559,12 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="MOD"></code>
        <display value="modifies"></display>
-       <definition value="Definition: Used to link a newer version or 'snapshot' of a business object (source) to an older version or 'snapshot' of the same business object (target).
+       <definition value="Definition: Used to link a newer version or 'snapshot' of a business object (source) to an older version or 'snapshot' of the same business object (target).
 
         
-         Usage:The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead.
+         Usage:The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead.
 
-        Name from source to target = &quot;modifiesPrior&quot;
+        Name from source to target = &quot;modifiesPrior&quot;
 
         Name from target to source = &quot;modifiesByNew&quot;"></definition>
       </concept>
@@ -25576,11 +25576,11 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="OPTN"></code>
        <display value="has option"></display>
-       <definition value="A relationship between a source Act that provides more detailed properties to the target Act.
+       <definition value="A relationship between a source Act that provides more detailed properties to the target Act.
 
-        The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements.
+        The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements.
 
-        The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements.
+        The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements.
 
         Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options."></definition>
       </concept>
@@ -25592,9 +25592,9 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <concept>
        <code value="REV"></code>
        <display value="reverses"></display>
-       <definition value="A relationship between a source Act that seeks to reverse or undo the action of the prior target Act.
+       <definition value="A relationship between a source Act that seeks to reverse or undo the action of the prior target Act.
 
-        Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction.
+        Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction.
 
         Constraints: the &quot;completion track&quot; mood of the target Act must be equally or more &quot;actual&quot; than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT."></definition>
       </concept>
@@ -25642,35 +25642,35 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
      <concept>
       <code value="SUBJ"></code>
       <display value="has subject"></display>
-      <definition value="Relates an Act to its subject Act that the first Act is primarily concerned with.
+      <definition value="Relates an Act to its subject Act that the first Act is primarily concerned with.
 
-        Examples
+        Examples
 
         
          
-          The first Act may be a ControlAct manipulating the subject Act 
+          The first Act may be a ControlAct manipulating the subject Act 
 
          
          
-          The first act is a region of interest (ROI) that defines a region within the subject Act.
+          The first act is a region of interest (ROI) that defines a region within the subject Act.
 
          
          
-          The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.
+          The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.
 
          
         
-        Constraints
+        Constraints
 
-        An Act may have multiple subject acts.
+        An Act may have multiple subject acts.
 
-        Rationale
+        Rationale
 
         The ActRelationshipType &quot;has subject&quot; is similar to the ParticipationType &quot;subject&quot;, Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship."></definition>
       <concept>
        <code value="QUALF"></code>
        <display value="has qualifier"></display>
-       <definition value="The target observation qualifies (refines) the semantics of the source observation.
+       <definition value="The target observation qualifies (refines) the semantics of the source observation.
 
         
          UsageNote: This is not intended to replace concept refinement and qualification via vocabulary.  It is used when there are multiple components which together provide the complete understanding of the source Act."></definition>
@@ -25684,15 +25684,15 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
      <concept>
       <code value="VALUE"></code>
       <display value="has value"></display>
-      <definition value="Description:Indicates that the target Act represents the result of the source observation Act.
+      <definition value="Description:Indicates that the target Act represents the result of the source observation Act.
 
         
-         FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified
+         FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified
 
         
-         UsageNote: This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute.  For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation.
+         UsageNote: This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute.  For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation.
 
-        The valueNegationInd attribute on the source Act has the same semantics of &quot;negated finding&quot; when it applies to the target of a VALUE ActRelationship as it does to the value attribute.  On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding.  Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd.
+        The valueNegationInd attribute on the source Act has the same semantics of &quot;negated finding&quot; when it applies to the target of a VALUE ActRelationship as it does to the value attribute.  On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding.  Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd.
 
         
          OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation."></definition>
@@ -25746,7 +25746,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/RoleLinkType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RoleLinkType"></id>
+    <id value="v3-RoleLinkType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -25784,7 +25784,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
     <concept>
      <code value="REL"></code>
      <display value="related"></display>
-     <definition value="An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be undesirable.
+     <definition value="An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be undesirable.
 
         Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.Examples:"></definition>
      <concept>
@@ -25830,7 +25830,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
   <fullUrl value="http://hl7.org/fhir/v3/TransmissionRelationshipTypeCode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TransmissionRelationshipTypeCode"></id>
+    <id value="v3-TransmissionRelationshipTypeCode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -25857,7 +25857,7 @@ The specific meanings of these codes can vary somewhat by jurisdiction and imple
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 A code specifying the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints to what kinds of Transmission objects can be related and in which way."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-TransmissionRelationshipTypeCode"></valueSet>
@@ -25875,7 +25875,7 @@ A code specifying the meaning and purpose of every TransmissionRelationship inst
   <fullUrl value="http://hl7.org/fhir/v3/SetOperator"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="SetOperator"></id>
+    <id value="v3-SetOperator"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -25954,7 +25954,7 @@ A code specifying the meaning and purpose of every TransmissionRelationship inst
   <fullUrl value="http://hl7.org/fhir/v3/EntityHandling"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityHandling"></id>
+    <id value="v3-EntityHandling"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26083,7 +26083,7 @@ A code specifying the meaning and purpose of every TransmissionRelationship inst
   <fullUrl value="http://hl7.org/fhir/v3/EntityRisk"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityRisk"></id>
+    <id value="v3-EntityRisk"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26177,7 +26177,7 @@ A code specifying the meaning and purpose of every TransmissionRelationship inst
   <fullUrl value="http://hl7.org/fhir/v3/ParticipationSignature"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ParticipationSignature"></id>
+    <id value="v3-ParticipationSignature"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26204,7 +26204,7 @@ A code specifying the meaning and purpose of every TransmissionRelationship inst
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed.  Examples:
+    <description value=" A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed.  Examples:
 A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.)"></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ParticipationSignature"></valueSet>
@@ -26232,7 +26232,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/ActMood"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActMood"></id>
+    <id value="v3-ActMood"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26301,7 +26301,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <concept>
        <code value="DEF"></code>
        <display value="definition"></display>
-       <definition value="Definition: A definition of a kind of act that can occur .
+       <definition value="Definition: A definition of a kind of act that can occur .
 
         
          OpenIssue: The semantic constructs embodied in DEF and CRT moods seem indistinguishable, and their uses can readily be determined by the context in which these are used. Therefore, this OpenIssue has been created to declare that it is likely that ActMood.DEF will be &quot;retired&quot; in the future in favor of the more general ActMood.CRT."></definition>
@@ -26325,7 +26325,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
      <concept>
       <code value="INT"></code>
       <display value="intent"></display>
-      <definition value="Definition: An intention or plan for an act. 
+      <definition value="Definition: An intention or plan for an act. 
 
         
          &gt;UsageNotes: The final outcome of the intent, the act that is intended to occur, is always an event. However the final outcome may be reached indirectly via steps through other intents, such as promise, permission request, or an appointment that may lead to an actual event to occur. Alternatively, the intended act may never occur."></definition>
@@ -26340,7 +26340,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="_ActMoodActRequest"></code>
         <display value="act request"></display>
-        <definition value="Definition: A request (or order) for an act that is part of a defined request/fulfillment cycle.
+        <definition value="Definition: A request (or order) for an act that is part of a defined request/fulfillment cycle.
 
         
          UsageNotes: Use of an HL7 defined request/fulfillment framework is not required to use this mood code."></definition>
@@ -26361,15 +26361,15 @@ A surgical Procedure act object (representing a procedure report) requires a sig
         <concept>
          <code value="RQO"></code>
          <display value="request"></display>
-         <definition value="Definition: A request act that is specialized for an event request/fulfillment cycle. 
+         <definition value="Definition: A request act that is specialized for an event request/fulfillment cycle. 
 
         
-         UsageNotes: The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event. 
+         UsageNotes: The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event. 
 
         
-         UsageNotes: The concepts of a &quot;request&quot; and an &quot;order&quot; are viewed as different, because there is an implication of a mandate associated with order.  In practice, however, this distinction has no general functional value in the inter-operation of health care computing.  &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; obligates the recipient (the fulfiller) to respond to the sender (the author).  Indeed, in many regions, including Australia and Europe, the common term used is &quot;request.&quot;
+         UsageNotes: The concepts of a &quot;request&quot; and an &quot;order&quot; are viewed as different, because there is an implication of a mandate associated with order.  In practice, however, this distinction has no general functional value in the inter-operation of health care computing.  &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; obligates the recipient (the fulfiller) to respond to the sender (the author).  Indeed, in many regions, including Australia and Europe, the common term used is &quot;request.&quot;
 
-        Thus, the concept embodies both notions, as there is no useful distinction to be made.  If a mandate is to be associated with a request, this will be embodied in the &quot;local&quot; business rules applied to the transactions.  Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.
+        Thus, the concept embodies both notions, as there is no useful distinction to be made.  If a mandate is to be associated with a request, this will be embodied in the &quot;local&quot; business rules applied to the transactions.  Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.
 
         The critical distinction here, is the difference between this concept and an &quot;intent&quot;, of which it is a specialization.  An intent involves decisions by a single party, the author.  A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request."></definition>
         </concept>
@@ -26381,7 +26381,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
         <concept>
          <code value="RMD"></code>
          <display value="recommendation"></display>
-         <definition value="Definition: A suggestion that an act should be performed with an acceptance of some degree of professional responsibility for the resulting act. Not an explicit request. .
+         <definition value="Definition: A suggestion that an act should be performed with an acceptance of some degree of professional responsibility for the resulting act. Not an explicit request. .
 
         
          UsageNotes: Where there is no clear definition or applicable concept of &quot;professional responsibility�, RMD becomes indistinguishable from PRP. ."></definition>
@@ -26391,7 +26391,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <concept>
        <code value="PRMS"></code>
        <display value="promise"></display>
-       <definition value="Definition: A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act.
+       <definition value="Definition: A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act.
 
         
          UsageNotes: Commitments may be retracted or cancelled."></definition>
@@ -26415,7 +26415,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <code value="CRT"></code>
       <display value="criterion"></display>
       <definition value="Deprecation Comment: 
-         This concept This codes should no longer be used.  Instead, set attribute Act.isCriterionInd to &quot;true&quot; and use the desired mood for your criterion.
+         This concept This codes should no longer be used.  Instead, set attribute Act.isCriterionInd to &quot;true&quot; and use the desired mood for your criterion.
 
         
          Definition: A condition that must be true for the source act to be considered."></definition>
@@ -26427,7 +26427,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <code value="EVN.CRT"></code>
        <display value="event criterion"></display>
        <definition value="Deprecation Comment: 
-         This concept This codes should no longer be used.  Instead, set attribute Act.isCriterionInd to &quot;true&quot; and use the desired mood for your criterion.
+         This concept This codes should no longer be used.  Instead, set attribute Act.isCriterionInd to &quot;true&quot; and use the desired mood for your criterion.
 
         
          Definition: A criterion (CRT) that has_match = an event (EVN)."></definition>
@@ -26485,20 +26485,20 @@ A surgical Procedure act object (representing a procedure report) requires a sig
      <concept>
       <code value="EXPEC"></code>
       <display value="expectation"></display>
-      <definition value="Definition: An act that is considered to have some noteworthy likelihood of occurring in the future (has_match = event).
+      <definition value="Definition: An act that is considered to have some noteworthy likelihood of occurring in the future (has_match = event).
 
         
-         Examples:Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning.
+         Examples:Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning.
 
         
          UsageNotes:INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with expectation, which is a prediction that something will happen in the future. GOL (goal) reflects a hope rather than a prediction. RSK (risk) reflects a potential negative event that may or may not be expected to happen."></definition>
       <concept>
        <code value="GOL"></code>
        <display value="Goal"></display>
-       <definition value="Definition: An expectation that is considered to be desirable to occur in the future 
+       <definition value="Definition: An expectation that is considered to be desirable to occur in the future 
 
         
-         Examples:Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction.
+         Examples:Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction.
 
         
          UsageNotes: INT (intent) reflects a plan for the future, which is a declaration to do something.  This contrasts with goal which doesn't represent an intention to act, merely a hope for an eventual result.  A goal is distinct from the intended actions to reach that goal.  &quot;I will reduce the dose of drug x to 20mg&quot; is an intent.  &quot;I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg&quot; is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope."></definition>
@@ -26506,10 +26506,10 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <concept>
        <code value="RSK"></code>
        <display value="risk"></display>
-       <definition value="Definition:An act that may occur in the future and which is regarded as undesirable 
+       <definition value="Definition:An act that may occur in the future and which is regarded as undesirable 
 
         
-         Examples:Increased risk of DVT, at risk for sub-acute bacterial endocarditis.
+         Examples:Increased risk of DVT, at risk for sub-acute bacterial endocarditis.
 
         
          UsageNotes:Note: An observation in RSK mood expresses the undesirable act, and not the underlying risk factor. A risk factor that is present (e.g. obesity, smoking, etc) should be expressed in event mood. INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen. GOL (goal) reflects a hope to achieve something. EXPEC (expectation) is the prediction of a positive or negative event. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen, and may not be expected to happen."></definition>
@@ -26528,7 +26528,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/IntegrityCheckAlgorithm"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="IntegrityCheckAlgorithm"></id>
+    <id value="v3-IntegrityCheckAlgorithm"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26577,7 +26577,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/HL7UpdateMode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="HL7UpdateMode"></id>
+    <id value="v3-HL7UpdateMode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26744,7 +26744,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/ProcessingID"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ProcessingID"></id>
+    <id value="v3-ProcessingID"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26798,7 +26798,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/RoleCode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RoleCode"></id>
+    <id value="v3-RoleCode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -26851,7 +26851,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
     <concept>
      <code value="_AffiliationRoleType"></code>
      <display value="AffiliationRoleType"></display>
-     <definition value="Concepts characterizing the type of association formed by player and scoper when there is a recognized Affiliate role by which the two parties are related.
+     <definition value="Concepts characterizing the type of association formed by player and scoper when there is a recognized Affiliate role by which the two parties are related.
 
         
          Examples: Business Partner, Business Associate, Colleague"></definition>
@@ -26965,7 +26965,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
      <concept>
       <code value="_PayorRoleType"></code>
       <display value="PayorRoleType"></display>
-      <definition value="Description:PayorRoleType for a particular type of policy or program benefit package or plan where more detail about the coverage administration role of the Payor is required.  The functions performed by a Payor qualified by a PayorRoleType may be specified by the PayorParticpationFunction value set.
+      <definition value="Description:PayorRoleType for a particular type of policy or program benefit package or plan where more detail about the coverage administration role of the Payor is required.  The functions performed by a Payor qualified by a PayorRoleType may be specified by the PayorParticpationFunction value set.
 
         
          Examples:A Payor that is a TPA may administer a managed care plan without underwriting the risk."></definition>
@@ -26981,9 +26981,9 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <concept>
        <code value="TPA"></code>
        <display value="Third party administrator"></display>
-       <definition value="Description:Third party administrator (TPA) is a payor organization that processes health care claims without carrying insurance risk. Third party administrators are prominent players in the managed care industry and have the expertise and capability to administer all or a portion of the claims process. They are normally contracted by a health insurer or self-insuring companies to administer services, including claims administration, premium collection, enrollment and other administrative activities.
+       <definition value="Description:Third party administrator (TPA) is a payor organization that processes health care claims without carrying insurance risk. Third party administrators are prominent players in the managed care industry and have the expertise and capability to administer all or a portion of the claims process. They are normally contracted by a health insurer or self-insuring companies to administer services, including claims administration, premium collection, enrollment and other administrative activities.
 
-        Self-insured employers often contract with third party administrator to handle their insurance functions. Insurance companies oftentimes outsource the claims, utilization review or membership functions to a TPA. Sometimes TPAs only manage provider networks, only claims or only utilization review.
+        Self-insured employers often contract with third party administrator to handle their insurance functions. Insurance companies oftentimes outsource the claims, utilization review or membership functions to a TPA. Sometimes TPAs only manage provider networks, only claims or only utilization review.
 
         While some third-party administrators may operate as units of insurance companies, they are often independent. However, hospitals or provider organizations desiring to set up their own health plans will often outsource certain responsibilities to TPAs.  TPAs may perform one or several payor functions, specified by the PayorParticipationFunction value set, such as provider management, enrollment, utilization management, and fee for service claims adjudication management."></definition>
       </concept>
@@ -27062,7 +27062,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="ANTIBIOT"></code>
         <display value="Antibiotic"></display>
-        <definition value="Description:Non-person living subject used as antibiotic.
+        <definition value="Description:Non-person living subject used as antibiotic.
 
         
          Examples:Bacteriophage, is a virus that infects bacteria."></definition>
@@ -27070,10 +27070,10 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="DEBR"></code>
         <display value="Debridement"></display>
-        <definition value="Description:Maggots raised for biodebridement.
+        <definition value="Description:Maggots raised for biodebridement.
 
         
-         Discussion: Maggot Debridement Therapy is the medical use of live maggots for cleaning non-healing wounds.
+         Discussion: Maggot Debridement Therapy is the medical use of live maggots for cleaning non-healing wounds.
 
         
          Examples:Removal of burnt skin."></definition>
@@ -27174,7 +27174,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <concept>
        <code value="ORG"></code>
        <display value="organizational contact"></display>
-       <definition value="A contact for an organization for administrative purposes. Contact role specifies a person acting as a liason for the organization.
+       <definition value="A contact for an organization for administrative purposes. Contact role specifies a person acting as a liason for the organization.
 
         Example: HR Department representative."></definition>
       </concept>
@@ -27206,7 +27206,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
     <concept>
      <code value="_IdentifiedEntityType"></code>
      <display value="IdentifiedEntityType"></display>
-     <definition value="Definition: A code representing the type of identifier that has been assigned to the identified entity (IDENT).
+     <definition value="Definition: A code representing the type of identifier that has been assigned to the identified entity (IDENT).
 
         
          Examples: Example values include Social Insurance Number, Product Catalog ID, Product Model Number."></definition>
@@ -27336,7 +27336,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
     <concept>
      <code value="_MedicationGeneralizationRoleType"></code>
      <display value="MedicationGeneralizationRoleType"></display>
-     <definition value="Identifies the specific hierarchical relationship between the playing and scoping medications. 
+     <definition value="Identifies the specific hierarchical relationship between the playing and scoping medications. 
 
         
          Examples: Generic, Generic Formulation, Therapeutic Class, etc."></definition>
@@ -27352,7 +27352,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
      <concept>
       <code value="GD"></code>
       <display value="generic drug"></display>
-      <definition value="Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients independent of strength, and form.
+      <definition value="Relates a manufactured drug product to the non-proprietary (generic) representation of its ingredients independent of strength, and form.
 
         The scoping entity identifies a unique combination of medicine ingredients; sometimes referred to as &quot;ingredient set&quot;."></definition>
       <concept>
@@ -27775,7 +27775,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
         <concept>
          <code value="FTHFOST"></code>
          <display value="foster father"></display>
-         <definition value="The player of the role (parent) who is a male state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary.
+         <definition value="The player of the role (parent) who is a male state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary.
 
         The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child."></definition>
         </concept>
@@ -27810,7 +27810,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
         <concept>
          <code value="MTHFOST"></code>
          <display value="foster mother"></display>
-         <definition value="The player of the role (parent) who is a female state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary.
+         <definition value="The player of the role (parent) who is a female state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary.
 
         The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child."></definition>
         </concept>
@@ -27850,7 +27850,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
         </modifierExtension>
         <code value="PRNFOST"></code>
         <display value="foster parent"></display>
-        <definition value="The player of the role (parent) who is a state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary.
+        <definition value="The player of the role (parent) who is a state-certified caregiver responsible for the scoper (child) who has been placed in the parent's care. The placement of the child is usually arranged through the government or a social-service agency, and temporary.
 
         The state, via a jurisdiction recognized child protection agency, stands as in loco parentis to the child, making all legal decisions while the foster parent is responsible for the day-to-day care of the specified child."></definition>
        </concept>
@@ -28019,7 +28019,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="FMRSPS"></code>
         <display value="former spouse"></display>
-        <definition value="Player of the role was previously joined to the scoping person in marriage and this marriage is now dissolved and inactive.
+        <definition value="Player of the role was previously joined to the scoping person in marriage and this marriage is now dissolved and inactive.
 
         
          Usage Note: This is significant to indicate as some jurisdictions have different legal requirements for former spouse to access the patient's record, from a general friend."></definition>
@@ -28065,26 +28065,26 @@ A surgical Procedure act object (representing a procedure report) requires a sig
     <concept>
      <code value="_PolicyOrProgramCoverageRoleType"></code>
      <display value="PolicyOrProgramCoverageRoleType"></display>
-     <definition value="Description: A role recognized through the eligibility of an identified party for benefits covered under an insurance policy or a program based on meeting eligibility criteria.
+     <definition value="Description: A role recognized through the eligibility of an identified party for benefits covered under an insurance policy or a program based on meeting eligibility criteria.
 
-        Eligibility as a covered party may be conditioned on the party meeting criteria to qualify for coverage under a policy or program, which may be mandated by law.  These criteria may be: 
+        Eligibility as a covered party may be conditioned on the party meeting criteria to qualify for coverage under a policy or program, which may be mandated by law.  These criteria may be: 
 
         
          
-          The sole basis for coverage, e.g., being differently abled may qualify a person for disability coverage
+          The sole basis for coverage, e.g., being differently abled may qualify a person for disability coverage
 
          
          
-          May more fully qualify a covered party role e.g, being differently abled may qualify an adult child as a dependent
+          May more fully qualify a covered party role e.g, being differently abled may qualify an adult child as a dependent
 
          
          
-          May impact the level of coverage for a covered party under a policy or program, e.g., being differently abled may qualify a program eligible for additional benefits.
+          May impact the level of coverage for a covered party under a policy or program, e.g., being differently abled may qualify a program eligible for additional benefits.
 
          
         
         
-         Discussion:  The Abstract Value Set &quot;CoverageRoleType&quot;, which was developed for use in the Canadian realm &quot;pre-coordinate&quot; coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., &quot;handicapped dependent&quot;.   These role.codes may only be used with COVPTY to avoid overlapping concepts that would result from using them to specify the specializations of COVPTY, e.g., the role.class DEPEN should not be used with the role.code family dependent because that relationship has overlapping concepts due to the role.code precoodination and is conveyed in FICO with the personal relationship role that has a PART role link to the covered party role.  For the same reasons, the role.class DEPEN should not be used with the role.code HANDIC (handicapped dependent); the role.code DIFFABLE (differently abled) should be used instead.
+         Discussion:  The Abstract Value Set &quot;CoverageRoleType&quot;, which was developed for use in the Canadian realm &quot;pre-coordinate&quot; coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., &quot;handicapped dependent&quot;.   These role.codes may only be used with COVPTY to avoid overlapping concepts that would result from using them to specify the specializations of COVPTY, e.g., the role.class DEPEN should not be used with the role.code family dependent because that relationship has overlapping concepts due to the role.code precoodination and is conveyed in FICO with the personal relationship role that has a PART role link to the covered party role.  For the same reasons, the role.class DEPEN should not be used with the role.code HANDIC (handicapped dependent); the role.code DIFFABLE (differently abled) should be used instead.
 
         In summary, the coded concepts in the Abstract Value Set &quot;CoveredPartyRoleType&quot; can be &quot;post-coordinated&quot; with the &quot;RoleClassCoveredParty&quot; Abstract Value Set.  Decoupling these concepts is intended to support an expansive range of covered party concepts and their semantic comparability."></definition>
      <property>
@@ -28215,10 +28215,10 @@ A surgical Procedure act object (representing a procedure report) requires a sig
      <concept>
       <code value="_CoveredPartyRoleType"></code>
       <display value="covered party role type"></display>
-      <definition value="A role recognized through the eligibility of an identified living subject for benefits covered under an insurance policy or a program.  Eligibility as a covered party may be conditioned on a relationship with (1) the policy holder such as the policy holder who is covered as an individual under a poliy or as a party sponsored for coverage by the policy holder.
+      <definition value="A role recognized through the eligibility of an identified living subject for benefits covered under an insurance policy or a program.  Eligibility as a covered party may be conditioned on a relationship with (1) the policy holder such as the policy holder who is covered as an individual under a poliy or as a party sponsored for coverage by the policy holder.
 
         
-         Example:An employee as a subscriber; or (2) on being scoped another covered party such as the subscriber, as in the case of a dependent. 
+         Example:An employee as a subscriber; or (2) on being scoped another covered party such as the subscriber, as in the case of a dependent. 
 
         
          Discussion:  The Abstract Value Set &quot;CoverageRoleType&quot;, which was developed for use in the Canadian realm &quot;pre-coordinate&quot; coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., &quot;handicapped dependent&quot;.  Other codes in the Abstract Value Set CoveredPartyRoleType domain can be &quot;post-coordinated&quot; with the EligiblePartyRoleType codes to denote comparable concepts.  Decoupling the concepts is intended to support a wider range of concepts and semantic comparability of coded concepts."></definition>
@@ -28237,7 +28237,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="CRIMEVIC"></code>
         <display value="crime victim"></display>
-        <definition value="Description: A person playing the role of program eligible under a program based on allegations of being the victim of a crime.
+        <definition value="Description: A person playing the role of program eligible under a program based on allegations of being the victim of a crime.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is &quot;program eligible&quot; and the person's status as a crime victim meets jurisdictional or program criteria."></definition>
@@ -28245,7 +28245,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="INJWKR"></code>
         <display value="injured worker"></display>
-        <definition value="Description: A person playing the role of program eligible under a workers compensation program based on the filing of work-related injury claim.
+        <definition value="Description: A person playing the role of program eligible under a workers compensation program based on the filing of work-related injury claim.
 
         
          Discussion:  This CoveredPartyRoleType.code is used when the CoveredPartyRole class code is either &quot;program eligible&quot;, a &quot;named insured&quot;, and &quot;individual insured&quot;,  or &quot;dependent&quot;, and the person's status as differently abled or &quot;handicapped&quot; meets jurisdictional, policy, or program criteria."></definition>
@@ -28262,7 +28262,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="COCBEN"></code>
         <display value="continuity of coverage beneficiary"></display>
-        <definition value="Description: A person playing the role of an individual insured with continuity of coverage under a policy which is being terminated based on loss of original status that was the basis for coverage.  Criteria for qualifying for continuity of coverage may be set by law.
+        <definition value="Description: A person playing the role of an individual insured with continuity of coverage under a policy which is being terminated based on loss of original status that was the basis for coverage.  Criteria for qualifying for continuity of coverage may be set by law.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot; or &quot;subscriber&quot; and the person's status as a continuity of coverage beneficiary meets jurisdictional or policy criteria."></definition>
@@ -28270,7 +28270,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="DIFFABL"></code>
         <display value="differently abled"></display>
-        <definition value="Description: A person playing the role of program eligible under a program based on meeting criteria for health or functional limitation set by law or by the program.
+        <definition value="Description: A person playing the role of program eligible under a program based on meeting criteria for health or functional limitation set by law or by the program.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot;, &quot;named insured&quot;, &quot;individual insured&quot;, or &quot;dependent&quot;, and the person's status as differently abled meets jurisdictional, policy, or program criteria."></definition>
@@ -28278,7 +28278,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="WARD"></code>
         <display value="ward"></display>
-        <definition value="Description: A person, who is a minor or is deemed incompetent, who plays the role of a program eligible where eligibility for coverage is based on meeting program eligibility criteria for status as a ward of a court or jurisdiction.
+        <definition value="Description: A person, who is a minor or is deemed incompetent, who plays the role of a program eligible where eligibility for coverage is based on meeting program eligibility criteria for status as a ward of a court or jurisdiction.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is a &quot;claimant&quot;, &quot;program eligible&quot;, a &quot;named insured&quot;, an &quot;individual Insured&quot; or a &quot;dependent&quot;, and the person's status as a ward meets program or policy criteria. In the case of a ward covered under a program providing financial or health benefits, a governmental agency may take temporary custody of a minor or incompetent for his/her protection and care, e.g., if the ward is suffering from neglect or abuse, or has been in trouble with the law."></definition>
@@ -28298,7 +28298,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="RETIREE"></code>
         <display value="retiree"></display>
-        <definition value="Description: A person playing the role of an individual insured under a policy based on meeting criteria for the employment status of retired set by law or the policy.
+        <definition value="Description: A person playing the role of an individual insured under a policy based on meeting criteria for the employment status of retired set by law or the policy.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot; or &quot;subscriber&quot; and the person's status as a retiree meets jurisdictional or policy criteria."></definition>
@@ -28327,7 +28327,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="INDIG"></code>
         <display value="member of an indigenous people"></display>
-        <definition value="Description: A person playing the role of program eligible under a program based on aboriginal ancestry or as a member of an aboriginal community.
+        <definition value="Description: A person playing the role of program eligible under a program based on aboriginal ancestry or as a member of an aboriginal community.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is &quot;program eligible&quot; and the person's status as a member of an indigenous people meets jurisdictional or program criteria."></definition>
@@ -28335,14 +28335,14 @@ A surgical Procedure act object (representing a procedure report) requires a sig
        <concept>
         <code value="MIL"></code>
         <display value="military"></display>
-        <definition value="Definition: A person playing the role of program eligible under a program based on military status.
+        <definition value="Definition: A person playing the role of program eligible under a program based on military status.
 
         
          Discussion:  This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot; or &quot;subscriber&quot; and the person's status as a member of the military meets jurisdictional or program criteria"></definition>
         <concept>
          <code value="ACTMIL"></code>
          <display value="active duty military"></display>
-         <definition value="Description: A person playing the role of program eligible under a program based on active military status.
+         <definition value="Description: A person playing the role of program eligible under a program based on active military status.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot; or &quot;subscriber&quot; and the persons status as active duty military meets jurisdictional or program criteria."></definition>
@@ -28350,7 +28350,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
         <concept>
          <code value="RETMIL"></code>
          <display value="retired military"></display>
-         <definition value="Description: A person playing the role of program eligible under a program based on retired military status.
+         <definition value="Description: A person playing the role of program eligible under a program based on retired military status.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot; or &quot;subscriber&quot; and the persons status as retired military meets jurisdictional or program criteria."></definition>
@@ -28358,7 +28358,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
         <concept>
          <code value="VET"></code>
          <display value="veteran"></display>
-         <definition value="Description: A person playing the role of program eligible under a program based on status as a military veteran.
+         <definition value="Description: A person playing the role of program eligible under a program based on status as a military veteran.
 
         
          Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either &quot;program eligible&quot; or &quot;subscriber&quot; and the persons status as a veteran meets jurisdictional or program criteria."></definition>
@@ -29287,7 +29287,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/ActRelationshipCheckpoint"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActRelationshipCheckpoint"></id>
+    <id value="v3-ActRelationshipCheckpoint"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -29351,7 +29351,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/AdministrativeGender"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AdministrativeGender"></id>
+    <id value="v3-AdministrativeGender"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -29405,7 +29405,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/Sequencing"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="Sequencing"></id>
+    <id value="v3-Sequencing"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -29459,7 +29459,7 @@ A surgical Procedure act object (representing a procedure report) requires a sig
   <fullUrl value="http://hl7.org/fhir/v3/hl7Realm"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="hl7Realm"></id>
+    <id value="v3-hl7Realm"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -29486,9 +29486,9 @@ A surgical Procedure act object (representing a procedure report) requires a sig
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
-Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models)  and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms.  All affiliate realm codes may automatically be used as both binding realms and namespace realms.  Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms.  (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.)  All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm.  For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types.  It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes.  However, tooling does not currently support namepace realm codes greater than 2 characters.  Open Issue:
-The name of the concept property &quot;owningAffiliate&quot; should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code.  Open Issue:
+    <description value="  Description:
+Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models)  and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms.  All affiliate realm codes may automatically be used as both binding realms and namespace realms.  Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms.  (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.)  All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm.  For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types.  It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes.  However, tooling does not currently support namepace realm codes greater than 2 characters.  Open Issue:
+The name of the concept property &quot;owningAffiliate&quot; should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code.  Open Issue:
 In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-hl7Realm"></valueSet>
@@ -29750,7 +29750,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
   <fullUrl value="http://hl7.org/fhir/v3/ContainerCap"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ContainerCap"></id>
+    <id value="v3-ContainerCap"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -29834,7 +29834,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
   <fullUrl value="http://hl7.org/fhir/v3/CalendarCycle"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="CalendarCycle"></id>
+    <id value="v3-CalendarCycle"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -30015,7 +30015,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
   <fullUrl value="http://hl7.org/fhir/v3/QueryResponse"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="QueryResponse"></id>
+    <id value="v3-QueryResponse"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -30074,7 +30074,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
   <fullUrl value="http://hl7.org/fhir/v3/Confidentiality"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="Confidentiality"></id>
+    <id value="v3-Confidentiality"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -30131,13 +30131,13 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="L"></code>
       <display value="low"></display>
-      <definition value="Definition: Privacy metadata indicating that the information has been de-identified, and there are mitigating circumstances that prevent re-identification, which minimize risk of harm from unauthorized disclosure.  The information requires protection to maintain low sensitivity.
+      <definition value="Definition: Privacy metadata indicating that the information has been de-identified, and there are mitigating circumstances that prevent re-identification, which minimize risk of harm from unauthorized disclosure.  The information requires protection to maintain low sensitivity.
 
         
-         Examples: Includes anonymized, pseudonymized, or non-personally identifiable information such as HIPAA limited data sets.
+         Examples: Includes anonymized, pseudonymized, or non-personally identifiable information such as HIPAA limited data sets.
 
         
-         Map: No clear map to ISO 13606-4 Sensitivity Level (1) Care Management:   RECORD_COMPONENTs that might need to be accessed by a wide range of administrative staff to manage the subject of care's access to health services.
+         Map: No clear map to ISO 13606-4 Sensitivity Level (1) Care Management:   RECORD_COMPONENTs that might need to be accessed by a wide range of administrative staff to manage the subject of care's access to health services.
 
         
          Usage Note: This metadata indicates the receiver may have an obligation to comply with a data use agreement."></definition>
@@ -30145,13 +30145,13 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="M"></code>
       <display value="moderate"></display>
-      <definition value="Definition: Privacy metadata indicating moderately sensitive information, which presents moderate risk of harm if disclosed without authorization.
+      <definition value="Definition: Privacy metadata indicating moderately sensitive information, which presents moderate risk of harm if disclosed without authorization.
 
         
-         Examples: Includes allergies of non-sensitive nature used inform food service; health information a patient authorizes to be used for marketing, released to a bank for a health credit card or savings account; or information in personal health record systems that are not governed under health privacy laws.
+         Examples: Includes allergies of non-sensitive nature used inform food service; health information a patient authorizes to be used for marketing, released to a bank for a health credit card or savings account; or information in personal health record systems that are not governed under health privacy laws.
 
         
-         Map: Partial Map to ISO 13606-4 Sensitivity Level (2) Clinical Management:  Less sensitive RECORD_COMPONENTs that might need to be accessed by a wider range of personnel not all of whom are actively caring for the patient (e.g. radiology staff).
+         Map: Partial Map to ISO 13606-4 Sensitivity Level (2) Clinical Management:  Less sensitive RECORD_COMPONENTs that might need to be accessed by a wider range of personnel not all of whom are actively caring for the patient (e.g. radiology staff).
 
         
          Usage Note: This metadata indicates that the receiver may be obligated to comply with the receiver's terms of use or privacy policies."></definition>
@@ -30159,13 +30159,13 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="N"></code>
       <display value="normal"></display>
-      <definition value="Definition: Privacy metadata indicating that the information is typical, non-stigmatizing health information, which presents typical risk of harm if disclosed without authorization.
+      <definition value="Definition: Privacy metadata indicating that the information is typical, non-stigmatizing health information, which presents typical risk of harm if disclosed without authorization.
 
         
-         Examples: In the US, this includes what HIPAA identifies as the minimum necessary protected health information (PHI) given a covered purpose of use (treatment, payment, or operations).  Includes typical, non-stigmatizing health information disclosed in an application for health, workers compensation, disability, or life insurance.
+         Examples: In the US, this includes what HIPAA identifies as the minimum necessary protected health information (PHI) given a covered purpose of use (treatment, payment, or operations).  Includes typical, non-stigmatizing health information disclosed in an application for health, workers compensation, disability, or life insurance.
 
         
-         Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care:   Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR).   Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations.
+         Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care:   Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR).   Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations.
 
         
          Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable jurisdictional privacy law or disclosure authorization."></definition>
@@ -30173,13 +30173,13 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="R"></code>
       <display value="restricted"></display>
-      <definition value="Privacy metadata indicating highly sensitive, potentially stigmatizing information, which presents a high risk to the information subject if disclosed without authorization. May be pre-empted by jurisdictional law, e.g., for public health reporting or emergency treatment.
+      <definition value="Privacy metadata indicating highly sensitive, potentially stigmatizing information, which presents a high risk to the information subject if disclosed without authorization. May be pre-empted by jurisdictional law, e.g., for public health reporting or emergency treatment.
 
         
-         Examples: Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual, e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer.
+         Examples: Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual, e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer.
 
         
-         Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations..
+         Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations..
 
         
          Usage Note: This metadata indicates that the receiver may be obligated to comply with applicable, prevailing (default) jurisdictional privacy law or disclosure authorization.."></definition>
@@ -30187,10 +30187,10 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="U"></code>
       <display value="unrestricted"></display>
-      <definition value="Definition: Privacy metadata indicating that the information is not classified as sensitive.
+      <definition value="Definition: Privacy metadata indicating that the information is not classified as sensitive.
 
         
-         Examples: Includes publicly available information, e.g., business name, phone, email or physical address.
+         Examples: Includes publicly available information, e.g., business name, phone, email or physical address.
 
         
          Usage Note: This metadata indicates that the receiver has no obligation to consider additional policies when making access control decisions.   Note that in some jurisdictions, personally identifiable information must be protected as confidential, so it would not be appropriate to assign a confidentiality code of &quot;unrestricted&quot;  to that information even if it is publicly available."></definition>
@@ -30198,13 +30198,13 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="V"></code>
       <display value="very restricted"></display>
-      <definition value=". Privacy metadata indicating that the information is extremely sensitive and likely stigmatizing health information that presents a very high risk if disclosed without authorization.  This information must be kept in the highest confidence.  
+      <definition value=". Privacy metadata indicating that the information is extremely sensitive and likely stigmatizing health information that presents a very high risk if disclosed without authorization.  This information must be kept in the highest confidence.  
 
         
-         Examples:  Includes information about a victim of abuse, patient requested information sensitivity, and taboo subjects relating to health status that must be discussed with the patient by an attending provider before sharing with the patient.  May also include information held under “legal lock� or attorney-client privilege
+         Examples:  Includes information about a victim of abuse, patient requested information sensitivity, and taboo subjects relating to health status that must be discussed with the patient by an attending provider before sharing with the patient.  May also include information held under “legal lock� or attorney-client privilege
 
         
-         Map:  This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject.
+         Map:  This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject.
 
         
          Usage Note:  This metadata indicates that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject."></definition>
@@ -30213,7 +30213,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
     <concept>
      <code value="_ConfidentialityByAccessKind"></code>
      <display value="ConfidentialityByAccessKind"></display>
-     <definition value="Description: By accessing subject / role and relationship based  rights  (These concepts are mutually exclusive, one and only one is required for a valid confidentiality coding.)
+     <definition value="Description: By accessing subject / role and relationship based  rights  (These concepts are mutually exclusive, one and only one is required for a valid confidentiality coding.)
 
         
          Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode"></definition>
@@ -30232,7 +30232,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="B"></code>
       <display value="business"></display>
-      <definition value="Description: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality.  However, no patient related information may ever be of this confidentiality level.
+      <definition value="Description: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality.  However, no patient related information may ever be of this confidentiality level.
 
         
          Deprecation Comment: Replced by ActCode.B"></definition>
@@ -30248,7 +30248,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="D"></code>
       <display value="clinician"></display>
-      <definition value="Description: Only clinicians may see this item, billing and administration persons can not access this item without special permission.
+      <definition value="Description: Only clinicians may see this item, billing and administration persons can not access this item without special permission.
 
         
          Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode"></definition>
@@ -30264,7 +30264,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="I"></code>
       <display value="individual"></display>
-      <definition value="Description: Access only to individual persons who are mentioned explicitly as actors of this service and whose actor type warrants that access (cf. to actor type code).
+      <definition value="Description: Access only to individual persons who are mentioned explicitly as actors of this service and whose actor type warrants that access (cf. to actor type code).
 
         
          Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode"></definition>
@@ -30281,7 +30281,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
     <concept>
      <code value="_ConfidentialityByInfoType"></code>
      <display value="ConfidentialityByInfoType"></display>
-     <definition value="Description: By information type, only for service catalog entries (multiples allowed). Not to be used with actual patient data!
+     <definition value="Description: By information type, only for service catalog entries (multiples allowed). Not to be used with actual patient data!
 
         
          Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode"></definition>
@@ -30300,7 +30300,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="ETH"></code>
       <display value="substance abuse related"></display>
-      <definition value="Description: Alcohol/drug-abuse related item
+      <definition value="Description: Alcohol/drug-abuse related item
 
         
          Deprecation Comment:Replced by ActCode.ETH"></definition>
@@ -30316,7 +30316,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="HIV"></code>
       <display value="HIV related"></display>
-      <definition value="Description: HIV and AIDS related item
+      <definition value="Description: HIV and AIDS related item
 
         
          Deprecation Comment:Replced by ActCode.HIV"></definition>
@@ -30332,7 +30332,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="PSY"></code>
       <display value="psychiatry relate"></display>
-      <definition value="Description: Psychiatry related item
+      <definition value="Description: Psychiatry related item
 
         
          Deprecation Comment:Replced by ActCode.PSY"></definition>
@@ -30348,7 +30348,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="SDV"></code>
       <display value="sexual and domestic violence related"></display>
-      <definition value="Description: Sexual assault / domestic violence related item
+      <definition value="Description: Sexual assault / domestic violence related item
 
         
          Deprecation Comment:Replced by ActCode.SDV"></definition>
@@ -30365,7 +30365,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
     <concept>
      <code value="_ConfidentialityModifiers"></code>
      <display value="ConfidentialityModifiers"></display>
-     <definition value="Description: Modifiers of role based access rights  (multiple allowed)
+     <definition value="Description: Modifiers of role based access rights  (multiple allowed)
 
         
          Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode"></definition>
@@ -30384,7 +30384,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
      <concept>
       <code value="C"></code>
       <display value="celebrity"></display>
-      <definition value="Description: Celebrities are people of public interest (VIP) including employees, whose information require special protection.
+      <definition value="Description: Celebrities are people of public interest (VIP) including employees, whose information require special protection.
 
         
          Deprecation Comment:Replced by ActCode.CEL"></definition>
@@ -30401,7 +30401,7 @@ In spite of the inability of tooling to process codes longer than 2 characters,
       <code value="S"></code>
       <display value="sensitive"></display>
       <definition value="Description: 
-        
+        
 Information for which the patient seeks heightened confidentiality. Sensitive information is not to be shared with family members.  Information reported by the patient about family members is sensitive by default. Flag can be set or cleared on patient's request.
          Deprecation Comment:Deprecated due to updated confidentiality codes under ActCode"></definition>
       <property>
@@ -30416,7 +30416,7 @@ Information for which the patient seeks heightened confidentiality. Sensitive in
      <concept>
       <code value="T"></code>
       <display value="taboo"></display>
-      <definition value="Description: Information not to be disclosed or discussed with patient except through physician assigned to patient in this case.  This is usually a temporary constraint only, example use is a new fatal diagnosis or finding, such as malignancy or HIV.
+      <definition value="Description: Information not to be disclosed or discussed with patient except through physician assigned to patient in this case.  This is usually a temporary constraint only, example use is a new fatal diagnosis or finding, such as malignancy or HIV.
 
         
          Deprecation Note:Replced by ActCode.TBOO"></definition>
@@ -30437,7 +30437,7 @@ Information for which the patient seeks heightened confidentiality. Sensitive in
   <fullUrl value="http://hl7.org/fhir/v3/ParticipationMode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ParticipationMode"></id>
+    <id value="v3-ParticipationMode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -30467,9 +30467,9 @@ Information for which the patient seeks heightened confidentiality. Sensitive in
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A set of codes specifying the modality by which the Entity playing the Role is participating in the Act.  Examples:
-Physically present, over the telephone, written communication.  Rationale:
-Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically.  Open Issue:
+    <description value=" A set of codes specifying the modality by which the Entity playing the Role is participating in the Act.  Examples:
+Physically present, over the telephone, written communication.  Rationale:
+Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically.  Open Issue:
 There needs to be a reexamination of the hierarchies as there seems to be some muddling between ELECTRONIC and other concepts that involve electronic communication that are in other hierarchies."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ParticipationMode"></valueSet>
@@ -30557,7 +30557,7 @@ There needs to be a reexamination of the hierarchies as there seems to be some m
   <fullUrl value="http://hl7.org/fhir/v3/EntityNamePartQualifier"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityNamePartQualifier"></id>
+    <id value="v3-EntityNamePartQualifier"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -30584,7 +30584,7 @@ There needs to be a reexamination of the hierarchies as there seems to be some m
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Needs description"></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-EntityNamePartQualifier"></valueSet>
@@ -30677,9 +30677,9 @@ Needs description"></description>
      <concept>
       <code value="CON"></code>
       <display value="container name"></display>
-      <definition value="Description: This refers to the container if present in the medicinal product name.
+      <definition value="Description: This refers to the container if present in the medicinal product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
@@ -30688,9 +30688,9 @@ Needs description"></description>
      <concept>
       <code value="DEV"></code>
       <display value="device name"></display>
-      <definition value="Description: This refers to the qualifiers in the name for devices and is at the moment mainly applicable to insulins and inhalation products.
+      <definition value="Description: This refers to the qualifiers in the name for devices and is at the moment mainly applicable to insulins and inhalation products.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
@@ -30699,11 +30699,11 @@ Needs description"></description>
      <concept>
       <code value="FLAV"></code>
       <display value="FlavorName"></display>
-      <definition value="Description: This refers to a flavor of the medicinal product if present in the medicinal product name.
+      <definition value="Description: This refers to a flavor of the medicinal product if present in the medicinal product name.
 
         
          Examples:
-        
+        
 
         
          For 'CoughCure Linctus Orange Flavor', the flavor part is &quot;Orange&quot;
@@ -30712,11 +30712,11 @@ Needs description"></description>
      <concept>
       <code value="FORMUL"></code>
       <display value="FormulationPartName"></display>
-      <definition value="Description: This refers to the formulation of the medicinal product if present in the medicinal product name.
+      <definition value="Description: This refers to the formulation of the medicinal product if present in the medicinal product name.
 
         
          Examples:
-        
+        
 
         
          For 'SpecialMed Sugar Free Cough Syrup', the formulation name part is &quot;Sugar Free&quot;
@@ -30725,17 +30725,17 @@ Needs description"></description>
      <concept>
       <code value="FRM"></code>
       <display value="form name"></display>
-      <definition value="Description: This refers to the pharmaceutical form/ if present in the medicinal product name.
+      <definition value="Description: This refers to the pharmaceutical form/ if present in the medicinal product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
-          For Agenerase 50 mg soft capsules: Soft Capsules
+          For Agenerase 50 mg soft capsules: Soft Capsules
 
          
          
-          For Ludiomil 25mg-Filmtabletten: Filmtabletten
+          For Ludiomil 25mg-Filmtabletten: Filmtabletten
 
          
          
@@ -30744,17 +30744,17 @@ Needs description"></description>
      <concept>
       <code value="INV"></code>
       <display value="invented name"></display>
-      <definition value="Description: This refers to the product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name and, if appropriate, whether it is intended e.g. for babies, children or adults. 
+      <definition value="Description: This refers to the product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name and, if appropriate, whether it is intended e.g. for babies, children or adults. 
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
-          Agenerase
+          Agenerase
 
          
          
-          Optaflu
+          Optaflu
 
          
          
@@ -30763,11 +30763,11 @@ Needs description"></description>
      <concept>
       <code value="POPUL"></code>
       <display value="TargetPopulationName"></display>
-      <definition value="Description: This refers to the target population for the medicinal product if present in the medicinal product name
+      <definition value="Description: This refers to the target population for the medicinal product if present in the medicinal product name
 
         
          Examples:
-        
+        
 
         
          For 'Broncho-Drug 3.5 mg-capsules for children', the target population part is &quot;children&quot;
@@ -30776,17 +30776,17 @@ Needs description"></description>
      <concept>
       <code value="SCI"></code>
       <display value="scientific name"></display>
-      <definition value="Description: This refers to the product common or scientific name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.
+      <definition value="Description: This refers to the product common or scientific name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
-          For Agenerase: N/A
+          For Agenerase: N/A
 
          
          
-          For Optaflu: Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season)
+          For Optaflu: Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season)
 
          
          
@@ -30795,17 +30795,17 @@ Needs description"></description>
      <concept>
       <code value="STR"></code>
       <display value="strength name"></display>
-      <definition value="Description: This refers to the strength if present in the medicinal product name. The use of decimal points should be accommodated if required.
+      <definition value="Description: This refers to the strength if present in the medicinal product name. The use of decimal points should be accommodated if required.
 
-        EXAMPLES:
+        EXAMPLES:
 
         
          
-          For Agenerase 50 mg soft capsules: 50mg
+          For Agenerase 50 mg soft capsules: 50mg
 
          
          
-          For Ludiomil 25mg-Filmtabletten: 25 mg
+          For Ludiomil 25mg-Filmtabletten: 25 mg
 
          
          
@@ -30814,11 +30814,11 @@ Needs description"></description>
      <concept>
       <code value="TIME"></code>
       <display value="TimeOrPeriodName"></display>
-      <definition value="Description: This refers to a time or time period that may be specified in the text of the medicinal product name
+      <definition value="Description: This refers to a time or time period that may be specified in the text of the medicinal product name
 
         
          Example:
-        
+        
 
         
          For an influenza vaccine 'Drug-FLU season 2008/2009', the time/period part is &quot;2008/2009 season&quot;"></definition>
@@ -30826,9 +30826,9 @@ Needs description"></description>
      <concept>
       <code value="TMK"></code>
       <display value="trademark name"></display>
-      <definition value="Description: This refers to trademark/company element if present in the medicinal product name.
+      <definition value="Description: This refers to trademark/company element if present in the medicinal product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
@@ -30838,11 +30838,11 @@ Needs description"></description>
       <code value="USE"></code>
       <display value="intended use name"></display>
       <definition value="Description: This refers to the intended use if present in the medicinal product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.
-
+
 
         
          Examples:
-        
+        
 
         
          For 'Drug-BI Caplets - Heartburn Relief', the intended use part is: &quot;Heartburn Relief&quot;
@@ -30938,7 +30938,7 @@ Needs description"></description>
   <fullUrl value="http://hl7.org/fhir/v3/AcknowledgementType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AcknowledgementType"></id>
+    <id value="v3-AcknowledgementType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -30965,7 +30965,7 @@ Needs description"></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" This attribute contains an acknowledgement code as described in the HL7 message processing rules.  OpenIssue:
+    <description value=" This attribute contains an acknowledgement code as described in the HL7 message processing rules.  OpenIssue:
 Description was copied from attribute and needs to be improved to be appropriate for a code system."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-AcknowledgementType"></valueSet>
@@ -31008,7 +31008,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/RouteOfAdministration"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RouteOfAdministration"></id>
+    <id value="v3-RouteOfAdministration"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34220,7 +34220,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/ResponseMode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ResponseMode"></id>
+    <id value="v3-ResponseMode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34274,7 +34274,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/ContextControl"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ContextControl"></id>
+    <id value="v3-ContextControl"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34387,7 +34387,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/NullFlavor"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="NullFlavor"></id>
+    <id value="v3-NullFlavor"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34441,10 +34441,10 @@ Description was copied from attribute and needs to be improved to be appropriate
       <concept>
        <code value="OTH"></code>
        <display value="other"></display>
-       <definition value="Description:The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).
+       <definition value="Description:The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).
 
         
-         Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors.  However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed.  For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc.
+         Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors.  However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed.  For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc.
 
         With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE.  By definition, all local codes and original text are part of the value set if the coding strength is CWE."></definition>
        <concept>
@@ -34461,13 +34461,13 @@ Description was copied from attribute and needs to be improved to be appropriate
       <concept>
        <code value="UNC"></code>
        <display value="un-encoded"></display>
-       <definition value="Description: The actual value has not yet been encoded within the approved value domain.
+       <definition value="Description: The actual value has not yet been encoded within the approved value domain.
 
         
-         Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system.  Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM.
+         Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system.  Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM.
 
         
-         Usage Notes: If it is known that it is not possible to encode the concept, OTH should be used instead.  However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted.
+         Usage Notes: If it is known that it is not possible to encode the concept, OTH should be used instead.  However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted.
 
         Data type properties such as original text and translations may be present when this null flavor is included."></definition>
       </concept>
@@ -34475,7 +34475,7 @@ Description was copied from attribute and needs to be improved to be appropriate
      <concept>
       <code value="MSK"></code>
       <display value="masked"></display>
-      <definition value="There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information.
+      <definition value="There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information.
 
         Note: using this null flavor does provide information that may be a breach of confidentiality, even though no detail data is provided.  Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist without providing any detail."></definition>
      </concept>
@@ -34487,10 +34487,10 @@ Description was copied from attribute and needs to be improved to be appropriate
      <concept>
       <code value="UNK"></code>
       <display value="unknown"></display>
-      <definition value="Description:A proper value is applicable, but not known.
+      <definition value="Description:A proper value is applicable, but not known.
 
         
-         Usage Notes: This means the actual value is not known.  If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used.  No properties should be included for a datatype with this property unless:
+         Usage Notes: This means the actual value is not known.  If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used.  No properties should be included for a datatype with this property unless:
 
         
          Those properties themselves directly translate to a semantic of &quot;unknown&quot;.  (E.g. a local code sent as a translation that conveys 'unknown')
@@ -34546,7 +34546,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/EquipmentAlertLevel"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EquipmentAlertLevel"></id>
+    <id value="v3-EquipmentAlertLevel"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34605,7 +34605,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/AcknowledgementCondition"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AcknowledgementCondition"></id>
+    <id value="v3-AcknowledgementCondition"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34674,7 +34674,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/PersonDisabilityType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="PersonDisabilityType"></id>
+    <id value="v3-PersonDisabilityType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34763,7 +34763,7 @@ Description was copied from attribute and needs to be improved to be appropriate
   <fullUrl value="http://hl7.org/fhir/v3/EntityNamePartQualifierR2"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityNamePartQualifierR2"></id>
+    <id value="v3-EntityNamePartQualifierR2"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -34790,7 +34790,7 @@ Description was copied from attribute and needs to be improved to be appropriate
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-EntityNamePartQualifierR2"></valueSet>
@@ -34805,7 +34805,7 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
     <concept>
      <code value="AD"></code>
      <display value="acquired"></display>
-     <definition value="Description:A name part a person acquired.  The name part may be acquired by adoption, or the person may have chosen to use the name part for some other reason.
+     <definition value="Description:A name part a person acquired.  The name part may be acquired by adoption, or the person may have chosen to use the name part for some other reason.
 
         
          Note: this differs from an Other/Psuedonym/Alias in that an acquired name part is acquired on a formal basis rather than an informal one (e.g. registered as part of the official name)."></definition>
@@ -34818,7 +34818,7 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
     <concept>
      <code value="BR"></code>
      <display value="birth"></display>
-     <definition value="Description:A name that a person was given at birth or established as a consequence of adoption. 
+     <definition value="Description:A name that a person was given at birth or established as a consequence of adoption. 
 
         
          Note: This is not used for temporary names assigned at birth such as &quot;Baby of Smith&quot; a&quot; which is just a name with a use code of &quot;TEMP&quot;."></definition>
@@ -34841,7 +34841,7 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
     <concept>
      <code value="MID"></code>
      <display value="middle name"></display>
-     <definition value="Description:Indicates that the name part is a middle name.
+     <definition value="Description:Indicates that the name part is a middle name.
 
         
          Usage Notes: In general, the english &quot;middle name&quot; concept is all of the given names after the first. This qualifier may be used to explicitly indicate which given names are considered to be middle names. The middle name qualifier may also be used with family names. This is a Scandinavian use case, matching the concept of &quot;mellomnavn&quot;,&quot;mellannamn&quot;. Note that there are specific rules that indicate what names may be taken as a mellannamn in different Scandinavian countries."></definition>
@@ -34862,9 +34862,9 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="CON"></code>
       <display value="container name"></display>
-      <definition value="Description: This refers to the container if present in the medicinal product name.
+      <definition value="Description: This refers to the container if present in the medicinal product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
@@ -34873,9 +34873,9 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="DEV"></code>
       <display value="device name"></display>
-      <definition value="Description: This refers to the qualifiers in the name for devices and is at the moment mainly applicable to insulins and inhalation products.
+      <definition value="Description: This refers to the qualifiers in the name for devices and is at the moment mainly applicable to insulins and inhalation products.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
@@ -34884,11 +34884,11 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="FLAV"></code>
       <display value="FlavorName"></display>
-      <definition value="Description: This refers to a flavor of the medicinal product if present in the medicinal product name.
+      <definition value="Description: This refers to a flavor of the medicinal product if present in the medicinal product name.
 
         
          Examples:
-        
+        
 
         
          For 'CoughCure Linctus Orange Flavor', the flavor part is &quot;Orange&quot;
@@ -34897,11 +34897,11 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="FORMUL"></code>
       <display value="FormulationPartName"></display>
-      <definition value="Description: This refers to the formulation of the medicinal product if present in the medicinal product name.
+      <definition value="Description: This refers to the formulation of the medicinal product if present in the medicinal product name.
 
         
          Examples:
-        
+        
 
         
          For 'SpecialMed Sugar Free Cough Syrup', the formulation name part is &quot;Sugar Free&quot;
@@ -34910,17 +34910,17 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="FRM"></code>
       <display value="form name"></display>
-      <definition value="Description: This refers to the pharmaceutical form/ if present in the medicinal product name.
+      <definition value="Description: This refers to the pharmaceutical form/ if present in the medicinal product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
-          For Agenerase 50 mg soft capsules: Soft Capsules
+          For Agenerase 50 mg soft capsules: Soft Capsules
 
          
          
-          For Ludiomil 25mg-Filmtabletten: Filmtabletten
+          For Ludiomil 25mg-Filmtabletten: Filmtabletten
 
          
          
@@ -34929,17 +34929,17 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="INV"></code>
       <display value="invented name"></display>
-      <definition value="Description: This refers to the product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name and, if appropriate, whether it is intended e.g. for babies, children or adults. 
+      <definition value="Description: This refers to the product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name and, if appropriate, whether it is intended e.g. for babies, children or adults. 
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
-          Agenerase
+          Agenerase
 
          
          
-          Optaflu
+          Optaflu
 
          
          
@@ -34948,11 +34948,11 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="POPUL"></code>
       <display value="TargetPopulationName"></display>
-      <definition value="Description: This refers to the target population for the medicinal product if present in the medicinal product name
+      <definition value="Description: This refers to the target population for the medicinal product if present in the medicinal product name
 
         
          Examples:
-        
+        
 
         
          For 'Broncho-Drug 3.5 mg-capsules for children', the target population part is &quot;children&quot;
@@ -34961,17 +34961,17 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="SCI"></code>
       <display value="scientific name"></display>
-      <definition value="Description: This refers to the product common or scientific name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.
+      <definition value="Description: This refers to the product common or scientific name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
-          For Agenerase: N/A
+          For Agenerase: N/A
 
          
          
-          For Optaflu: Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season)
+          For Optaflu: Influenza vaccine (surface antigen, inactivated, prepared in cell culture) (2007/2008 season)
 
          
          
@@ -34980,17 +34980,17 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="STR"></code>
       <display value="strength name"></display>
-      <definition value="Description: This refers to the strength if present in the medicinal product name. The use of decimal points should be accommodated if required.
+      <definition value="Description: This refers to the strength if present in the medicinal product name. The use of decimal points should be accommodated if required.
 
-        EXAMPLES:
+        EXAMPLES:
 
         
          
-          For Agenerase 50 mg soft capsules: 50mg
+          For Agenerase 50 mg soft capsules: 50mg
 
          
          
-          For Ludiomil 25mg-Filmtabletten: 25 mg
+          For Ludiomil 25mg-Filmtabletten: 25 mg
 
          
          
@@ -34999,11 +34999,11 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="TIME"></code>
       <display value="TimeOrPeriodName"></display>
-      <definition value="Description: This refers to a time or time period that may be specified in the text of the medicinal product name
+      <definition value="Description: This refers to a time or time period that may be specified in the text of the medicinal product name
 
         
          Example:
-        
+        
 
         
          For an influenza vaccine 'Drug-FLU season 2008/2009', the time/period part is &quot;2008/2009 season&quot;"></definition>
@@ -35011,9 +35011,9 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
      <concept>
       <code value="TMK"></code>
       <display value="trademark name"></display>
-      <definition value="Description: This refers to trademark/company element if present in the medicinal product name.
+      <definition value="Description: This refers to trademark/company element if present in the medicinal product name.
 
-        EXAMPLES: 
+        EXAMPLES: 
 
         
          
@@ -35023,11 +35023,11 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
       <code value="USE"></code>
       <display value="intended use name"></display>
       <definition value="Description: This refers to the intended use if present in the medicinal product name without the trademark or the name of the marketing authorization holder or any other descriptor reflected in the product name.
-
+
 
         
          Examples:
-        
+        
 
         
          For 'Drug-BI Caplets - Heartburn Relief', the intended use part is: &quot;Heartburn Relief&quot;
@@ -35075,7 +35075,7 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
   <fullUrl value="http://hl7.org/fhir/v3/EncounterSpecialCourtesy"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EncounterSpecialCourtesy"></id>
+    <id value="v3-EncounterSpecialCourtesy"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -35139,7 +35139,7 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
   <fullUrl value="http://hl7.org/fhir/v3/ObservationInterpretation"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ObservationInterpretation"></id>
+    <id value="v3-ObservationInterpretation"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -35166,7 +35166,7 @@ The qualifier is a set of codes each of which specifies a certain subcategory of
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" One or more codes specifying a rough qualitative interpretation of the observation, such as &quot;normal&quot;, &quot;abnormal&quot;, &quot;below normal&quot;, &quot;change up&quot;, &quot;resistant&quot;, &quot;susceptible&quot;, etc.  OpenIssue:
+    <description value=" One or more codes specifying a rough qualitative interpretation of the observation, such as &quot;normal&quot;, &quot;abnormal&quot;, &quot;below normal&quot;, &quot;change up&quot;, &quot;resistant&quot;, &quot;susceptible&quot;, etc.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified.  Note also that this might be identical to the V2 code system of interpretation codes (formerly Abnormal Flags in older versions)."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ObservationInterpretation"></valueSet>
@@ -35200,7 +35200,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="Carrier"></code>
       <display value="Carrier"></display>
-      <definition value="The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder.
+      <definition value="The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder.
 
         
          
@@ -35223,7 +35223,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="B"></code>
       <display value="Better"></display>
-      <definition value="The current result or observation value has improved compared to the previous result or observation value (the change is significant as defined in the respective test procedure).
+      <definition value="The current result or observation value has improved compared to the previous result or observation value (the change is significant as defined in the respective test procedure).
 
         [Note: This can be applied to quantitative or qualitative observations.]"></definition>
      </concept>
@@ -35240,7 +35240,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="W"></code>
       <display value="Worse"></display>
-      <definition value="The current result or observation value has degraded compared to the previous result or observation value (the change is significant as defined in the respective test procedure).
+      <definition value="The current result or observation value has degraded compared to the previous result or observation value (the change is significant as defined in the respective test procedure).
 
         [Note: This can be applied to quantitative or qualitative observations.]"></definition>
      </concept>
@@ -35256,21 +35256,21 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="&lt;"></code>
       <display value="Off scale low"></display>
-      <definition value="The result is below the minimum detection limit (the test procedure or equipment is the limiting factor).
+      <definition value="The result is below the minimum detection limit (the test procedure or equipment is the limiting factor).
 
         Synonyms: Below analytical limit, low off scale."></definition>
      </concept>
      <concept>
       <code value="&gt;"></code>
       <display value="Off scale high"></display>
-      <definition value="The result is above the maximum quantifiable limit (the test procedure or equipment is the limiting factor).
+      <definition value="The result is above the maximum quantifiable limit (the test procedure or equipment is the limiting factor).
 
         Synonyms: Above analytical limit, high off scale."></definition>
      </concept>
      <concept>
       <code value="AC"></code>
       <display value="Anti-complementary substances present"></display>
-      <definition value="A valid result cannot be obtained for the specified component / analyte due to the presence of anti-complementary substances in the sample.
+      <definition value="A valid result cannot be obtained for the specified component / analyte due to the presence of anti-complementary substances in the sample.
 
         
          
@@ -35284,14 +35284,14 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="IE"></code>
       <display value="Insufficient evidence"></display>
-      <definition value="There is insufficient evidence that the species in question is a good target for therapy with the drug.  A categorical interpretation is not possible.
+      <definition value="There is insufficient evidence that the species in question is a good target for therapy with the drug.  A categorical interpretation is not possible.
 
         [Note: A MIC with &quot;IE&quot; and/or a comment may be reported (without an accompanying S, I or R-categorization).]"></definition>
      </concept>
      <concept>
       <code value="QCF"></code>
       <display value="Quality control failure"></display>
-      <definition value="A result cannot be considered valid for the specified component / analyte or organism due to failure in the quality control testing component.
+      <definition value="A result cannot be considered valid for the specified component / analyte or organism due to failure in the quality control testing component.
 
         
          
@@ -35305,7 +35305,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="TOX"></code>
       <display value="Cytotoxic substance present"></display>
-      <definition value="A valid result cannot be obtained for the specified organism or cell line due to the presence of cytotoxic substances in the sample or culture.
+      <definition value="A valid result cannot be obtained for the specified organism or cell line due to the presence of cytotoxic substances in the sample or culture.
 
         
          
@@ -35328,26 +35328,26 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="A"></code>
       <display value="Abnormal"></display>
-      <definition value="The result or observation value is outside the reference range or expected norm (as defined for the respective test procedure).
+      <definition value="The result or observation value is outside the reference range or expected norm (as defined for the respective test procedure).
 
         [Note: Typically applies to non-numeric results.]"></definition>
       <concept>
        <code value="AA"></code>
        <display value="Critical abnormal"></display>
-       <definition value="The result or observation value is outside a reference range or expected norm at a level at which immediate action should be considered for patient safety (as defined for the respective test procedure).
+       <definition value="The result or observation value is outside a reference range or expected norm at a level at which immediate action should be considered for patient safety (as defined for the respective test procedure).
 
         [Note: Typically applies to non-numeric results.  Analogous to critical/panic limits for numeric results.]"></definition>
        <concept>
         <code value="HH"></code>
         <display value="Critical high"></display>
-        <definition value="The result for a quantitative observation is above a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure).
+        <definition value="The result for a quantitative observation is above a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure).
 
         Synonym: Above upper panic limits."></definition>
        </concept>
        <concept>
         <code value="LL"></code>
         <display value="Critical low"></display>
-        <definition value="The result for a quantitative observation is below a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure).
+        <definition value="The result for a quantitative observation is below a reference level at which immediate action should be considered for patient safety (as defined for the respective test procedure).
 
         Synonym: Below lower panic limits."></definition>
        </concept>
@@ -35355,7 +35355,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
       <concept>
        <code value="H"></code>
        <display value="High"></display>
-       <definition value="The result for a quantitative observation is above the upper limit of the reference range (as defined for the respective test procedure).
+       <definition value="The result for a quantitative observation is above the upper limit of the reference range (as defined for the respective test procedure).
 
         Synonym: Above high normal"></definition>
        <concept>
@@ -35364,10 +35364,10 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
         </modifierExtension>
         <code value="H&gt;"></code>
         <display value="Significantly high"></display>
-        <definition value="A test result that is significantly higher than the reference (normal) or therapeutic interval, but has not reached the critically high value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'H' and 'HH'.]
+        <definition value="A test result that is significantly higher than the reference (normal) or therapeutic interval, but has not reached the critically high value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'H' and 'HH'.]
 
         
-         Deprecation Comment: The code 'H&gt;' is being deprecated in order to align with the use of the code 'HU' for &quot;Very high&quot; in V2 Table 0078 &quot;Interpretation Codes&quot;.
+         Deprecation Comment: The code 'H&gt;' is being deprecated in order to align with the use of the code 'HU' for &quot;Very high&quot; in V2 Table 0078 &quot;Interpretation Codes&quot;.
 
         [Note: The use of code 'H&gt;' is non-preferred, as this code is deprecated and on track to be retired; use code 'HU' instead."></definition>
         <property>
@@ -35387,7 +35387,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
       <concept>
        <code value="L"></code>
        <display value="Low"></display>
-       <definition value="The result for a quantitative observation is below the lower limit of the reference range (as defined for the respective test procedure).
+       <definition value="The result for a quantitative observation is below the lower limit of the reference range (as defined for the respective test procedure).
 
         Synonym: Below low normal"></definition>
        <concept>
@@ -35396,10 +35396,10 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
         </modifierExtension>
         <code value="L&lt;"></code>
         <display value="Significantly low"></display>
-        <definition value="A test result that is significantly lower than the reference (normal) or therapeutic interval, but has not reached the critically low value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'L' and 'LL'.]
+        <definition value="A test result that is significantly lower than the reference (normal) or therapeutic interval, but has not reached the critically low value and might need special attention, as defined by the laboratory or the clinician.[Note: This level is situated between 'L' and 'LL'.]
 
         
-         Deprecation Comment: The code 'L&lt;' is being deprecated in order to align with the use of the code 'LU' for &quot;Very low&quot; in V2 Table 0078 &quot;Interpretation Codes&quot;.
+         Deprecation Comment: The code 'L&lt;' is being deprecated in order to align with the use of the code 'LU' for &quot;Very low&quot; in V2 Table 0078 &quot;Interpretation Codes&quot;.
 
         [Note: The use of code 'L&lt;' is non-preferred, as this code is deprecated and on track to be retired; use code 'LU' instead."></definition>
         <property>
@@ -35420,7 +35420,7 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
      <concept>
       <code value="N"></code>
       <display value="Normal"></display>
-      <definition value="The result or observation value is within the reference range or expected norm (as defined for the respective test procedure).
+      <definition value="The result or observation value is within the reference range or expected norm (as defined for the respective test procedure).
 
         [Note: Applies to numeric or non-numeric results.]"></definition>
      </concept>
@@ -35440,20 +35440,20 @@ Description copied from Concept Domain of same name.  Must be verified.  Note al
       <code value="I"></code>
       <display value="Intermediate"></display>
       <definition value="Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with uncertain therapeutic effect. Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)
-Projects: ISO 20776-1, ISO 20776-2
+Projects: ISO 20776-1, ISO 20776-2
 
-        [Note 1: Bacterial strains are categorized as intermediate by applying the appropriate breakpoints in a defined phenotypic test system.]
+        [Note 1: Bacterial strains are categorized as intermediate by applying the appropriate breakpoints in a defined phenotypic test system.]
 
-        [Note 2: This class of susceptibility implies that an infection due to the isolate can be appropriately treated in body sites where the drugs are physiologically concentrated or when a high dosage of drug can be used.]
+        [Note 2: This class of susceptibility implies that an infection due to the isolate can be appropriately treated in body sites where the drugs are physiologically concentrated or when a high dosage of drug can be used.]
 
-        [Note 3: This class also indicates a &quot;buffer zone,&quot; to prevent small, uncontrolled, technical factors from causing major discrepancies in interpretations.]
+        [Note 3: This class also indicates a &quot;buffer zone,&quot; to prevent small, uncontrolled, technical factors from causing major discrepancies in interpretations.]
 
         [Note 4: These breakpoints can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).]"></definition>
      </concept>
      <concept>
       <code value="MS"></code>
       <display value="moderately susceptible"></display>
-      <definition value="The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder.
+      <definition value="The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder.
 
         
          
@@ -35467,11 +35467,11 @@ Projects: ISO 20776-1, ISO 20776-2
      <concept>
       <code value="NS"></code>
       <display value="Non-susceptible"></display>
-      <definition value="A category used for isolates for which only a susceptible interpretive criterion has been designated because of the absence or rare occurrence of resistant strains. Isolates that have MICs above or zone diameters below the value indicated for the susceptible breakpoint should be reported as non-susceptible.
+      <definition value="A category used for isolates for which only a susceptible interpretive criterion has been designated because of the absence or rare occurrence of resistant strains. Isolates that have MICs above or zone diameters below the value indicated for the susceptible breakpoint should be reported as non-susceptible.
 
-        NOTE 1: An isolate that is interpreted as non-susceptible does not necessarily mean that the isolate has a resistance mechanism. It is possible that isolates with MICs above the susceptible breakpoint that lack resistance mechanisms may be encountered within the wild-type distribution subsequent to the time the susceptible-only breakpoint is set. 
+        NOTE 1: An isolate that is interpreted as non-susceptible does not necessarily mean that the isolate has a resistance mechanism. It is possible that isolates with MICs above the susceptible breakpoint that lack resistance mechanisms may be encountered within the wild-type distribution subsequent to the time the susceptible-only breakpoint is set. 
 
-        NOTE 2: For strains yielding results in the &quot;nonsusceptible&quot; category, organism identification and antimicrobial susceptibility test results should be confirmed.
+        NOTE 2: For strains yielding results in the &quot;nonsusceptible&quot; category, organism identification and antimicrobial susceptibility test results should be confirmed.
 
         Synonym: decreased susceptibility."></definition>
      </concept>
@@ -35480,18 +35480,18 @@ Projects: ISO 20776-1, ISO 20776-2
       <display value="Resistant"></display>
       <definition value="Bacterial strain inhibited in vitro by a concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic failure.
 Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)  
-Projects: ISO 20776-1, ISO 20776-2
+Projects: ISO 20776-1, ISO 20776-2
 
-        [Note 1: Bacterial strains are categorized as resistant by applying the appropriate breakpoints in a defined phenotypic test system.]
+        [Note 1: Bacterial strains are categorized as resistant by applying the appropriate breakpoints in a defined phenotypic test system.]
 
         [Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).]"></definition>
       <concept>
        <code value="SYN-R"></code>
        <display value="Synergy - resistant"></display>
-       <definition value="A category for isolates where the bacteria (e.g. enterococci) are not susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent).  This is predictive that this combination therapy will not be effective. 
+       <definition value="A category for isolates where the bacteria (e.g. enterococci) are not susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent).  This is predictive that this combination therapy will not be effective. 
 
         
-         Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside.
+         Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside.
 
         
          Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found."></definition>
@@ -35502,25 +35502,25 @@ Projects: ISO 20776-1, ISO 20776-2
       <display value="Susceptible"></display>
       <definition value="Bacterial strain inhibited by in vitro concentration of an antimicrobial agent that is associated with a high likelihood of therapeutic success.
 Reference: CLSI (http://www.clsi.org/Content/NavigationMenu/Resources/HarmonizedTerminologyDatabase/Harmonized_Terminolo.htm)
-Synonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2
+Synonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2
 
-        [Note 1: Bacterial strains are categorized as susceptible by applying the appropriate breakpoints in a defined phenotypic system.]
+        [Note 1: Bacterial strains are categorized as susceptible by applying the appropriate breakpoints in a defined phenotypic system.]
 
         [Note 2: This breakpoint can be altered due to changes in circumstances (e.g., changes in commonly used drug dosages, emergence of new resistance mechanisms).]"></definition>
       <concept>
        <code value="SDD"></code>
        <display value="Susceptible-dose dependent"></display>
-       <definition value="A category that includes isolates with antimicrobial agent minimum inhibitory concentrations (MICs) that approach usually attainable blood and tissue levels and for which response rates may be lower than for susceptible isolates.
+       <definition value="A category that includes isolates with antimicrobial agent minimum inhibitory concentrations (MICs) that approach usually attainable blood and tissue levels and for which response rates may be lower than for susceptible isolates.
 
         Reference: CLSI document M44-A2 2009 &quot;Method for antifungal disk diffusion susceptibility testing of yeasts; approved guideline - second edition&quot; - page 2."></definition>
       </concept>
       <concept>
        <code value="SYN-S"></code>
        <display value="Synergy - susceptible"></display>
-       <definition value="A category for isolates where the bacteria (e.g. enterococci) are susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent).  This is predictive that this combination therapy will be effective. 
+       <definition value="A category for isolates where the bacteria (e.g. enterococci) are susceptible in vitro to a combination therapy (e.g., high-level aminoglycoside and cell wall active agent).  This is predictive that this combination therapy will be effective. 
 
         
-         Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside.
+         Usage Note: Since the use of penicillin or ampicillin alone often results in treatment failure of serious enterococcal or other bacterial infections, combination therapy is usually indicated to enhance bactericidal activity. The synergy between a cell wall active agent (such as penicillin, ampicillin, or vancomycin) and an aminoglycoside (such as gentamicin, kanamycin or streptomycin) is best predicted by screening for high-level bacterial resistance to the aminoglycoside.
 
         
          Open Issue: The print name of the code is very general and the description is very specific to a pair of classes of agents, which may lead to confusion of these concepts in the future should other synergies be found."></definition>
@@ -35529,7 +35529,7 @@ Synonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2
      <concept>
       <code value="VS"></code>
       <display value="very susceptible"></display>
-      <definition value="The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder.
+      <definition value="The patient is considered as carrier based on the testing results. A carrier is an individual who carries an altered form of a gene which can lead to having a child or offspring in future generations with a genetic disorder.
 
         
          
@@ -35545,7 +35545,7 @@ Synonym (earlier term): Sensitive Projects: ISO 20776-1, ISO 20776-2
      <code value="EX"></code>
      <display value="outside threshold"></display>
      <definition value="The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.
-
+
 
         Example: A positive result on a Hepatitis screening test.
          Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L).  The only apparent significant difference is their reference to use in protocols for exclusion of study subjects.
@@ -35555,7 +35555,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <code value="HX"></code>
       <display value="above high threshold"></display>
       <definition value="The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.
-
+
 
         Example: A positive result on a Hepatitis screening test.
          Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L).  The only apparent significant difference is their reference to use in protocols for exclusion of study subjects.  These concepts/codes were proposed by RCRIM for use in the CTLaboratory message.  They were submitted and approved in the November 2005 Harmonization cycle in proposal &quot;030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455&quot;. However, this proposal was not fully implemented in the vocabulary.  The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes.  Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response.  It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held."></definition>
@@ -35563,7 +35563,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="LX"></code>
       <display value="below low threshold"></display>
-      <definition value="The numeric observation/test result is interpreted as being below the low threshold value for a particular protocol within which the result is being reported.
+      <definition value="The numeric observation/test result is interpreted as being below the low threshold value for a particular protocol within which the result is being reported.
 
         Example: A Total White Blood Cell Count falling below a protocol-defined threshold value of 3000/mm^3
          Open Issue: EX, HX, LX: These three concepts do not seem to meet a clear need in the vocabulary, and their use in observation interpretation appears likely to be covered by other existing concepts (e.g., A, H, L).  The only apparent significant difference is their reference to use in protocols for exclusion of study subjects.  These concepts/codes were proposed by RCRIM for use in the CTLaboratory message.  They were submitted and approved in the November 2005 Harmonization cycle in proposal &quot;030103C_VOCAB_RCRIM_l_quade_RCRIM Obs Interp_20051028154455&quot;.  However, this proposal was not fully implemented in the vocabulary.  The proposal recommended creation of the x_ClinicalResearchExclusion domain in ObservationInterpretation with a value set including those three concepts/codes, but there is no subdomain of that name or equivalent with a binding to either of the value sets that contain these concepts/codes.  Members of the OO WG have recently attempted to contact members of RCRIM regarding these concepts, both by email and at the recent WGM in Atlanta, without response.  It is felt by OO that the best course of action to take at this time is to add this comprehensive Open Issue rather than deprecate these three concepts at this time, until further discussion is held."></definition>
@@ -35572,7 +35572,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
     <concept>
      <code value="HM"></code>
      <display value="Hold for Medical Review"></display>
-     <definition value="Hold for Medical Review
+     <definition value="Hold for Medical Review
 
         
          Usage Note: This code is not intended for use in V3 artifacts.  It is included in the code system to maintain alignment with the V2 Table 0078 &quot;Interpretation Codes.&quot;"></definition>
@@ -35592,7 +35592,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="IND"></code>
       <display value="Indeterminate"></display>
-      <definition value="The specified component / analyte, organism or clinical sign could neither be declared positive / negative nor detected / not detected by the performed test or procedure.
+      <definition value="The specified component / analyte, organism or clinical sign could neither be declared positive / negative nor detected / not detected by the performed test or procedure.
 
         
          Usage Note: For example, if the specimen was degraded, poorly processed, or was missing the required anatomic structures, then &quot;indeterminate&quot; (i.e. &quot;cannot be determined&quot;) is the appropriate response, not &quot;equivocal&quot;."></definition>
@@ -35605,7 +35605,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="NEG"></code>
       <display value="Negative"></display>
-      <definition value="An absence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure.
+      <definition value="An absence finding of the specified component / analyte, organism or clinical sign based on the established threshold of the performed test or procedure.
 
         [Note: Negative does not necessarily imply the complete absence of the specified item.]"></definition>
       <concept>
@@ -35647,7 +35647,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
     <concept>
      <code value="OBX"></code>
      <display value="Interpretation qualifiers in separate OBX segments"></display>
-     <definition value="Interpretation qualifiers in separate OBX segments
+     <definition value="Interpretation qualifiers in separate OBX segments
 
         
          Usage Note: This code is not intended for use in V3 artifacts.  It is included in the code system to maintain alignment with the V2 Table 0078 &quot;Interpretation Codes.&quot;"></definition>
@@ -35687,7 +35687,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
   <fullUrl value="http://hl7.org/fhir/v3/RelationshipConjunction"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RelationshipConjunction"></id>
+    <id value="v3-RelationshipConjunction"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -35741,7 +35741,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
   <fullUrl value="http://hl7.org/fhir/v3/ActRelationshipJoin"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActRelationshipJoin"></id>
+    <id value="v3-ActRelationshipJoin"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -35800,7 +35800,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
   <fullUrl value="http://hl7.org/fhir/v3/RoleStatus"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RoleStatus"></id>
+    <id value="v3-RoleStatus"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -35874,7 +35874,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
   <fullUrl value="http://hl7.org/fhir/v3/ActClass"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActClass"></id>
+    <id value="v3-ActClass"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -35927,23 +35927,23 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
     <concept>
      <code value="ACT"></code>
      <display value="act"></display>
-     <definition value="A record of something that is being done, has been done, can be done, or is intended or requested to be done.
+     <definition value="A record of something that is being done, has been done, can be done, or is intended or requested to be done.
 
         
-         Examples:The kinds of acts that are common in health care are (1) a clinical observation, (2) an assessment of health condition (such as problems and diagnoses), (3) healthcare goals, (4) treatment services (such as medication, surgery, physical and psychological therapy), (5) assisting, monitoring or attending, (6) training and education services to patients and their next of kin, (7) and notary services (such as advanced directives or living will), (8)  editing and maintaining documents, and many others.
+         Examples:The kinds of acts that are common in health care are (1) a clinical observation, (2) an assessment of health condition (such as problems and diagnoses), (3) healthcare goals, (4) treatment services (such as medication, surgery, physical and psychological therapy), (5) assisting, monitoring or attending, (6) training and education services to patients and their next of kin, (7) and notary services (such as advanced directives or living will), (8)  editing and maintaining documents, and many others.
 
         
-         Discussion and Rationale: Acts are the pivot of the RIM; all domain information and processes are represented primarily in Acts. Any profession or business, including healthcare, is primarily constituted of intentional and occasionally non-intentional actions, performed and recorded by responsible actors. An Act-instance is a record of such an action.
+         Discussion and Rationale: Acts are the pivot of the RIM; all domain information and processes are represented primarily in Acts. Any profession or business, including healthcare, is primarily constituted of intentional and occasionally non-intentional actions, performed and recorded by responsible actors. An Act-instance is a record of such an action.
 
-        Acts connect to Entities in their Roles through Participations and connect to other Acts through ActRelationships. Participations are the authors, performers and other responsible parties as well as subjects and beneficiaries (which includes tools and material used in the performance of the act, which are also subjects). The moodCode distinguishes between Acts that are meant as factual records, vs. records of intended or ordered services, and the other modalities in which act can appear.
+        Acts connect to Entities in their Roles through Participations and connect to other Acts through ActRelationships. Participations are the authors, performers and other responsible parties as well as subjects and beneficiaries (which includes tools and material used in the performance of the act, which are also subjects). The moodCode distinguishes between Acts that are meant as factual records, vs. records of intended or ordered services, and the other modalities in which act can appear.
 
-        One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who &quot;owns&quot; the act. Responsibility for the act means responsibility for what is being stated in the Act and as what it is stated. Ownership of the act is assumed in the sense of who may operationally modify the same act. Ownership and responsibility of the Act is not the same as ownership or responsibility of what the Act-object refers to in the real world. The same real world activity can be described by two people, each being the author of their Act, describing the same real world activity. Yet one can be a witness while the other can be a principal performer. The performer has responsibilities for the physical actions; the witness only has responsibility for making a true statement to the best of his or her ability. The two Act-instances may even disagree, but because each is properly attributed to its author, such disagreements can exist side by side and left to arbitration by a recipient of these Act-instances.
+        One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who &quot;owns&quot; the act. Responsibility for the act means responsibility for what is being stated in the Act and as what it is stated. Ownership of the act is assumed in the sense of who may operationally modify the same act. Ownership and responsibility of the Act is not the same as ownership or responsibility of what the Act-object refers to in the real world. The same real world activity can be described by two people, each being the author of their Act, describing the same real world activity. Yet one can be a witness while the other can be a principal performer. The performer has responsibilities for the physical actions; the witness only has responsibility for making a true statement to the best of his or her ability. The two Act-instances may even disagree, but because each is properly attributed to its author, such disagreements can exist side by side and left to arbitration by a recipient of these Act-instances.
 
-        In this sense, an Act-instance represents a &quot;statement&quot; according to Rector and Nowlan (1991) [Foundations for an electronic medical record. Methods Inf Med. 30.]  Rector and Nowlan have emphasized the importance of understanding the medical record not as a collection of facts, but &quot;a faithful record of what clinicians have heard, seen, thought, and done.&quot; Rector and Nowlan go on saying that &quot;the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view.&quot; Indeed the Act class is this attributable statement, and the rules of updating acts (discussed in the state-transition model, see Act.statusCode) versus generating new Act-instances are designed according to this principle of permanent attributable statements.
+        In this sense, an Act-instance represents a &quot;statement&quot; according to Rector and Nowlan (1991) [Foundations for an electronic medical record. Methods Inf Med. 30.]  Rector and Nowlan have emphasized the importance of understanding the medical record not as a collection of facts, but &quot;a faithful record of what clinicians have heard, seen, thought, and done.&quot; Rector and Nowlan go on saying that &quot;the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view.&quot; Indeed the Act class is this attributable statement, and the rules of updating acts (discussed in the state-transition model, see Act.statusCode) versus generating new Act-instances are designed according to this principle of permanent attributable statements.
 
-        Rector and Nolan focus on the electronic medical record as a collection of statements, while attributed statements, these are still mostly factual statements. However, the Act class goes beyond this limitation to attributed factual statements, representing what is known as &quot;speech-acts&quot; in linguistics and philosophy.  The notion of speech-act includes that there is pragmatic meaning in language utterances, aside from just factual statements; and that these utterances interact with the real world to change the state of affairs, even directly cause physical activities to happen. For example, an order is a speech act that (provided it is issued adequately) will cause the ordered action to be physically performed. The speech act theory has culminated in the seminal work by Austin (1962) [How to do things with words. Oxford University Press].
+        Rector and Nolan focus on the electronic medical record as a collection of statements, while attributed statements, these are still mostly factual statements. However, the Act class goes beyond this limitation to attributed factual statements, representing what is known as &quot;speech-acts&quot; in linguistics and philosophy.  The notion of speech-act includes that there is pragmatic meaning in language utterances, aside from just factual statements; and that these utterances interact with the real world to change the state of affairs, even directly cause physical activities to happen. For example, an order is a speech act that (provided it is issued adequately) will cause the ordered action to be physically performed. The speech act theory has culminated in the seminal work by Austin (1962) [How to do things with words. Oxford University Press].
 
-        An activity in the real world may progress from defined, through planned and ordered to executed, which is represented as the mood of the Act. Even though one might think of a single activity as progressing from planned to executed, this progression is reflected by multiple Act-instances, each having one and only one mood that will not change along the Act-instance life cycle.  This is because the attribution and content of speech acts along this progression of an activity may be different, and it is often critical that a permanent and faithful record be maintained of this progression. The specification of orders or promises or plans must not be overwritten by the specification of what was actually done, so as to allow comparing actions with their earlier specifications. Act-instances that describe this progression of the same real world activity are linked through the ActRelationships (of the relationship category &quot;sequel&quot;).
+        An activity in the real world may progress from defined, through planned and ordered to executed, which is represented as the mood of the Act. Even though one might think of a single activity as progressing from planned to executed, this progression is reflected by multiple Act-instances, each having one and only one mood that will not change along the Act-instance life cycle.  This is because the attribution and content of speech acts along this progression of an activity may be different, and it is often critical that a permanent and faithful record be maintained of this progression. The specification of orders or promises or plans must not be overwritten by the specification of what was actually done, so as to allow comparing actions with their earlier specifications. Act-instances that describe this progression of the same real world activity are linked through the ActRelationships (of the relationship category &quot;sequel&quot;).
 
         Act as statements or speech-acts are the only representation of real world facts or processes in the HL7 RIM. The truth about the real world is constructed through a combination (and arbitration) of such attributed statements only, and there is no class in the RIM whose objects represent &quot;objective state of affairs&quot; or &quot;real processes&quot; independent from attributed statements. As such, there is no distinction between an activity and its documentation. Every Act includes both to varying degrees. For example, a factual statement made about recent (but past) activities, authored (and signed) by the performer of such activities, is commonly known as a procedure report or original documentation (e.g., surgical procedure report, clinic note etc.). Conversely, a status update on an activity that is presently in progress, authored by the performer (or a close observer) is considered to capture that activity (and is later superceded by a full procedure report). However, both status update and procedure report are acts of the same kind, only distinguished by mood and state (see statusCode) and completeness of the information."></definition>
      <concept>
@@ -35957,39 +35957,39 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="COMPOSITION"></code>
        <display value="composition"></display>
-       <definition value="A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians.
+       <definition value="A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians.
 
-        A composition represents part of a patient record originating from a single interaction between an authenticator and the record.
+        A composition represents part of a patient record originating from a single interaction between an authenticator and the record.
 
-        Unless otherwise stated all statements within a composition have the same authenticator, apply to the same patient and were recorded in a single session of use of a single application.
+        Unless otherwise stated all statements within a composition have the same authenticator, apply to the same patient and were recorded in a single session of use of a single application.
 
         A composition contains organizers and entries."></definition>
        <concept>
         <code value="DOC"></code>
         <display value="document"></display>
-        <definition value="The notion of a document comes particularly from the paper world, where it corresponds to the contents recorded on discrete pieces of paper. In the electronic world, a document is a kind of composition that bears resemblance to their paper world counter-parts. Documents typically are meant to be human-readable.
+        <definition value="The notion of a document comes particularly from the paper world, where it corresponds to the contents recorded on discrete pieces of paper. In the electronic world, a document is a kind of composition that bears resemblance to their paper world counter-parts. Documents typically are meant to be human-readable.
 
         HL7's notion of document differs from that described in the W3C XML Recommendation, in which a document refers specifically to the contents that fall between the root element's start-tag and end-tag. Not all XML documents are HL7 documents."></definition>
         <concept>
          <code value="DOCCLIN"></code>
          <display value="clinical document"></display>
-         <definition value="A clinical document is a documentation of clinical observations and services, with the following characteristics:
+         <definition value="A clinical document is a documentation of clinical observations and services, with the following characteristics:
 
         
          
-          Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; 
+          Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; 
 
          
          
-          Stewardship - A clinical document is maintained by a person or organization entrusted with its care; 
+          Stewardship - A clinical document is maintained by a person or organization entrusted with its care; 
 
          
          
-          Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; 
+          Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; 
 
          
          
-          Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document;
+          Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document;
 
          
          
@@ -36005,15 +36005,15 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="CONTAINER"></code>
        <display value="record container"></display>
-       <definition value="Description: Container of clinical statements. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or &quot;container tree&quot;.
+       <definition value="Description: Container of clinical statements. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or &quot;container tree&quot;.
 
         The record entries relating to a single clinical session are usually grouped under headings that represent phases of the encounter, or assist with layout and navigation. Clinical headings usually reflect the clinical workflow during a care session, and might also reflect the main author's reasoning processes. Much research has demonstrated that headings are used differently by different professional groups and specialties, and that headings are not used consistently enough to support safe automatic processing of the E H R."></definition>
        <concept>
         <code value="CATEGORY"></code>
         <display value="category"></display>
-        <definition value="A group of entries within a composition or topic that have a common characteristic - for example, Examination, Diagnosis, Management OR Subjective, Objective, Analysis, Plan.
+        <definition value="A group of entries within a composition or topic that have a common characteristic - for example, Examination, Diagnosis, Management OR Subjective, Objective, Analysis, Plan.
 
-        The distinction from Topic relates to value sets. For Category there is a bounded list of things like &quot;Examination&quot;, &quot;Diagnosis&quot; or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter.
+        The distinction from Topic relates to value sets. For Category there is a bounded list of things like &quot;Examination&quot;, &quot;Diagnosis&quot; or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter.
 
         A CATEGORY MAY CONTAIN ENTRIES."></definition>
        </concept>
@@ -36030,7 +36030,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
        <concept>
         <code value="TOPIC"></code>
         <display value="topic"></display>
-        <definition value="A group of entries within a composition that are related to a common clinical theme - such as a specific disorder or problem, prevention, screening and provision of contraceptive services.
+        <definition value="A group of entries within a composition that are related to a common clinical theme - such as a specific disorder or problem, prevention, screening and provision of contraceptive services.
 
         A topic may contain categories and entries."></definition>
        </concept>
@@ -36038,17 +36038,17 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="EXTRACT"></code>
        <display value="extract"></display>
-       <definition value="This context represents the part of a patient record conveyed in a single communication. It is drawn from a providing system for the purposes of communication to a requesting process (which might be another repository, a client application or a middleware service such as an electronic guideline engine), and supporting the faithful inclusion of the communicated data in the receiving system.
+       <definition value="This context represents the part of a patient record conveyed in a single communication. It is drawn from a providing system for the purposes of communication to a requesting process (which might be another repository, a client application or a middleware service such as an electronic guideline engine), and supporting the faithful inclusion of the communicated data in the receiving system.
 
-        An extract may be the entirety of the patient record as held by the sender or it may be a part of that record (e.g. changes since a specified date).
+        An extract may be the entirety of the patient record as held by the sender or it may be a part of that record (e.g. changes since a specified date).
 
-        An extract contains folders or compositions.
+        An extract contains folders or compositions.
 
         An extract cannot contain another extract."></definition>
        <concept>
         <code value="EHR"></code>
         <display value="electronic health record"></display>
-        <definition value="A context that comprises all compositions. The EHR is an extract that includes the entire chart.
+        <definition value="A context that comprises all compositions. The EHR is an extract that includes the entire chart.
 
         
          NOTE: In an exchange scenario, an EHR is a specialization of an extract."></definition>
@@ -36057,40 +36057,40 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="FOLDER"></code>
        <display value="folder"></display>
-       <definition value="A context representing the high-level organization of an extract e.g. to group parts of the record by episode, care team, clinical specialty, clinical condition, or source application. Internationally, this kind of organizing structure is used variably: in some centers and systems the folder is treated as an informal compartmentalization of the overall health record; in others it might represent a significant legal portion of the EHR relating to the originating enterprise or team.
+       <definition value="A context representing the high-level organization of an extract e.g. to group parts of the record by episode, care team, clinical specialty, clinical condition, or source application. Internationally, this kind of organizing structure is used variably: in some centers and systems the folder is treated as an informal compartmentalization of the overall health record; in others it might represent a significant legal portion of the EHR relating to the originating enterprise or team.
 
-        A folder contains compositions.
+        A folder contains compositions.
 
         Folders may be nested within folders."></definition>
       </concept>
       <concept>
        <code value="GROUPER"></code>
        <display value="grouper"></display>
-       <definition value="Definition: An ACT that organizes a set of component acts into a semantic grouping that share a particular context such as timeframe, patient, etc.
+       <definition value="Definition: An ACT that organizes a set of component acts into a semantic grouping that share a particular context such as timeframe, patient, etc.
 
         
-         UsageNotes: The focus in a GROUPER act is the grouping of the contained acts.  For example &quot;a request to group&quot; (RQO), &quot;a type of grouping that is allowed to occur&quot; (DEF), etc.
+         UsageNotes: The focus in a GROUPER act is the grouping of the contained acts.  For example &quot;a request to group&quot; (RQO), &quot;a type of grouping that is allowed to occur&quot; (DEF), etc.
 
         Unlike WorkingList, which represents a dynamic, shared, continuously updated collection to provide a &quot;view&quot; of a set of objects, GROUPER collections tend to be static and simply indicate a shared set of semantics.  Note that sharing of semantics can be achieved using ACT as well.  However, with GROUPER, the sole semantic is of grouping."></definition>
        <concept>
         <code value="CLUSTER"></code>
         <display value="Cluster"></display>
-        <definition value="Description:An ACT that organizes a set of component acts into a semantic grouping that have a shared subject. The subject may be either a subject participation (SBJ), subject act relationship (SUBJ), or child participation/act relationship types.
+        <definition value="Description:An ACT that organizes a set of component acts into a semantic grouping that have a shared subject. The subject may be either a subject participation (SBJ), subject act relationship (SUBJ), or child participation/act relationship types.
 
         
-         Discussion: The focus in a CLUSTER act is the grouping of the contained acts.  For example &quot;a request to cluster&quot; (RQO), &quot;a type of cluster that is allowed to occur&quot; (DEF), etc.
+         Discussion: The focus in a CLUSTER act is the grouping of the contained acts.  For example &quot;a request to cluster&quot; (RQO), &quot;a type of cluster that is allowed to occur&quot; (DEF), etc.
 
         
          Examples: 
-        
+        
 
         
          
-          Radiologic investigations that might include administration of a dye, followed by radiographic observations;
+          Radiologic investigations that might include administration of a dye, followed by radiographic observations;
 
          
          
-          &quot;Isolate cluster&quot; which includes all testing and specimen processing performed on a specific isolate;
+          &quot;Isolate cluster&quot; which includes all testing and specimen processing performed on a specific isolate;
 
          
          
@@ -36116,7 +36116,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="ADJUD"></code>
       <display value="financial adjudication"></display>
-      <definition value="A transformation process where a requested invoice is transformed into an agreed invoice.  Represents the adjudication processing of an invoice (claim).  Adjudication results can be adjudicated as submitted, with adjustments or refused.
+      <definition value="A transformation process where a requested invoice is transformed into an agreed invoice.  Represents the adjudication processing of an invoice (claim).  Adjudication results can be adjudicated as submitted, with adjustments or refused.
 
         Adjudication results comprise 2 components: the adjudication processing results and a restated (or adjudicated) invoice or claim"></definition>
      </concept>
@@ -36151,21 +36151,21 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
        <concept>
         <code value="COV"></code>
         <display value="coverage"></display>
-        <definition value="When used in the EVN mood, this concept means with respect to a covered party:
+        <definition value="When used in the EVN mood, this concept means with respect to a covered party:
 
         
          
-          A health care insurance policy or plan that is contractually binding between two or more parties; or 
+          A health care insurance policy or plan that is contractually binding between two or more parties; or 
 
          
          
-          A health care program, usually administered by government entities, that provides coverage to persons determined eligible under the terms of the program.
+          A health care program, usually administered by government entities, that provides coverage to persons determined eligible under the terms of the program.
 
          
         
         
          
-          When used in the definition (DEF) mood, COV means potential coverage for a patient who may or may not be a covered party.
+          When used in the definition (DEF) mood, COV means potential coverage for a patient who may or may not be a covered party.
 
          
          
@@ -36176,24 +36176,24 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="CONC"></code>
       <display value="concern"></display>
-      <definition value="Definition: A worry that tends to persist over time and has as its subject a state or process. The subject of the worry has the potential to require intervention or management.
+      <definition value="Definition: A worry that tends to persist over time and has as its subject a state or process. The subject of the worry has the potential to require intervention or management.
 
         
          Examples: an observation result, procedure, substance administration, equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, allergy, and acute or chronic illness."></definition>
       <concept>
        <code value="HCASE"></code>
        <display value="public health case"></display>
-       <definition value="A public health case is a Concern about an observation or event that has a specific significance for public health. The creation of a PublicHealthCase initiates the tracking of the object of concern.  The decision to track is related to but somewhat independent of the underlying event or observation.
+       <definition value="A public health case is a Concern about an observation or event that has a specific significance for public health. The creation of a PublicHealthCase initiates the tracking of the object of concern.  The decision to track is related to but somewhat independent of the underlying event or observation.
 
         
-         UsageNotes: Typically a Public Health Case involves an instance or instances of a reportable infectious disease or other condition. The public health case can include a health-related event concerning a single individual or it may refer to multiple health-related events that are occurrences of the same disease or condition of interest to public health.
+         UsageNotes: Typically a Public Health Case involves an instance or instances of a reportable infectious disease or other condition. The public health case can include a health-related event concerning a single individual or it may refer to multiple health-related events that are occurrences of the same disease or condition of interest to public health.
 
         A public health case definition (Act.moodCode = &quot;definition&quot;) includes the description of the clinical, laboratory, and epidemiologic indicators associated with a disease or condition of interest to public health. There are case definitions for conditions that are reportable, as well as for those that are not. A public health case definition is a construct used by public health for the purpose of counting cases, and should not be used as clinical indications for treatment. Examples include AIDS, toxic-shock syndrome, and salmonellosis and their associated indicators that are used to define a case."></definition>
       </concept>
       <concept>
        <code value="OUTBR"></code>
        <display value="outbreak"></display>
-       <definition value="An Outbreak is a concern resulting from a series of public health cases.
+       <definition value="An Outbreak is a concern resulting from a series of public health cases.
 
         
          UsageNotes: The date on which an outbreak starts is the earliest date of onset among the cases assigned to the outbreak and its ending date is the last date of onset among the cases assigned to the outbreak. The effectiveTime attribute is used to convey the relevant dates for the case. An outbreak definition (Act.moodCode = &quot;definition&quot; includes the criteria for the number, types and occurrence pattern of cases necessary to declare an outbreak and to judge the severity of an outbreak."></definition>
@@ -36202,11 +36202,11 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="CONS"></code>
       <display value="consent"></display>
-      <definition value="The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.
+      <definition value="The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.
 
-        The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act.
+        The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act.
 
-        The &quot;signatures&quot; to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of &quot;performer&quot;, the healthcare provider informing the patient, and &quot;consenter&quot;, the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.
+        The &quot;signatures&quot; to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of &quot;performer&quot;, the healthcare provider informing the patient, and &quot;consenter&quot;, the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.
 
         Some consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed."></definition>
      </concept>
@@ -36223,180 +36223,180 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="DISPACT"></code>
       <display value="disciplinary action"></display>
-      <definition value="An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be 							undesirable.
+      <definition value="An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be 							undesirable.
 
         Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.Examples:"></definition>
      </concept>
      <concept>
       <code value="EXPOS"></code>
       <display value="exposure"></display>
-      <definition value="An interaction between entities that provides opportunity for transmission of a physical, chemical, or biological agent from an exposure source entity to an exposure target entity.
+      <definition value="An interaction between entities that provides opportunity for transmission of a physical, chemical, or biological agent from an exposure source entity to an exposure target entity.
 
         
-         Examples:  The following examples are provided to indicate what interactions are considered exposures rather than other types of Acts:
+         Examples:  The following examples are provided to indicate what interactions are considered exposures rather than other types of Acts:
 
         
          
-          A patient accidentally receives three times the recommended dose of their medication due to a dosing error. 
+          A patient accidentally receives three times the recommended dose of their medication due to a dosing error. 
 
           
            
-            This is a substance administration.  Public health and/or safety authorities may also be interested in documenting this with an associated exposure.
+            This is a substance administration.  Public health and/or safety authorities may also be interested in documenting this with an associated exposure.
 
            
           
          
          
-          A patient accidentally is dispensed an incorrect medicine (e.g., clomiphene instead of clomipramine).  They have taken several doses before the mistake is detected.  They are therefore &quot;exposed&quot; to a medicine that there was no therapeutic indication for them to receive. 
+          A patient accidentally is dispensed an incorrect medicine (e.g., clomiphene instead of clomipramine).  They have taken several doses before the mistake is detected.  They are therefore &quot;exposed&quot; to a medicine that there was no therapeutic indication for them to receive. 
 
           
            
-            There are several substance administrations in this example.  Public health and/or safety authorities may also be interested in documenting this with associated exposures.
+            There are several substance administrations in this example.  Public health and/or safety authorities may also be interested in documenting this with associated exposures.
 
            
           
          
          
-          In a busy medical ward, a patient is receiving chemotherapy for a lymphoma.  Unfortunately, the IV infusion bag containing the medicine splits, spraying cytotoxic medication over the patient being treated and the patient in the adjacent bed. 
+          In a busy medical ward, a patient is receiving chemotherapy for a lymphoma.  Unfortunately, the IV infusion bag containing the medicine splits, spraying cytotoxic medication over the patient being treated and the patient in the adjacent bed. 
 
           
            
-            There are three substance administrations in this example.  The first is the intended one (IV infusion) with its associated (implicit) exposure.  There is an incident with an associated substance administration to the same patient involving the medication sprayed over the patient as well as an associated exposure.  Additionally, the incident includes a substance administration involving the spraying of medication on the adjacent patient, also with an associated exposure.
+            There are three substance administrations in this example.  The first is the intended one (IV infusion) with its associated (implicit) exposure.  There is an incident with an associated substance administration to the same patient involving the medication sprayed over the patient as well as an associated exposure.  Additionally, the incident includes a substance administration involving the spraying of medication on the adjacent patient, also with an associated exposure.
 
            
           
          
          
-          A patient who is a refugee from a war-torn African nation arrives in a busy inner city A&amp;E department suffering from a cough with bloody sputum.  Not understanding the registration and triage process, they sit in the waiting room for several hours before it is noticed that they have not booked in.  As soon as they are being processed, it is suspected that they are suffering from TB.  Vulnerable (immunosuppressed) patients who were sharing the waiting room with this patient may have been exposed to the tubercule bacillus, and must be traced for investigation. 
+          A patient who is a refugee from a war-torn African nation arrives in a busy inner city A&amp;E department suffering from a cough with bloody sputum.  Not understanding the registration and triage process, they sit in the waiting room for several hours before it is noticed that they have not booked in.  As soon as they are being processed, it is suspected that they are suffering from TB.  Vulnerable (immunosuppressed) patients who were sharing the waiting room with this patient may have been exposed to the tubercule bacillus, and must be traced for investigation. 
 
           
            
-            This is an exposure (or possibly multiple exposures) in the waiting room involving the refugee and everyone else in the waiting room during the period.  There might also be a number of known or presumed substance administrations (coughing) via several possible routes.  The substance administrations are only hypotheses until confirmed by further testing.
+            This is an exposure (or possibly multiple exposures) in the waiting room involving the refugee and everyone else in the waiting room during the period.  There might also be a number of known or presumed substance administrations (coughing) via several possible routes.  The substance administrations are only hypotheses until confirmed by further testing.
 
            
           
          
          
-          A patient who has received an elective total hip replacement procedure suffers a prolonged stay in hospital, due to contracting an MRSA infection in the surgical wound site after the surgery. 
+          A patient who has received an elective total hip replacement procedure suffers a prolonged stay in hospital, due to contracting an MRSA infection in the surgical wound site after the surgery. 
 
           
            
-            This is an exposure to MRSA.  Although there was some sort of substance administration, it's possible the exact mechanism for introduction of the MRSA into the wound will not be identified.
+            This is an exposure to MRSA.  Although there was some sort of substance administration, it's possible the exact mechanism for introduction of the MRSA into the wound will not be identified.
 
            
           
          
          
-          Routine maintenance of the X-ray machines at a local hospital reveals a serious breach of the shielding on one of the machines.  Patients who have undergone investigations using that machine in the last month are likely to have been exposed to significantly higher doses of X-rays than was intended, and must be tracked for possible adverse effects. 
+          Routine maintenance of the X-ray machines at a local hospital reveals a serious breach of the shielding on one of the machines.  Patients who have undergone investigations using that machine in the last month are likely to have been exposed to significantly higher doses of X-rays than was intended, and must be tracked for possible adverse effects. 
 
           
            
-            There has been an exposure of each patient who used the machine in the past 30 days. Some patients may have had substance administrations.
+            There has been an exposure of each patient who used the machine in the past 30 days. Some patients may have had substance administrations.
 
            
           
          
          
-          A new member of staff is employed in the laundry processing room of a small cottage hospital, and a misreading of the instructions for adding detergents results in fifty times the usual concentration of cleaning materials being added to a batch of hospital bedding.  As a result, several patients have been exposed to very high levels of detergents still present in the &quot;clean&quot; bedding, and have experienced dermatological reactions to this. 
+          A new member of staff is employed in the laundry processing room of a small cottage hospital, and a misreading of the instructions for adding detergents results in fifty times the usual concentration of cleaning materials being added to a batch of hospital bedding.  As a result, several patients have been exposed to very high levels of detergents still present in the &quot;clean&quot; bedding, and have experienced dermatological reactions to this. 
 
           
            
-            There has been an incident with multiple exposures to several patients.  Although there are substance administrations involving the application of the detergent to the skin of the patients, it is expected that the substance administrations would not be directly documented.
+            There has been an incident with multiple exposures to several patients.  Although there are substance administrations involving the application of the detergent to the skin of the patients, it is expected that the substance administrations would not be directly documented.
 
            
           
          
          
-          Seven patients who are residents in a health care facility for the elderly mentally ill have developed respiratory problems. After several months of various tests having been performed and various medications prescribed to these patients, the problem is traced to their being &quot;sensitive&quot; to a new fungicide used in the wall plaster of the ward where these patients reside.
+          Seven patients who are residents in a health care facility for the elderly mentally ill have developed respiratory problems. After several months of various tests having been performed and various medications prescribed to these patients, the problem is traced to their being &quot;sensitive&quot; to a new fungicide used in the wall plaster of the ward where these patients reside.
 
           
            
-            The patients have been continuously exposed to the fungicide.  Although there have been continuous substance administrations (via breathing) this would not normally be documented as a substance administration.
+            The patients have been continuously exposed to the fungicide.  Although there have been continuous substance administrations (via breathing) this would not normally be documented as a substance administration.
 
            
           
          
          
-          A patient with osteoarthritis of the knees is treated symptomatically using analgesia, paracetamol (acetaminophen) 1g up to four times a day for pain relief.  His GP does not realize that the patient has, 20 years previously (while at college) had severe alcohol addiction problems, and now, although this is completely under control, his liver has suffered significantly, leaving him more sensitive to hepatic toxicity from paracetamol use.  Later that year, the patient returns with a noticeable level of jaundice.  Paracetamol is immediately withdrawn and alternative solutions for the knee pain are sought.  The jaundice gradually subsides with conservative management, but referral to the gastroenterologist is required for advice and monitoring. 
+          A patient with osteoarthritis of the knees is treated symptomatically using analgesia, paracetamol (acetaminophen) 1g up to four times a day for pain relief.  His GP does not realize that the patient has, 20 years previously (while at college) had severe alcohol addiction problems, and now, although this is completely under control, his liver has suffered significantly, leaving him more sensitive to hepatic toxicity from paracetamol use.  Later that year, the patient returns with a noticeable level of jaundice.  Paracetamol is immediately withdrawn and alternative solutions for the knee pain are sought.  The jaundice gradually subsides with conservative management, but referral to the gastroenterologist is required for advice and monitoring. 
 
           
            
-            There is a substance administration with an associated exposure.  The exposure component is based on the relative toxic level of the substance to a patient with a compromised liver function.
+            There is a substance administration with an associated exposure.  The exposure component is based on the relative toxic level of the substance to a patient with a compromised liver function.
 
            
           
          
          
-          A patient goes to their GP complaining of abdominal pain, having been discharged from the local hospital ten days' previously after an emergency appendectomy.  The GP can find nothing particularly amiss, and presumes it is post operative surgical pain that will resolve.  The patient returns a fortnight later, when the GP prescribes further analgesia, but does decide to request an outpatient surgical follow-up appointment.  At this post-surgical outpatient review, the registrar decides to order an ultrasound, which, when performed three weeks later, shows a small faint inexplicable mass.  A laparoscopy is then performed, as a day case procedure, and a piece of a surgical swab is removed from the patient's abdominal cavity.  Thankfully, a full recovery then takes place. 
+          A patient goes to their GP complaining of abdominal pain, having been discharged from the local hospital ten days' previously after an emergency appendectomy.  The GP can find nothing particularly amiss, and presumes it is post operative surgical pain that will resolve.  The patient returns a fortnight later, when the GP prescribes further analgesia, but does decide to request an outpatient surgical follow-up appointment.  At this post-surgical outpatient review, the registrar decides to order an ultrasound, which, when performed three weeks later, shows a small faint inexplicable mass.  A laparoscopy is then performed, as a day case procedure, and a piece of a surgical swab is removed from the patient's abdominal cavity.  Thankfully, a full recovery then takes place. 
 
           
            
-            This is a procedural sequelae.  There may be an Incident recorded for this also.
+            This is a procedural sequelae.  There may be an Incident recorded for this also.
 
            
           
          
          
-          A patient is slightly late for a regular pacemaker battery check in the Cardiology department of the local hospital.  They are hurrying down the second floor corridor.  A sudden summer squall has recently passed over the area, and rain has come in through an open corridor window leaving a small puddle on the corridor floor.  In their haste, the patient slips in the puddle and falls so badly that they have to be taken to the A&amp;E department, where it is discovered on investigation they have slightly torn the cruciate ligament in their left knee. 
+          A patient is slightly late for a regular pacemaker battery check in the Cardiology department of the local hospital.  They are hurrying down the second floor corridor.  A sudden summer squall has recently passed over the area, and rain has come in through an open corridor window leaving a small puddle on the corridor floor.  In their haste, the patient slips in the puddle and falls so badly that they have to be taken to the A&amp;E department, where it is discovered on investigation they have slightly torn the cruciate ligament in their left knee. 
 
           
            
-            This is not an exposure.  There has been an incident.  
+            This is not an exposure.  There has been an incident.  
 
            
           
          
         
         
-         Usage Notes: This class deals only with opportunity and not the outcome of the exposure; i.e. not all exposed parties will necessarily experience actual harm or benefit.
+         Usage Notes: This class deals only with opportunity and not the outcome of the exposure; i.e. not all exposed parties will necessarily experience actual harm or benefit.
 
-        Exposure differs from Substance Administration by the absence of the participation of a performer in the act. 
+        Exposure differs from Substance Administration by the absence of the participation of a performer in the act. 
 
-        The following participations SHOULD be used with the following participations to distinguish the specific entities:
+        The following participations SHOULD be used with the following participations to distinguish the specific entities:
 
         
          
-          The exposed entity participates via the &quot;exposure target&quot; (EXPTRGT) participation.
+          The exposed entity participates via the &quot;exposure target&quot; (EXPTRGT) participation.
 
          
          
-          An entity that has carried the agent transmitted in the exposure participates via the &quot;exposure source&quot; (EXSRC) participation.  For example: 
+          An entity that has carried the agent transmitted in the exposure participates via the &quot;exposure source&quot; (EXSRC) participation.  For example: 
 
           
            
-            a person or animal who carried an infectious disease and interacts (EXSRC) with another person or animal (EXPTRGT) transmitting the disease agent;
+            a person or animal who carried an infectious disease and interacts (EXSRC) with another person or animal (EXPTRGT) transmitting the disease agent;
 
            
            
-            a place or other environment (EXSRC) and a person or animal (EXPTRGT) who is exposed in the presence of this environment.
+            a place or other environment (EXSRC) and a person or animal (EXPTRGT) who is exposed in the presence of this environment.
 
            
           
          
          
-          When it is unknown whether a participating entity is the source of the agent (EXSRC) or the target of the transmission (EXPTRGT), the &quot;exposure participant&quot; (EXPART) is used.
+          When it is unknown whether a participating entity is the source of the agent (EXSRC) or the target of the transmission (EXPTRGT), the &quot;exposure participant&quot; (EXPART) is used.
 
          
          
-          The physical (including energy), chemical or biological substance which is participating in the exposure uses the &quot;exposure agent&quot; (EXPAGNT) participation.  There are at least three scenarios:
+          The physical (including energy), chemical or biological substance which is participating in the exposure uses the &quot;exposure agent&quot; (EXPAGNT) participation.  There are at least three scenarios:
 
           
            
-            the player of the Role that participates as EXPAGNT is the chemical or biological substance mixed or carried by the scoper-entity of the Role (e.g., ingredient role); or 
+            the player of the Role that participates as EXPAGNT is the chemical or biological substance mixed or carried by the scoper-entity of the Role (e.g., ingredient role); or 
 
            
            
-            the player of the Role that participates as EXPAGNT is a mixture known to contain the chemical, radiological or biological substance of interest; or 
+            the player of the Role that participates as EXPAGNT is a mixture known to contain the chemical, radiological or biological substance of interest; or 
 
            
            
-            the player of the Role that participates as a EXPAGNT is known to carry the agent (i.e., the player is a fomite, vector, etc.).
+            the player of the Role that participates as a EXPAGNT is known to carry the agent (i.e., the player is a fomite, vector, etc.).
 
            
           
          
         
-        The Exposure.statusCode attribute should be interpreted as the state of the Exposure business object (e.g., active, aborted, completed) and not the clinical status of the exposure (e.g., probable, confirmed).  The clinical status of the exposure should be associated with the exposure via a subject observation.
+        The Exposure.statusCode attribute should be interpreted as the state of the Exposure business object (e.g., active, aborted, completed) and not the clinical status of the exposure (e.g., probable, confirmed).  The clinical status of the exposure should be associated with the exposure via a subject observation.
 
         
          Design Comment: The usage notes require a clear criterion for determining whether an act is an exposure or substance administration-deleterious potential, uncertainty of actual transmission, or otherwise. SBADM states that the criterion is the presence of a performer-but there are examples above that call this criterion into question (e.g., the first one, concerning a dosing error)."></definition>
@@ -36404,9 +36404,9 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
        <code value="AEXPOS"></code>
        <display value="acquisition exposure"></display>
        <definition value="Description: 
-        
+        
 
-        An acquisition exposure act describes the proximity (location and time) through which the participating entity was potentially exposed to a physical (including energy), chemical or biological agent from another entity.  The acquisition exposure act is used in conjunction with transmission exposure acts as part of an analysis technique for contact tracing.  Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion.
+        An acquisition exposure act describes the proximity (location and time) through which the participating entity was potentially exposed to a physical (including energy), chemical or biological agent from another entity.  The acquisition exposure act is used in conjunction with transmission exposure acts as part of an analysis technique for contact tracing.  Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion.
 
         
          Constraints:  The Acquisition Exposure inherits the participation constraints that apply to Exposure with the following exception.  The EXPSRC (exposure source) participation must never be associated with the Transmission Exposure either directly or via context conduction."></definition>
@@ -36415,9 +36415,9 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
        <code value="TEXPOS"></code>
        <display value="transmission exposure"></display>
        <definition value="Description: 
-        
+        
 
-        A transmission exposure act describes the proximity (time and location) over which the participating source entity was capable of transmitting a physical (including energy), chemical or biological substance agent to another entity.  The transmission exposure act is used in conjunction with acquisition exposure acts as part of an analysis technique for contact tracing.  Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion.
+        A transmission exposure act describes the proximity (time and location) over which the participating source entity was capable of transmitting a physical (including energy), chemical or biological substance agent to another entity.  The transmission exposure act is used in conjunction with acquisition exposure acts as part of an analysis technique for contact tracing.  Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion.
 
         
          Constraints:  The Transmission Exposure inherits the participation constraints that apply to Exposure with the following exception.  The EXPTRGT (exposure target) participation must never be associated with the Transmission Exposure either directly or via context conduction."></definition>
@@ -36431,7 +36431,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="INFRM"></code>
       <display value="inform"></display>
-      <definition value="The act  of transmitting information and understanding about a topic to a subject where the participation association must be SBJ.
+      <definition value="The act  of transmitting information and understanding about a topic to a subject where the participation association must be SBJ.
 
         
          Discussion: This act may be used to request that a patient or provider be informed about an Act, or to indicate that a person was informed about a particular act."></definition>
@@ -36454,43 +36454,43 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="OBS"></code>
       <display value="observation"></display>
-      <definition value="Description:An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The code attribute of Observation and the value attribute of Observation must be considered in combination to determine the semantics of the observation.
+      <definition value="Description:An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The code attribute of Observation and the value attribute of Observation must be considered in combination to determine the semantics of the observation.
 
         
          Discussion:
-        
+        
 
-        Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a  variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter.
+        Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a  variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter.
 
-        As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. 
+        As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. 
 
-        The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology.
+        The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology.
 
-        An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations.
+        An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations.
 
-        Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. 
+        Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. 
 
-        Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation. 
+        Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation. 
 
         
          Examples:
-        
+        
 
         
          
-          Recording the results of a Family History Assessment
+          Recording the results of a Family History Assessment
 
          
          
-          Laboratory test and associated result
+          Laboratory test and associated result
 
          
          
-          Physical exam test and associated result
+          Physical exam test and associated result
 
          
          
-          Device temperature
+          Device temperature
 
          
          
@@ -36525,7 +36525,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
        <concept>
         <code value="_SubjectBodyPosition"></code>
         <display value="subject body position"></display>
-        <definition value="Contains codes for defining the observed, physical position of a subject, such as during an observation, assessment, collection of a specimen, etc.  ECG waveforms and vital signs, such as blood pressure, are two examples where a general, observed position typically needs to be noted.
+        <definition value="Contains codes for defining the observed, physical position of a subject, such as during an observation, assessment, collection of a specimen, etc.  ECG waveforms and vital signs, such as blood pressure, are two examples where a general, observed position typically needs to be noted.
 
         
          
@@ -36542,7 +36542,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
         <concept>
          <code value="LLD"></code>
          <display value="left lateral decubitus"></display>
-         <definition value="Lying on the left side.
+         <definition value="Lying on the left side.
 
         
          
@@ -36556,7 +36556,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
         <concept>
          <code value="PRN"></code>
          <display value="prone"></display>
-         <definition value="Lying with the front or ventral surface downward; lying face down.
+         <definition value="Lying with the front or ventral surface downward; lying face down.
 
         
          
@@ -36570,7 +36570,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
         <concept>
          <code value="RLD"></code>
          <display value="right lateral decubitus"></display>
-         <definition value="Lying on the right side.
+         <definition value="Lying on the right side.
 
         
          
@@ -36584,7 +36584,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
         <concept>
          <code value="SFWL"></code>
          <display value="Semi-Fowler's"></display>
-         <definition value="A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees.
+         <definition value="A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees.
 
         
          
@@ -36598,7 +36598,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
         <concept>
          <code value="SIT"></code>
          <display value="sitting"></display>
-         <definition value="Resting the body on the buttocks, typically with upper torso erect or semi erect.
+         <definition value="Resting the body on the buttocks, typically with upper torso erect or semi erect.
 
         
          
@@ -36612,7 +36612,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
         <concept>
          <code value="STN"></code>
          <display value="standing"></display>
-         <definition value="To be stationary, upright, vertical, on one's legs.
+         <definition value="To be stationary, upright, vertical, on one's legs.
 
         
          
@@ -36635,7 +36635,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
          <concept>
           <code value="RTRD"></code>
           <display value="reverse trendelenburg"></display>
-          <definition value="Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered.
+          <definition value="Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered.
 
         
          
@@ -36649,7 +36649,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
          <concept>
           <code value="TRD"></code>
           <display value="trendelenburg"></display>
-          <definition value="Lying on the back, on an inclined plane, typically about 30-45 degrees, with  head lowered and feet raised.
+          <definition value="Lying on the back, on an inclined plane, typically about 30-45 degrees, with  head lowered and feet raised.
 
         
          
@@ -36666,13 +36666,13 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="ALRT"></code>
        <display value="detected issue"></display>
-       <definition value="An observation identifying a potential adverse outcome as a result of an Act or combination of Acts.
+       <definition value="An observation identifying a potential adverse outcome as a result of an Act or combination of Acts.
 
         
-         Examples: Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria.
+         Examples: Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria.
 
         
-         Discussion: This class is commonly used for identifying 'business rule' or 'process' problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to 'bypass' a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation.
+         Discussion: This class is commonly used for identifying 'business rule' or 'process' problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to 'bypass' a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation.
 
         
          Constraints: the Act or Acts that may cause the the adverse outcome are the target of a subject ActRelationship. The subbtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to repesent a specific problem code (e.g. specific drug-drug interaction id)."></definition>
@@ -36680,10 +36680,10 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="BATTERY"></code>
        <display value="battery"></display>
-       <definition value="Definition: An observation that is composed of a set of observations. These observations typically have a logical or practical grouping for generally accepted clinical or functional purposes, such as observations that are run together because of automation. A battery can define required and optional component observations and, in some cases, will define complex rules that determine whether or not a particular observation is made. BATTERY is a constraint on the Observation class in that it is understood to always be composed of component observations.
+       <definition value="Definition: An observation that is composed of a set of observations. These observations typically have a logical or practical grouping for generally accepted clinical or functional purposes, such as observations that are run together because of automation. A battery can define required and optional component observations and, in some cases, will define complex rules that determine whether or not a particular observation is made. BATTERY is a constraint on the Observation class in that it is understood to always be composed of component observations.
 
         
-         UsageNotes: The focus in a BATTERY is that it is composed of individual observations. In request (RQO) mood, a battery is a request to perform the component observations. In event (EVN) mood a battery is a reporting of associated set of observation events. In definition mood a battery is the definition of the associated set of observations.
+         UsageNotes: The focus in a BATTERY is that it is composed of individual observations. In request (RQO) mood, a battery is a request to perform the component observations. In event (EVN) mood a battery is a reporting of associated set of observation events. In definition mood a battery is the definition of the associated set of observations.
 
         
          Examples: Vital signs, Full blood count, Chemistry panel."></definition>
@@ -36696,7 +36696,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="CNOD"></code>
        <display value="Condition Node"></display>
-       <definition value="An instance of Observation of a Condition at a point in time that includes any Observations or Procedures associated with that Condition as well as links to previous instances of Condition Node for the same Condition
+       <definition value="An instance of Observation of a Condition at a point in time that includes any Observations or Procedures associated with that Condition as well as links to previous instances of Condition Node for the same Condition
 
         
          
@@ -36823,46 +36823,46 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="PCPR"></code>
       <display value="care provision"></display>
-      <definition value="An Act that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care. 
+      <definition value="An Act that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care. 
 
         
-         Discussion: A care provision event may exist without any other care actions taking place. For example, when a patient is assigned to the care of a particular health professional.
+         Discussion: A care provision event may exist without any other care actions taking place. For example, when a patient is assigned to the care of a particular health professional.
 
-        In request (RQO) mood care provision communicates a referral, which is a request:
+        In request (RQO) mood care provision communicates a referral, which is a request:
 
         
          
-          from one party (linked as a participant of type author (AUT)),
+          from one party (linked as a participant of type author (AUT)),
 
          
          
-          to another party (linked as a participant of type performer (PRF),
+          to another party (linked as a participant of type performer (PRF),
 
          
          
-          to take responsibility for a scope specified by the code attribute, 
+          to take responsibility for a scope specified by the code attribute, 
 
          
          
-          for an entity (linked as a participant of type subject (SBJ)).
+          for an entity (linked as a participant of type subject (SBJ)).
 
          
         
-        The scope of the care for which responsibility is taken is identified by code attribute.
+        The scope of the care for which responsibility is taken is identified by code attribute.
 
-        In event (EVN) mood care provision indicates the effective time interval of a specified scope of responsibility by a performer (PRF) or set of performers (PRF) for a subject (SBJ).
+        In event (EVN) mood care provision indicates the effective time interval of a specified scope of responsibility by a performer (PRF) or set of performers (PRF) for a subject (SBJ).
 
         
          Examples:
-        
+        
 
         
          
-          Referral from GP to a specialist.
+          Referral from GP to a specialist.
 
          
          
-          Assignment of a patient or group of patients to the case list of a health professional.
+          Assignment of a patient or group of patients to the case list of a health professional.
 
          
          
@@ -36876,15 +36876,15 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="POLICY"></code>
       <display value="policy"></display>
-      <definition value="Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on:
+      <definition value="Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on:
 
         
          
-          The activity of another party
+          The activity of another party
 
          
          
-          The behavior of another party
+          The behavior of another party
 
          
          
@@ -36892,19 +36892,19 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="JURISPOL"></code>
        <display value="jurisdictional policy"></display>
-       <definition value="Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on:
+       <definition value="Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on:
 
         
          
-          The activity of another party
+          The activity of another party
 
          
          
-          The behavior of another party
+          The behavior of another party
 
          
          
-          The manner in which an act is executed
+          The manner in which an act is executed
 
          
         
@@ -36914,19 +36914,19 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="ORGPOL"></code>
        <display value="organizational policy"></display>
-       <definition value="Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization on:
+       <definition value="Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization on:
 
         
          
-          The activity of another party
+          The activity of another party
 
          
          
-          The behavior of another party
+          The behavior of another party
 
          
          
-          The manner in which an act is executed
+          The manner in which an act is executed
 
          
         
@@ -36936,19 +36936,19 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="SCOPOL"></code>
        <display value="scope of practice policy"></display>
-       <definition value="Description:An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications on:
+       <definition value="Description:An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications on:
 
         
          
-          The activity of another party
+          The activity of another party
 
          
          
-          The behavior of another party
+          The behavior of another party
 
          
          
-          The manner in which an act is executed
+          The manner in which an act is executed
 
          
         
@@ -36958,19 +36958,19 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="STDPOL"></code>
        <display value="standard of practice policy"></display>
-       <definition value="Description:A requirement, rule, or expectation typically documented as guidelines, protocols, or formularies imposed or strongly encouraged by an organization that oversees or has authority over the practices within a domain, and which may have legal basis or ramifications on:
+       <definition value="Description:A requirement, rule, or expectation typically documented as guidelines, protocols, or formularies imposed or strongly encouraged by an organization that oversees or has authority over the practices within a domain, and which may have legal basis or ramifications on:
 
         
          
-          The activity of another party
+          The activity of another party
 
          
          
-          The behavior of another party
+          The behavior of another party
 
          
          
-          The manner in which an act is executed
+          The manner in which an act is executed
 
          
         
@@ -36981,17 +36981,17 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="PROC"></code>
       <display value="procedure"></display>
-      <definition value="An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.
+      <definition value="An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.
 
         
          Examples: : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc."></definition>
       <concept>
        <code value="SBADM"></code>
        <display value="substance administration"></display>
-       <definition value="The act of introducing or otherwise applying a substance to the subject.
+       <definition value="The act of introducing or otherwise applying a substance to the subject.
 
         
-         Discussion: The effect of the substance is typically established on a biochemical basis, however, that is not a requirement. For example, radiotherapy can largely be described in the same way, especially if it is a systemic therapy such as radio-iodine.  This class also includes the application of chemical treatments to an area.
+         Discussion: The effect of the substance is typically established on a biochemical basis, however, that is not a requirement. For example, radiotherapy can largely be described in the same way, especially if it is a systemic therapy such as radio-iodine.  This class also includes the application of chemical treatments to an area.
 
         
          Examples: Chemotherapy protocol; Drug prescription; Vaccination record"></definition>
@@ -37010,7 +37010,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="REG"></code>
       <display value="registration"></display>
-      <definition value="Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role, and includes subjects such as lab exam definitions, drug protocol definitions, prescriptions, persons, patients, practitioners, and equipment.
+      <definition value="Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role, and includes subjects such as lab exam definitions, drug protocol definitions, prescriptions, persons, patients, practitioners, and equipment.
 
         The registration may have a unique identifier - separate from the unique identification of the subject - as well as a core set of related participations and act relationships that characterize the registration event and aid in the disposition of the subject information by a receiving system."></definition>
      </concept>
@@ -37031,17 +37031,17 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="DIET"></code>
        <display value="diet"></display>
-       <definition value="Diet services are supply services, with some aspects resembling Medication services: the detail of the diet is given as a description of the Material associated via Participation.typeCode=&quot;product&quot;. Medically relevant diet types may be communicated in the Diet.code attribute using domain ActDietCode, however, the detail of the food supplied and the various combinations of dishes should be communicated as Material instances.
+       <definition value="Diet services are supply services, with some aspects resembling Medication services: the detail of the diet is given as a description of the Material associated via Participation.typeCode=&quot;product&quot;. Medically relevant diet types may be communicated in the Diet.code attribute using domain ActDietCode, however, the detail of the food supplied and the various combinations of dishes should be communicated as Material instances.
 
         
          Deprecation Note
-        
+        
 
         
-         Class: Use either the Supply class (if dealing with what should be given to the patient) or SubstanceAdministration class (if dealing with what the patient should consume)
+         Class: Use either the Supply class (if dealing with what should be given to the patient) or SubstanceAdministration class (if dealing with what the patient should consume)
 
         
-         energyQuantity: This quantity can be conveyed by using a Content relationship with a quantity attribute expressing the calories
+         energyQuantity: This quantity can be conveyed by using a Content relationship with a quantity attribute expressing the calories
 
         
          carbohydrateQuantity:This quantity can be conveyed using a Content relationship to an Entity with a code of  carbohydrate and a quantity attribute on the content relationship."></definition>
@@ -37059,7 +37059,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="SUBST"></code>
       <display value="Substitution"></display>
-      <definition value="Definition: Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code.
+      <definition value="Definition: Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code.
 
         Rationale: Used to specify &quot;allowed&quot; substitution when creating orders, &quot;actual&quot; susbstitution when sending events, as well as the reason for the substitution and who was responsible for it."></definition>
      </concept>
@@ -37076,9 +37076,9 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
      <concept>
       <code value="XACT"></code>
       <display value="financial transaction"></display>
-      <definition value="A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms.
+      <definition value="A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms.
 
-        In the &quot;intent&quot; mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts.
+        In the &quot;intent&quot; mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts.
 
         In the &quot;event&quot; mood, communicates the posting of a transaction to an account."></definition>
      </concept>
@@ -37106,7 +37106,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <concept>
        <code value="ORGANIZER"></code>
        <display value="organizer"></display>
-       <definition value="Organizer of entries. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or &quot;organizer tree&quot;.
+       <definition value="Organizer of entries. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or &quot;organizer tree&quot;.
 
         The record entries relating to a single clinical session are usually grouped under headings that represent phases of the encounter, or assist with layout and navigation. Clinical headings usually reflect the clinical workflow during a care session, and might also reflect the main author's reasoning processes. Much research has demonstrated that headings are used differently by different professional groups and specialties, and that headings are not used consistently enough to support safe automatic processing of the E H R."></definition>
        <property>
@@ -37256,7 +37256,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
   <fullUrl value="http://hl7.org/fhir/v3/IdentifierScope"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="IdentifierScope"></id>
+    <id value="v3-IdentifierScope"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -37283,7 +37283,7 @@ Members of the OO WG have recently attempted to contact members of RCRIM regardi
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-IdentifierScope"></valueSet>
@@ -37302,7 +37302,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
     <concept>
      <code value="VER"></code>
      <display value="Version Identifier"></display>
-     <definition value="Description: An identifier that references a particular object as it existed at a given point in time. The identifier SHALL change with each state transition on the object. I.e. The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being (though the control act may never be instantiated).
+     <definition value="Description: An identifier that references a particular object as it existed at a given point in time. The identifier SHALL change with each state transition on the object. I.e. The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being (though the control act may never be instantiated).
 
         
          NOTE: Applications that do not support versioning of objects must ignore and not persist these ids to avoid confusion resulting from leaving the same identifier on an object that undergoes changes."></definition>
@@ -37310,10 +37310,10 @@ Codes to specify the scope in which the identifier applies to the object with wh
     <concept>
      <code value="VW"></code>
      <display value="View Specific Identifier"></display>
-     <definition value="Description: An identifier that references a particular object as it existed at a given point in time. The identifier SHALL change with each state transition on the object.
+     <definition value="Description: An identifier that references a particular object as it existed at a given point in time. The identifier SHALL change with each state transition on the object.
 
         
-         Example The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being (though the control act may never be instantiated).
+         Example The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being (though the control act may never be instantiated).
 
         
          NOTE: Applications that do not support versioning of objects must ignore and not persist these ids to avoid confusion resulting from leaving the same identifier on an object that undergoes changes."></definition>
@@ -37325,7 +37325,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
   <fullUrl value="http://hl7.org/fhir/v3/Ethnicity"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="Ethnicity"></id>
+    <id value="v3-Ethnicity"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -37579,7 +37579,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
   <fullUrl value="http://hl7.org/fhir/v3/ActPriority"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActPriority"></id>
+    <id value="v3-ActPriority"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -37696,7 +37696,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
   <fullUrl value="http://hl7.org/fhir/v3/ContainerSeparator"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ContainerSeparator"></id>
+    <id value="v3-ContainerSeparator"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -37745,7 +37745,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
   <fullUrl value="http://hl7.org/fhir/v3/ActExposureLevelCode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActExposureLevelCode"></id>
+    <id value="v3-ActExposureLevelCode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -37814,7 +37814,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
   <fullUrl value="http://hl7.org/fhir/v3/CommunicationFunctionType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="CommunicationFunctionType"></id>
+    <id value="v3-CommunicationFunctionType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -37868,7 +37868,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
   <fullUrl value="http://hl7.org/fhir/v3/ObservationValue"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ObservationValue"></id>
+    <id value="v3-ObservationValue"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -37895,7 +37895,7 @@ Codes to specify the scope in which the identifier applies to the object with wh
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type.  OpenIssue:
+    <description value=" This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be corrected.."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ObservationValue"></valueSet>
@@ -38499,7 +38499,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
      <concept>
       <code value="DENEXCEP"></code>
       <display value="denominator exceptions"></display>
-      <definition value="Denominator exceptions are those conditions that should remove a patient, procedure or unit of measurement from the denominator only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures.  Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories:
+      <definition value="Denominator exceptions are those conditions that should remove a patient, procedure or unit of measurement from the denominator only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures.  Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories:
 
         
          Medical reasons
@@ -38616,7 +38616,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
      <concept>
       <code value="_SECINTOBV"></code>
       <display value="security integrity"></display>
-      <definition value="Abstract security observation values used to indicate security integrity metadata.
+      <definition value="Abstract security observation values used to indicate security integrity metadata.
 
         
          Examples: Codes conveying integrity status, integrity confidence, and provenance."></definition>
@@ -38650,19 +38650,19 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="MAPPED"></code>
         <display value="mapped"></display>
-        <definition value="Security metadata observation value used to indicate that the IT resource semantic content has been transformed from one encoding to another.
+        <definition value="Security metadata observation value used to indicate that the IT resource semantic content has been transformed from one encoding to another.
 
         
-         Usage Note: &quot;MAP&quot; code does not indicate the semantic fidelity of the transformed content.
+         Usage Note: &quot;MAP&quot; code does not indicate the semantic fidelity of the transformed content.
 
-        To indicate semantic fidelity for maps of HL7 to other code systems, this security alteration integrity observation may be further specified using an Act valued with Value Set: MapRelationship (2.16.840.1.113883.1.11.11052).
+        To indicate semantic fidelity for maps of HL7 to other code systems, this security alteration integrity observation may be further specified using an Act valued with Value Set: MapRelationship (2.16.840.1.113883.1.11.11052).
 
         Semantic fidelity of the mapped IT Resource may also be indicated using a SecurityIntegrityConfidenceObservation."></definition>
        </concept>
        <concept>
         <code value="MASKED"></code>
         <display value="masked"></display>
-        <definition value="Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by indicating the mechanism by which software systems can make data unintelligible (that is, as unreadable and unusable by algorithmically transforming plaintext into ciphertext) such that it can only be accessed or used by authorized users.  An authorized user may be provided a key to decrypt per license or &quot;shared secret&quot;.
+        <definition value="Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability) by indicating the mechanism by which software systems can make data unintelligible (that is, as unreadable and unusable by algorithmically transforming plaintext into ciphertext) such that it can only be accessed or used by authorized users.  An authorized user may be provided a key to decrypt per license or &quot;shared secret&quot;.
 
         
          Usage Note: &quot;MASKED&quot; may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has been further encrypted, and may be accessed only by an authorized user or receiver to which a decryption key is provided."></definition>
@@ -38670,7 +38670,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="PSEUDED"></code>
         <display value="pseudonymized"></display>
-        <definition value="Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability), by indicating the mechanism by which software systems can strip portions of the resource that could allow the identification of the source of the information or the information subject.  Custodian may retain a key to relink data necessary to reidentify the information subject.
+        <definition value="Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability), by indicating the mechanism by which software systems can strip portions of the resource that could allow the identification of the source of the information or the information subject.  Custodian may retain a key to relink data necessary to reidentify the information subject.
 
         
          Rationale: Personal data which has been processed to make it impossible to know whose data it is. Used particularly for secondary use of health data. In some cases, it may be possible for authorized individuals to restore the identity of the individual, e.g.,for public health case management.  Based on ISO/TS 25237:2008 Health informatics—Pseudonymization"></definition>
@@ -38678,7 +38678,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="REDACTED"></code>
         <display value="redacted"></display>
-        <definition value="Security metadata observation value used to indicate the mechanism by which software systems can filter an IT resource (data, information object, service, or system capability) to remove any portion of the resource that is not authorized to be access, used, or disclosed.
+        <definition value="Security metadata observation value used to indicate the mechanism by which software systems can filter an IT resource (data, information object, service, or system capability) to remove any portion of the resource that is not authorized to be access, used, or disclosed.
 
         
          Usage Note: &quot;REDACTED&quot; may be used, per applicable policy, as a flag to indicate to a user or receiver that some portion of an IT resource has filtered and not included in the content accessed or received."></definition>
@@ -38686,7 +38686,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="SUBSETTED"></code>
         <display value="subsetted"></display>
-        <definition value="Metadata observation used to indicate that some information has been removed from the source object when the view this object contains was constructed because of configuration options when the view was created. The content may not be suitable for use as the basis of a record update
+        <definition value="Metadata observation used to indicate that some information has been removed from the source object when the view this object contains was constructed because of configuration options when the view was created. The content may not be suitable for use as the basis of a record update
 
         
          Usage Note: This is not suitable to be used when information is removed for security reasons - see the code REDACTED for this use."></definition>
@@ -38694,7 +38694,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="SYNTAC"></code>
         <display value="syntactic transform"></display>
-        <definition value="Security metadata observation value used to indicate that the IT resource syntax has been transformed from one syntactical representation to another.  
+        <definition value="Security metadata observation value used to indicate that the IT resource syntax has been transformed from one syntactical representation to another.  
 
         
          Usage Note: &quot;SYNTAC&quot; code does not indicate the syntactical correctness of the syntactically transformed IT resource."></definition>
@@ -38702,19 +38702,19 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="TRSLT"></code>
         <display value="translated"></display>
-        <definition value="Security metadata observation value used to indicate that the IT resource has been translated from one human language to another.  
+        <definition value="Security metadata observation value used to indicate that the IT resource has been translated from one human language to another.  
 
         
-         Usage Note: &quot;TRSLT&quot; does not indicate the fidelity of the translation or the languages translated.
+         Usage Note: &quot;TRSLT&quot; does not indicate the fidelity of the translation or the languages translated.
 
-        The fidelity of the IT Resource translation may be indicated using a SecurityIntegrityConfidenceObservation.
+        The fidelity of the IT Resource translation may be indicated using a SecurityIntegrityConfidenceObservation.
 
         To indicate languages, use the Value Set:HumanLanguage (2.16.840.1.113883.1.11.11526)"></definition>
        </concept>
        <concept>
         <code value="VERSIONED"></code>
         <display value="versioned"></display>
-        <definition value="Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability)  which indicates that the resource only retains versions of an IT resource  for access and use per applicable policy
+        <definition value="Security metadata observation value conveying the alteration integrity of an IT resource (data, information object, service, or system capability)  which indicates that the resource only retains versions of an IT resource  for access and use per applicable policy
 
         
          Usage Note: When this code is used, expectation is that the system has removed historical versions of the data that falls outside the time period deemed to be the effective time of the applicable version."></definition>
@@ -38723,7 +38723,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
       <concept>
        <code value="_SECDATINTOBV"></code>
        <display value="data integrity"></display>
-       <definition value="Abstract security observation values used to indicate data integrity metadata.
+       <definition value="Abstract security observation values used to indicate data integrity metadata.
 
         
          Examples: Codes conveying the mechanism used to preserve the accuracy and consistency of an IT resource such as a digital signature and a cryptographic hash function."></definition>
@@ -38734,14 +38734,14 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="CRYTOHASH"></code>
         <display value="cryptographic hash function"></display>
-        <definition value="Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit.
+        <definition value="Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit.
 
         
-         Rationale: This definition is intended to align with the ISO 22600-2 3.3.19 definition of cryptographic checkvalue: Information which is derived by performing a cryptographic transformation (see cryptography) on the data unit.  The derivation of the checkvalue may be performed in one or more steps and is a result of a mathematical function of the key and a data unit. It is usually used to check the integrity of a data unit.
+         Rationale: This definition is intended to align with the ISO 22600-2 3.3.19 definition of cryptographic checkvalue: Information which is derived by performing a cryptographic transformation (see cryptography) on the data unit.  The derivation of the checkvalue may be performed in one or more steps and is a result of a mathematical function of the key and a data unit. It is usually used to check the integrity of a data unit.
 
         
          Examples: 
-        
+        
 
         
          SHA-1
@@ -38750,7 +38750,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="DIGSIG"></code>
         <display value="digital signature"></display>
-        <definition value="Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified.  
+        <definition value="Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified.  
 
         
          Rationale: This definition is intended to align with the ISO 22600-2 3.3.26 definition of digital signature:  Data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g., by the recipient."></definition>
@@ -38759,7 +38759,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
       <concept>
        <code value="_SECINTCONOBV"></code>
        <display value="integrity confidence"></display>
-       <definition value="Abstract security observation value used to indicate integrity confidence metadata.
+       <definition value="Abstract security observation value used to indicate integrity confidence metadata.
 
         
          Examples: Codes conveying the level of reliability and trustworthiness of an IT resource."></definition>
@@ -38791,7 +38791,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
       <concept>
        <code value="_SECINTPRVOBV"></code>
        <display value="provenance"></display>
-       <definition value="Abstract security metadata observation value used to indicate the provenance of an IT resource (data, information object, service, or system capability).
+       <definition value="Abstract security metadata observation value used to indicate the provenance of an IT resource (data, information object, service, or system capability).
 
         
          Examples: Codes conveying the provenance metadata about the entity reporting an IT resource."></definition>
@@ -38802,7 +38802,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="_SECINTPRVABOBV"></code>
         <display value="provenance asserted by"></display>
-        <definition value="Abstract security provenance metadata observation value used to indicate the entity that asserted an IT resource (data, information object, service, or system capability).
+        <definition value="Abstract security provenance metadata observation value used to indicate the entity that asserted an IT resource (data, information object, service, or system capability).
 
         
          Examples: Codes conveying the provenance metadata about the entity asserting the resource."></definition>
@@ -38854,7 +38854,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="_SECINTPRVRBOBV"></code>
         <display value="provenance reported by"></display>
-        <definition value="Abstract security provenance metadata observation value used to indicate the entity that reported the resource (data, information object, service, or system capability).
+        <definition value="Abstract security provenance metadata observation value used to indicate the entity that reported the resource (data, information object, service, or system capability).
 
         
          Examples: Codes conveying the provenance metadata about the entity reporting an IT resource."></definition>
@@ -38927,7 +38927,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
       <concept>
        <code value="TRSTCERTOBV"></code>
        <display value="trust certificate observation"></display>
-       <definition value="Values for security trust certificate metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1]
+       <definition value="Values for security trust certificate metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1]
 
         For example, a Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements.  A particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range.  Another example is Cross Certification with Federal Bridge."></definition>
       </concept>
@@ -38942,7 +38942,7 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
        <concept>
         <code value="LOAAN"></code>
         <display value="authentication level of assurance value"></display>
-        <definition value="The value assigned as the indicator of the digital quality or reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2]
+        <definition value="The value assigned as the indicator of the digital quality or reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2]
 
         For example, the degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]"></definition>
         <property>
@@ -38952,18 +38952,18 @@ Description copied from Concept Domain of same name.  Must be corrected.."></des
         <concept>
          <code value="LOAAN1"></code>
          <display value="low authentication level of assurance"></display>
-         <definition value="Indicator of low digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
+         <definition value="Indicator of low digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
 
-        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 
+        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 
 
         Low authentication level of assurance indicates that the relying party may have little or no confidence in the asserted identity's validity. Level 1 requires little or no confidence in the asserted identity. No identity proofing is required at this level, but the authentication mechanism should provide some assurance that the same claimant is accessing the protected transaction or data. A wide range of available authentication technologies can be employed and any of the token methods of Levels 2, 3, or 4, including Personal Identification Numbers (PINs), may be used. To be authenticated, the claimant must prove control of the token through a secure authentication protocol. At Level 1, long-term shared authentication secrets may be revealed to verifiers.  Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol.   [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
         <concept>
          <code value="LOAAN2"></code>
          <display value="basic authentication level of assurance"></display>
-         <definition value="Indicator of basic digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
+         <definition value="Indicator of basic digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
 
-        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]
+        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]
 
         Basic authentication level of assurance indicates that the relying party may have some confidence in the asserted identity's validity. Level 2 requires confidence that the asserted identity is accurate. Level 2 provides for single-factor remote network authentication, including identity-proofing requirements for presentation of identifying materials or information. A wide range of available authentication technologies can be employed, including any of the token methods of Levels 3 or 4, as well as passwords. Successful authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token.  Eavesdropper, replay, and online guessing attacks are prevented.  
 Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Approved cryptographic techniques are required. Assertions issued about claimants as a result of a successful authentication are either cryptographically authenticated by relying parties (using approved methods) or are obtained directly from a trusted party via a secure authentication protocol.   [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
@@ -38971,11 +38971,11 @@ Long-term shared authentication secrets, if used, are never revealed to any part
         <concept>
          <code value="LOAAN3"></code>
          <display value="medium authentication level of assurance"></display>
-         <definition value="Indicator of medium digital quality or reliability of the digital reliability of verification and validation of the process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
+         <definition value="Indicator of medium digital quality or reliability of the digital reliability of verification and validation of the process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
 
-        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 
+        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies] 
 
-        Medium authentication level of assurance indicates that the relying party may have high confidence in the asserted identity's validity.  Level 3 is appropriate for transactions that need high confidence in the accuracy of the asserted identity. Level 3 provides multifactor remote network authentication. At this level, identity-proofing procedures require verification of identifying materials and information. Authentication is based on proof of possession of a key or password through a cryptographic protocol. Cryptographic strength mechanisms should protect the primary authentication token (a cryptographic key) against compromise by the protocol threats, including eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks. A minimum of two authentication factors is required. Three kinds of tokens may be used:
+        Medium authentication level of assurance indicates that the relying party may have high confidence in the asserted identity's validity.  Level 3 is appropriate for transactions that need high confidence in the accuracy of the asserted identity. Level 3 provides multifactor remote network authentication. At this level, identity-proofing procedures require verification of identifying materials and information. Authentication is based on proof of possession of a key or password through a cryptographic protocol. Cryptographic strength mechanisms should protect the primary authentication token (a cryptographic key) against compromise by the protocol threats, including eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks. A minimum of two authentication factors is required. Three kinds of tokens may be used:
 
         
          &quot;soft&quot; cryptographic token, which has the key stored on a general-purpose computer, 
@@ -38987,11 +38987,11 @@ Long-term shared authentication secrets, if used, are never revealed to any part
         <concept>
          <code value="LOAAN4"></code>
          <display value="high authentication level of assurance"></display>
-         <definition value="Indicator of high digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
+         <definition value="Indicator of high digital quality or reliability of the digital reliability of the verification and validation process used to verify the claimed identity of an entity by securely associating an identifier and its authenticator. [Based on ISO 7498-2] 
 
-        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]
+        The degree of confidence in the vetting process used to establish the identity of the individual to whom the credential was issued, and 2) the degree of confidence that the individual who uses the credential is the individual to whom the credential was issued. [OMB M-04-04 E-Authentication Guidance for Federal Agencies]
 
-        High authentication level of assurance indicates that the relying party may have very high confidence in the asserted identity's validity. Level 4 is for transactions that need very high confidence in the accuracy of the asserted identity. Level 4 provides the highest practical assurance of remote network authentication. Authentication is based on proof of possession of a key through a cryptographic protocol. This level is similar to Level 3 except that only “hard� cryptographic tokens are allowed, cryptographic module validation requirements are strengthened, and subsequent critical data transfers must be authenticated via a key that is bound to the authentication process. The token should be a hardware cryptographic module validated at FIPS 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. This level requires a physical token, which cannot readily be copied, and operator authentication at Level 2 and higher, and ensures good, two-factor remote authentication.
+        High authentication level of assurance indicates that the relying party may have very high confidence in the asserted identity's validity. Level 4 is for transactions that need very high confidence in the accuracy of the asserted identity. Level 4 provides the highest practical assurance of remote network authentication. Authentication is based on proof of possession of a key through a cryptographic protocol. This level is similar to Level 3 except that only “hard� cryptographic tokens are allowed, cryptographic module validation requirements are strengthened, and subsequent critical data transfers must be authenticated via a key that is bound to the authentication process. The token should be a hardware cryptographic module validated at FIPS 140-2 Level 2 or higher overall with at least FIPS 140-2 Level 3 physical security. This level requires a physical token, which cannot readily be copied, and operator authentication at Level 2 and higher, and ensures good, two-factor remote authentication.
 
         Level 4 requires strong cryptographic authentication of all parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the claimant prove through a secure authentication protocol that the claimant controls the token. Eavesdropper, replay, online guessing, verifier impersonation, and man-in-the-middle attacks are prevented. Long-term shared authentication secrets, if used, are never revealed to any party except the claimant and verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent verifiers by the CSP. Strong approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process.   [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
@@ -39007,30 +39007,30 @@ Long-term shared authentication secrets, if used, are never revealed to any part
         <concept>
          <code value="LOAAP1"></code>
          <display value="low authentication process level of assurance"></display>
-         <definition value="Indicator of the low digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
+         <definition value="Indicator of the low digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
 
         Low authentication process level of assurance indicates that (1) long-term shared authentication secrets may be revealed to verifiers; and (2) assertions and assertion references require protection from manufacture/modification and reuse attacks.  [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
         <concept>
          <code value="LOAAP2"></code>
          <display value="basic authentication process level of assurance"></display>
-         <definition value="Indicator of the basic digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
+         <definition value="Indicator of the basic digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
 
         Basic authentication process level of assurance indicates that long-term shared authentication secrets are never revealed to any other party except Credential Service Provider (CSP).  Sessions (temporary) shared secrets may be provided to independent verifiers by CSP. Long-term shared authentication secrets, if used, are never revealed to any other party except Verifiers operated by the Credential Service Provider (CSP); however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 1 requirements, assertions are resistant to disclosure, redirection, capture and substitution attacks. Approved cryptographic techniques are required.  [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
         <concept>
          <code value="LOAAP3"></code>
          <display value="medium authentication process level of assurance"></display>
-         <definition value="Indicator of the medium digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
+         <definition value="Indicator of the medium digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
 
-        Medium authentication process level of assurance indicates that the token can be unlocked with password, biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication.  Long-term shared authentication secrets are never revealed to any party except the Claimant and Credential Service Provider (CSP).
+        Medium authentication process level of assurance indicates that the token can be unlocked with password, biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication.  Long-term shared authentication secrets are never revealed to any party except the Claimant and Credential Service Provider (CSP).
 
         Authentication requires that the Claimant prove, through a secure authentication protocol, that he or she controls the token. The Claimant unlocks the token with a password or biometric, or uses a secure multi-token authentication protocol to establish two-factor authentication (through proof of possession of a physical or software token in combination with some memorized secret knowledge). Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. In addition to Level 2 requirements, assertions are protected against repudiation by the Verifier."></definition>
         </concept>
         <concept>
          <code value="LOAAP4"></code>
          <display value="high authentication process level of assurance"></display>
-         <definition value="Indicator of the high digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
+         <definition value="Indicator of the high digital quality or reliability of a defined sequence of messages between a Claimant and a Verifier that demonstrates that the Claimant has possession and control of a valid token to establish his/her identity, and optionally, demonstrates to the Claimant that he or she is communicating with the intended Verifier. [Based on NIST SP 800-63-2]
 
         High authentication process level of assurance indicates all sensitive data transfer are cryptographically authenticated using keys bound to the authentication process.  Level 4 requires strong cryptographic authentication of all communicating parties and all sensitive data transfers between the parties. Either public key or symmetric key technology may be used. Authentication requires that the Claimant prove through a secure authentication protocol that he or she controls the token. All protocol threats at Level 3 are required to be prevented at Level 4. Protocols shall also be strongly resistant to man-in-the-middle attacks. Long-term shared authentication secrets, if used, are never revealed to any party except the Claimant and Verifiers operated directly by the CSP; however, session (temporary) shared secrets may be provided to independent Verifiers by the CSP. Approved cryptographic techniques are used for all operations. All sensitive data transfers are cryptographically authenticated using keys bound to the authentication process.   [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
@@ -39046,28 +39046,28 @@ Long-term shared authentication secrets, if used, are never revealed to any part
         <concept>
          <code value="LOAAS1"></code>
          <display value="low assertion level of assurance"></display>
-         <definition value="Indicator of the low quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
+         <definition value="Indicator of the low quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
 
         Assertions and assertion references require protection from modification and reuse attacks.  [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
         <concept>
          <code value="LOAAS2"></code>
          <display value="basic assertion level of assurance"></display>
-         <definition value="Indicator of the basic quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
+         <definition value="Indicator of the basic quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
 
         Assertions are resistant to disclosure, redirection, capture and substitution attacks.  Approved cryptographic techniques are required for all assertion protocols.  [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
         <concept>
          <code value="LOAAS3"></code>
          <display value="medium assertion level of assurance"></display>
-         <definition value="Indicator of the medium quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
+         <definition value="Indicator of the medium quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
 
         Assertions are protected against repudiation by the verifier.  [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
         <concept>
          <code value="LOAAS4"></code>
          <display value="high assertion level of assurance"></display>
-         <definition value="Indicator of the high quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
+         <definition value="Indicator of the high quality or reliability of the statement from a Verifier to a Relying Party (RP) that contains identity information about a Subscriber. Assertions may also contain verified attributes.
 
         Strongly resistant to man-in-the-middle attacks. &quot;Bearer&quot; assertions are not used.  &quot;Holder-of-key&quot; assertions may be used. RP maintains records of the assertions.  [Summary of the technical requirements specified in NIST SP 800-63 for the four levels of assurance defined by the December 2003, the Office of Management and Budget (OMB) issued Memorandum M-04-04, E-Authentication Guidance for Federal Agencies.]"></definition>
         </concept>
@@ -39306,7 +39306,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
     <concept>
      <code value="_VerificationOutcomeValue"></code>
      <display value="verification outcome"></display>
-     <definition value="Values for observations of verification act results
+     <definition value="Values for observations of verification act results
 
         
          Examples: Verified, not verified, verified with warning."></definition>
@@ -39409,7 +39409,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
   <fullUrl value="http://hl7.org/fhir/v3/EducationLevel"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EducationLevel"></id>
+    <id value="v3-EducationLevel"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -39493,7 +39493,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
   <fullUrl value="http://hl7.org/fhir/v3/EntityStatus"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityStatus"></id>
+    <id value="v3-EntityStatus"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -39567,7 +39567,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
   <fullUrl value="http://hl7.org/fhir/v3/PatientImportance"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="PatientImportance"></id>
+    <id value="v3-PatientImportance"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -39651,7 +39651,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
   <fullUrl value="http://hl7.org/fhir/v3/EntityDeterminer"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityDeterminer"></id>
+    <id value="v3-EntityDeterminer"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -39698,7 +39698,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
     <concept>
      <code value="INSTANCE"></code>
      <display value="specific"></display>
-     <definition value="Description:A determiner that specifies that the Entity object represents a particular physical thing (as opposed to a universal, kind, or class of physical thing).
+     <definition value="Description:A determiner that specifies that the Entity object represents a particular physical thing (as opposed to a universal, kind, or class of physical thing).
 
         
          Discussion: It does not matter whether an INSTANCE still exists as a whole at the point in time (or process) when we mention it, for example, a drug product lot is an INSTANCE even though it has been portioned out for retail purpose."></definition>
@@ -39738,7 +39738,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
   <fullUrl value="http://hl7.org/fhir/v3/LocalMarkupIgnore"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="LocalMarkupIgnore"></id>
+    <id value="v3-LocalMarkupIgnore"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -39787,7 +39787,7 @@ Long-term shared authentication secrets, if used, are never revealed to any part
   <fullUrl value="http://hl7.org/fhir/v3/LanguageAbilityMode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="LanguageAbilityMode"></id>
+    <id value="v3-LanguageAbilityMode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -39814,8 +39814,8 @@ Long-term shared authentication secrets, if used, are never revealed to any part
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A value representing the method of expression of the language.  Example:
-Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.  OpenIssue:
+    <description value=" A value representing the method of expression of the language.  Example:
+Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-LanguageAbilityMode"></valueSet>
@@ -39858,7 +39858,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/ParticipationType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ParticipationType"></id>
+    <id value="v3-ParticipationType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -39961,20 +39961,20 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="AUT"></code>
        <display value="author (originator)"></display>
-       <definition value="Definition: A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act.
+       <definition value="Definition: A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act.
 
         
-         Example: the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship. 
+         Example: the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship. 
 
-        Examples of such policies might include:
+        Examples of such policies might include:
 
         
          
-          The author and anyone they explicitly delegate may update the report;
+          The author and anyone they explicitly delegate may update the report;
 
          
          
-          All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic;
+          All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic;
 
          
         
@@ -40013,10 +40013,10 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="ALY"></code>
        <display value="analyte"></display>
-       <definition value="The target of an Observation action. Links an observation to a Role whose player is the substance or most specific component entity (material, micro-organism, etc.) being measured within the subject.
+       <definition value="The target of an Observation action. Links an observation to a Role whose player is the substance or most specific component entity (material, micro-organism, etc.) being measured within the subject.
 
         
-         Examples: A &quot;plasma porcelain substance concentration&quot; has analyte a Role with player substance Entity &quot;porcelain&quot;.
+         Examples: A &quot;plasma porcelain substance concentration&quot; has analyte a Role with player substance Entity &quot;porcelain&quot;.
 
         
          UsageNotes: The Role that this participation connects to may be any Role whose player is that substance measured. Very often, the scoper may indicate the system in which the component is being measured. E.g., for &quot;plasma porcelain&quot; the scoper could be &quot;Plasma&quot;."></definition>
@@ -40048,7 +40048,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="DEV"></code>
        <display value="device"></display>
-       <definition value="Participant used in performing the act without being substantially affected by the act (i.e. durable or inert with respect to that particular service).
+       <definition value="Participant used in performing the act without being substantially affected by the act (i.e. durable or inert with respect to that particular service).
 
         
          Examples: monitoring equipment, tools, but also access/drainage lines, prostheses, pace maker, etc."></definition>
@@ -40096,10 +40096,10 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="SBJ"></code>
        <display value="subject"></display>
-       <definition value="The principle target on which the action happens.
+       <definition value="The principle target on which the action happens.
 
         
-         Examples: The patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). 
+         Examples: The patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). 
 
         
          UsageNotes: Not all direct targets are subjects. Consumables and devices used as tools for an act are not subjects. However, a device may be a subject of a maintenance action."></definition>
@@ -40117,14 +40117,14 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="BEN"></code>
        <display value="beneficiary"></display>
-       <definition value="Target on behalf of whom the service happens, but that is not necessarily present in the service.  Can occur together with direct target to indicate that a target is both, as in the case where the patient is the indirect beneficiary of a service rendered to a family member, e.g. counseling or given home care instructions.  This concept includes a participant, such as a covered party, who derives benefits from a service act covered by a coverage act.
+       <definition value="Target on behalf of whom the service happens, but that is not necessarily present in the service.  Can occur together with direct target to indicate that a target is both, as in the case where the patient is the indirect beneficiary of a service rendered to a family member, e.g. counseling or given home care instructions.  This concept includes a participant, such as a covered party, who derives benefits from a service act covered by a coverage act.
 
         Note that the semantic role of the intended recipient who benefits from the happening denoted by the verb in the clause.  Thus, a patient who has no coverage under a policy or program may be a beneficiary of a health service while not being the beneficiary of coverage for that service."></definition>
       </concept>
       <concept>
        <code value="CAGNT"></code>
        <display value="causative agent"></display>
-       <definition value="Definition: A factor, such as a microorganism, chemical substance, or form of radiation, whose presence, excessive presence, or (in deficiency diseases) relative absence is essential, in whole or in part, for the occurrence of a condition.
+       <definition value="Definition: A factor, such as a microorganism, chemical substance, or form of radiation, whose presence, excessive presence, or (in deficiency diseases) relative absence is essential, in whole or in part, for the occurrence of a condition.
 
         Constraint:  The use of this participation is limited to observations."></definition>
       </concept>
@@ -40136,7 +40136,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="GUAR"></code>
        <display value="guarantor party"></display>
-       <definition value="The target person or organization contractually recognized by the issuer as a participant who has assumed fiscal responsibility for another personaTMs financial obligations by guaranteeing to pay for amounts owed to a particular account
+       <definition value="The target person or organization contractually recognized by the issuer as a participant who has assumed fiscal responsibility for another personaTMs financial obligations by guaranteeing to pay for amounts owed to a particular account
 
         
          Example:The subscriber of the patientaTMs health insurance policy signs a contract with the provider to be fiscally responsible for the patient billing account balance amount owed."></definition>
@@ -40174,7 +40174,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <concept>
        <code value="REFB"></code>
        <display value="Referred By"></display>
-       <definition value="A participant (e.g. provider) who has referred the subject of an act (e.g. patient).
+       <definition value="A participant (e.g. provider) who has referred the subject of an act (e.g. patient).
 
         Typically, a referred by participant will provide a report (e.g. referral)."></definition>
       </concept>
@@ -40222,10 +40222,10 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
      <concept>
       <code value="PRF"></code>
       <display value="performer"></display>
-      <definition value="Definition: A person, non-person living subject, organization or device that who actually and principally carries out the action. Device should only be assigned as a performer in circumstances where the device is performing independent of human intervention.  Need not be the principal responsible actor.
+      <definition value="Definition: A person, non-person living subject, organization or device that who actually and principally carries out the action. Device should only be assigned as a performer in circumstances where the device is performing independent of human intervention.  Need not be the principal responsible actor.
 
         
-         Exampe: A surgery resident operating under supervision of attending surgeon, a search and rescue dog locating survivors, an electronic laboratory analyzer or the laboratory discipline requested to perform a laboratory test. The performer may also be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event.
+         Exampe: A surgery resident operating under supervision of attending surgeon, a search and rescue dog locating survivors, an electronic laboratory analyzer or the laboratory discipline requested to perform a laboratory test. The performer may also be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event.
 
         
          Note: that existing HL7 designs assign an organization as the playing entity of the Role that is the performer.  These designs should be revised in subsequent releases to make this the scooping entity for the role involved."></definition>
@@ -40248,7 +40248,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
      <concept>
       <code value="RESP"></code>
       <display value="responsible party"></display>
-      <definition value="The person or organization that has primary responsibility for the act.  The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate, and the duty to review actions with the performing actor after the fact.  This responsibility may be ethical, legal, contractual, fiscal, or fiduciary in nature.
+      <definition value="The person or organization that has primary responsibility for the act.  The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate, and the duty to review actions with the performing actor after the fact.  This responsibility may be ethical, legal, contractual, fiscal, or fiduciary in nature.
 
         
          Example: A person who is the head of a biochemical laboratory; a sponsor for a policy or government program."></definition>
@@ -40276,7 +40276,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/CalendarType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="CalendarType"></id>
+    <id value="v3-CalendarType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -40320,7 +40320,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/RoleLinkStatus"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="RoleLinkStatus"></id>
+    <id value="v3-RoleLinkStatus"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -40347,7 +40347,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-RoleLinkStatus"></valueSet>
@@ -40390,7 +40390,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/AddressUse"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="AddressUse"></id>
+    <id value="v3-AddressUse"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -40464,7 +40464,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
      <concept>
       <code value="OLD"></code>
       <display value="no longer in use"></display>
-      <definition value="This address is no longer in use.
+      <definition value="This address is no longer in use.
 
         
          Usage Note: Address may also carry valid time ranges. This code is used to cover the situations where it is known that the address is no longer valid, but no particular time range for its use is known."></definition>
@@ -40545,7 +40545,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/LocalRemoteControlState"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="LocalRemoteControlState"></id>
+    <id value="v3-LocalRemoteControlState"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -40594,7 +40594,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/GTSAbbreviation"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="GTSAbbreviation"></id>
+    <id value="v3-GTSAbbreviation"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -40828,7 +40828,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/ParticipationFunction"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ParticipationFunction"></id>
+    <id value="v3-ParticipationFunction"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -41088,7 +41088,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
      <code value="COMPOSER"></code>
      <display value="composer software"></display>
      <definition value="A device used by an author to record new information, which may also be used by the author to select existing information for aggregation with newly recorded information for the purpose of generating a new artifact.
-         UsageConstraint: COMPOSER ParticipationFunction should be used with DEV (device) ParticipationType.
+         UsageConstraint: COMPOSER ParticipationFunction should be used with DEV (device) ParticipationType.
 
         
          Usage Note: This code will enable implementers to more specifically represent the manner in which a Device participated in and facilitated the generation of a CDA Clinical Document or a CDA Entry by the responsible Author, which is comprised of the Author's newly entered content, and may include the pre-existing content selected by the Author, for the purpose of establishing the provenance and accountability for these acts."></definition>
@@ -41126,10 +41126,10 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
     <concept>
      <code value="REVIEWER"></code>
      <display value="reviewer"></display>
-     <definition value="A verifier who is accountable for reviewing and asserting that the verification of an Act complies with jurisdictional or organizational policy.
+     <definition value="A verifier who is accountable for reviewing and asserting that the verification of an Act complies with jurisdictional or organizational policy.
 
         
-         UsageConstraint: UsageConstraint:  Specifies the exact function that an actor is authorized to have as a verifier of an Act.  Connotes that a specialized verifier asserts compliance for veracity of the review per jurisdictional or organizational policy.  E.g., The Provider who takes responsibility for authenticity of a record submitted to a payer.
+         UsageConstraint: UsageConstraint:  Specifies the exact function that an actor is authorized to have as a verifier of an Act.  Connotes that a specialized verifier asserts compliance for veracity of the review per jurisdictional or organizational policy.  E.g., The Provider who takes responsibility for authenticity of a record submitted to a payer.
 
         REVIEW ParticipationFunction should be used with VFR (verifier)"></definition>
     </concept>
@@ -41160,7 +41160,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/TableCellHorizontalAlign"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TableCellHorizontalAlign"></id>
+    <id value="v3-TableCellHorizontalAlign"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -41224,7 +41224,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/SpecimenType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="SpecimenType"></id>
+    <id value="v3-SpecimenType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -41893,7 +41893,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/HtmlLinkType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="HtmlLinkType"></id>
+    <id value="v3-HtmlLinkType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42007,7 +42007,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
   <fullUrl value="http://hl7.org/fhir/v3/EntityNameUseR2"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityNameUseR2"></id>
+    <id value="v3-EntityNameUseR2"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42034,7 +42034,7 @@ Codes representing possible states of a RoleLink, as defined by the RoleLink cla
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 A set of codes advising a system or user which name in a set of names to select for a given purpose."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-EntityNameUseR2"></valueSet>
@@ -42151,7 +42151,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/ActSite"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActSite"></id>
+    <id value="v3-ActSite"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42474,7 +42474,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/EntityNamePartType"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityNamePartType"></id>
+    <id value="v3-EntityNamePartType"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42538,7 +42538,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/TimingEvent"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TimingEvent"></id>
+    <id value="v3-TimingEvent"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42658,14 +42658,14 @@ A set of codes advising a system or user which name in a set of names to select
     <concept>
      <code value="WAKE"></code>
      <display value="WAKE"></display>
-     <definition value="Description: Upon waking up from a regular period of sleep, in order to start regular activities (this would exclude waking up from a nap or temporarily waking up during a period of sleep)
+     <definition value="Description: Upon waking up from a regular period of sleep, in order to start regular activities (this would exclude waking up from a nap or temporarily waking up during a period of sleep)
 
         
-         Usage Notes: e.g.
+         Usage Notes: e.g.
 
-        Take pulse rate on waking in management of thyrotoxicosis.
+        Take pulse rate on waking in management of thyrotoxicosis.
 
-        Take BP on waking in management of hypertension
+        Take BP on waking in management of hypertension
 
         Take basal body temperature on waking in establishing date of ovulation"></definition>
     </concept>
@@ -42676,7 +42676,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/ActRelationshipSplit"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActRelationshipSplit"></id>
+    <id value="v3-ActRelationshipSplit"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42735,7 +42735,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/EntityNameUse"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityNameUse"></id>
+    <id value="v3-EntityNameUse"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42844,7 +42844,7 @@ A set of codes advising a system or user which name in a set of names to select
      <concept>
       <code value="PHON"></code>
       <display value="phonetic"></display>
-      <definition value="A name spelled phonetically.
+      <definition value="A name spelled phonetically.
 
         There are a variety of phonetic spelling algorithms. This code value does not distinguish between these.Discussion:"></definition>
      </concept>
@@ -42861,7 +42861,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/ActInvoiceElementModifier"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActInvoiceElementModifier"></id>
+    <id value="v3-ActInvoiceElementModifier"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -42920,7 +42920,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/DataOperation"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="DataOperation"></id>
+    <id value="v3-DataOperation"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43059,7 +43059,7 @@ A set of codes advising a system or user which name in a set of names to select
   <fullUrl value="http://hl7.org/fhir/v3/MessageWaitingPriority"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="MessageWaitingPriority"></id>
+    <id value="v3-MessageWaitingPriority"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43086,7 +43086,7 @@ A set of codes advising a system or user which name in a set of names to select
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" Indicates that the receiver has messages for the sender  OpenIssue:
+    <description value=" Indicates that the receiver has messages for the sender  OpenIssue:
 Description does not make sense relative to name of coding system.  Must be reviewed and improved."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-MessageWaitingPriority"></valueSet>
@@ -43114,7 +43114,7 @@ Description does not make sense relative to name of coding system.  Must be revi
   <fullUrl value="http://hl7.org/fhir/v3/LanguageAbilityProficiency"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="LanguageAbilityProficiency"></id>
+    <id value="v3-LanguageAbilityProficiency"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43141,8 +43141,8 @@ Description does not make sense relative to name of coding system.  Must be revi
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A value representing the level of proficiency in a language.  Example:
-Excellent, good, fair, poor.  OpenIssue:
+    <description value=" A value representing the level of proficiency in a language.  Example:
+Excellent, good, fair, poor.  OpenIssue:
 Description copied from Concept Domain of same name.  Must be verified."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-LanguageAbilityProficiency"></valueSet>
@@ -43175,7 +43175,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/ActRelationshipSubset"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActRelationshipSubset"></id>
+    <id value="v3-ActRelationshipSubset"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43216,7 +43216,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
     <concept>
      <code value="_ParticipationSubset"></code>
      <display value="ParticipationSubset"></display>
-     <definition value="Used to indicate that the participation is a filtered subset of the total participations of the same type owned by the Act. 
+     <definition value="Used to indicate that the participation is a filtered subset of the total participations of the same type owned by the Act. 
 
         Used when there is a need to limit the participations to the first, the last, the next or some other filtered subset."></definition>
      <property>
@@ -43296,7 +43296,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/DocumentCompletion"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="DocumentCompletion"></id>
+    <id value="v3-DocumentCompletion"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43380,7 +43380,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/QueryPriority"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="QueryPriority"></id>
+    <id value="v3-QueryPriority"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43429,7 +43429,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
   <fullUrl value="http://hl7.org/fhir/v3/EntityNamePartTypeR2"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityNamePartTypeR2"></id>
+    <id value="v3-EntityNamePartTypeR2"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43456,7 +43456,7 @@ Description copied from Concept Domain of same name.  Must be verified."></descr
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Indicates whether the name part is a given name, family name, prefix, suffix, etc."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-EntityNamePartTypeR2"></valueSet>
@@ -43480,7 +43480,7 @@ Indicates whether the name part is a given name, family name, prefix, suffix, et
     <concept>
      <code value="TITLE"></code>
      <display value="title"></display>
-     <definition value="Description:Part of the name that is acquired as a title due to academic, legal, employment or nobility status etc.
+     <definition value="Description:Part of the name that is acquired as a title due to academic, legal, employment or nobility status etc.
 
         
          Note:Title name parts include name parts that come after the name such as qualifications, even if they are not always considered to be titles."></definition>
@@ -43492,7 +43492,7 @@ Indicates whether the name part is a given name, family name, prefix, suffix, et
   <fullUrl value="http://hl7.org/fhir/v3/EncounterAdmissionSource"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EncounterAdmissionSource"></id>
+    <id value="v3-EncounterAdmissionSource"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43546,7 +43546,7 @@ Indicates whether the name part is a given name, family name, prefix, suffix, et
   <fullUrl value="http://hl7.org/fhir/v3/QueryRequestLimit"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="QueryRequestLimit"></id>
+    <id value="v3-QueryRequestLimit"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43573,7 +43573,7 @@ Indicates whether the name part is a given name, family name, prefix, suffix, et
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Definition:
+    <description value="  Definition:
 Defines the units associated with the magnitude of the maximum size limit of a query response that can be accepted by the requesting application."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-QueryRequestLimit"></valueSet>
@@ -43606,7 +43606,7 @@ Defines the units associated with the magnitude of the maximum size limit of a q
   <fullUrl value="http://hl7.org/fhir/v3/ActReason"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActReason"></id>
+    <id value="v3-ActReason"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -43636,7 +43636,7 @@ Defines the units associated with the magnitude of the maximum size limit of a q
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type &quot;has reason&quot; linking to another Act.  Examples:
+    <description value=" A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type &quot;has reason&quot; linking to another Act.  Examples:
 Example reasons that might qualify for being coded in this field might be: &quot;routine requirement&quot;, &quot;infectious disease reporting requirement&quot;, &quot;on patient request&quot;, &quot;required by law&quot;."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ActReason"></valueSet>
@@ -43694,7 +43694,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="_EligibilityActReasonCode"></code>
       <display value="EligibilityActReasonCode"></display>
-      <definition value="Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. 
+      <definition value="Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. 
 
         
          Examples:  A person is a claimant under an automobile insurance policy are client deceased &amp; adopted client has been given a new policy identifier.  A new employee is eligible for health insurance as an employment benefit.  A person meets a government program eligibility criteria for financial, age or health status."></definition>
@@ -43705,7 +43705,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <concept>
        <code value="_ActIneligibilityReason"></code>
        <display value="ActIneligibilityReason"></display>
-       <definition value="Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy.
+       <definition value="Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy.
 
         Examples are client deceased &amp; adopted client has been given a new policy identifier."></definition>
        <property>
@@ -43715,7 +43715,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="COVSUS"></code>
         <display value="coverage suspended"></display>
-        <definition value="When a client has no contact with the health system for an extended period, coverage is suspended.  Client will be reinstated to original start date upon proof of identification, residency etc.
+        <definition value="When a client has no contact with the health system for an extended period, coverage is suspended.  Client will be reinstated to original start date upon proof of identification, residency etc.
 
         Example: Coverage may be suspended during a strike situation, when employer benefits for employees are not covered (i.e. not in effect)."></definition>
        </concept>
@@ -43733,7 +43733,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <concept>
        <code value="_CoverageEligibilityReason"></code>
        <display value="CoverageEligibilityReason"></display>
-       <definition value="Definition: Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. 
+       <definition value="Definition: Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. 
 
         
          Examples:  A person is a claimant under an automobile insurance policy are client deceased &amp; adopted client has been given a new policy identifier.  A new employee is eligible for health insurance as an employment benefit.  A person meets a government program eligibility criteria for financial, age or health status."></definition>
@@ -43744,7 +43744,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="AGE"></code>
         <display value="age eligibility"></display>
-        <definition value="A person becomes eligible for a program based on age.
+        <definition value="A person becomes eligible for a program based on age.
 
         
          Example:  In the U.S., a person who is 65 years of age or older is eligible for Medicare."></definition>
@@ -43752,7 +43752,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="CRIME"></code>
         <display value="crime victim"></display>
-        <definition value="A person becomes eligible for insurance or a program because of crime related health condition or injury. 
+        <definition value="A person becomes eligible for insurance or a program because of crime related health condition or injury. 
 
         
          Example:  A person is a claimant under the U.S. Crime Victims Compensation program."></definition>
@@ -43770,7 +43770,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="FINAN"></code>
         <display value="financial eligibility"></display>
-        <definition value="A person becomes eligible for a program based on financial criteria.
+        <definition value="A person becomes eligible for a program based on financial criteria.
 
         
          Example:  A person whose family income is below a financial threshold for eligibility for Medicaid or SCHIP."></definition>
@@ -43778,7 +43778,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="HEALTH"></code>
         <display value="health status"></display>
-        <definition value="A person becomes eligible for a program because of a qualifying health condition or injury. 
+        <definition value="A person becomes eligible for a program because of a qualifying health condition or injury. 
 
         
          Examples:  A person is determined to have a qualifying health conditions include pregnancy, HIV/AIDs, tuberculosis, end stage renal disease, breast or cervical cancer, or other condition requiring specialized health services, hospice, institutional or community based care provided under a program"></definition>
@@ -43786,7 +43786,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="MULTI"></code>
         <display value="multiple criteria eligibility"></display>
-        <definition value="A person becomes eligible for a program based on more than one criterion.
+        <definition value="A person becomes eligible for a program based on more than one criterion.
 
         
          Examples:  In the U.S., a child whose familiy income meets Medicaid financial thresholds and whose age is less than 18 is eligible for the Early and Periodic Screening, Diagnostic, and Treatment program (EPSDT).  A person whose family income meets Medicaid financial thresholds and whose age is 65 years or older is eligible for Medicaid and Medicare, and are referred to as dual eligibles."></definition>
@@ -43794,7 +43794,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="PNC"></code>
         <display value="property and casualty condition"></display>
-        <definition value="A person becomes a claimant under a property and casualty insurance policy because of a related health condition or injury resulting from a circumstance covered under the terms of the policy. 
+        <definition value="A person becomes a claimant under a property and casualty insurance policy because of a related health condition or injury resulting from a circumstance covered under the terms of the policy. 
 
         
          Example:  A person is a claimant under a homeowners insurance policy because of an injury sustained on the policyholderaTMs premises."></definition>
@@ -43802,7 +43802,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="STATUTORY"></code>
         <display value="statutory eligibility"></display>
-        <definition value="A person becomes eligible for a program based on statutory criteria.
+        <definition value="A person becomes eligible for a program based on statutory criteria.
 
         
          Examples:  A person is a member of an indigenous group, a veteran of military service, or  in the U.S., a recipient of adoption assistance and foster care under Title IV-E of the Social Security."></definition>
@@ -43815,7 +43815,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="WORK"></code>
         <display value="work related"></display>
-        <definition value="A person becomes eligible for insurance or a program because of a work related health condition or injury. 
+        <definition value="A person becomes eligible for insurance or a program because of a work related health condition or injury. 
 
         
          Example:  A person is a claimant under the U.S. Black Lung Program."></definition>
@@ -43842,7 +43842,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <concept>
        <code value="_ActConsentInformationAccessOverrideReason"></code>
        <display value="ActConsentInformationAccessOverrideReason"></display>
-       <definition value="To perform one or more operations on information to which the patient has not consented as deemed necessary by authorized entities for providing care in the best interest of the patient; providing immediately needed health care for an emergent condition;  or for protecting public or third party safety.
+       <definition value="To perform one or more operations on information to which the patient has not consented as deemed necessary by authorized entities for providing care in the best interest of the patient; providing immediately needed health care for an emergent condition;  or for protecting public or third party safety.
 
         
          Usage Notes: Used to convey the reason that a provider or other entity may or has accessed personal healthcare information.  Typically, this involves overriding the subject's consent directives."></definition>
@@ -43853,7 +43853,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="OVRER"></code>
         <display value="emergency treatment override"></display>
-        <definition value="To perform one or more operations on information to which the patient has not consented by authorized entities for treating a condition which poses an immediate threat to the patient's health and which requires immediate medical intervention.
+        <definition value="To perform one or more operations on information to which the patient has not consented by authorized entities for treating a condition which poses an immediate threat to the patient's health and which requires immediate medical intervention.
 
         
          Usage Notes: The patient is unable to provide consent, but the provider determines they have an urgent healthcare related reason to access the record."></definition>
@@ -43861,7 +43861,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="OVRPJ"></code>
         <display value="professional judgment override"></display>
-        <definition value="To perform one or more operations on information to which the patient declined to consent for providing health care.
+        <definition value="To perform one or more operations on information to which the patient declined to consent for providing health care.
 
         
          Usage Notes: The patient, while able to give consent, has not.  However the provider believes it is in the patient's interest to access the record without patient consent."></definition>
@@ -43869,7 +43869,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="OVRPS"></code>
         <display value="public safety override"></display>
-        <definition value="To perform one or more operations on information to which the patient has not consented for public safety reasons.
+        <definition value="To perform one or more operations on information to which the patient has not consented for public safety reasons.
 
         
          Usage Notes: The patient, while able to give consent, has not.  However, the provider believes that access to masked patient information is justified because of concerns related to public safety."></definition>
@@ -43877,7 +43877,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
        <concept>
         <code value="OVRTPS"></code>
         <display value="third party safety override"></display>
-        <definition value="To perform one or more operations on information to which the patient has not consented for third party safety.  
+        <definition value="To perform one or more operations on information to which the patient has not consented for third party safety.  
 
         
          Usage Notes: The patient, while able to give consent, has not.  However, the provider believes that access to masked patient information is justified because of concerns related to the health and safety of one or more third parties."></definition>
@@ -43886,7 +43886,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <concept>
        <code value="PurposeOfUse"></code>
        <display value="purpose of use"></display>
-       <definition value="Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives.
+       <definition value="Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives.
 
         
          Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes."></definition>
@@ -43932,11 +43932,11 @@ Example reasons that might qualify for being coded in this field might be: &quot
         <concept>
          <code value="HDIRECT"></code>
          <display value="directory"></display>
-         <definition value="To perform one or more operation operations on information used to manage a patient directory.
+         <definition value="To perform one or more operation operations on information used to manage a patient directory.
 
         
          Examples: 
-        
+        
 
         
          facility
@@ -44249,7 +44249,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
     <concept>
      <code value="_ActNoImmunizationReason"></code>
      <display value="ActNoImmunizationReason"></display>
-     <definition value="A coded description of the reason for why a patient did not receive a scheduled immunization.
+     <definition value="A coded description of the reason for why a patient did not receive a scheduled immunization.
 
         (important for public health strategy"></definition>
      <property>
@@ -44289,7 +44289,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="VACEFF"></code>
       <display value="vaccine efficacy concerns"></display>
-      <definition value="Definition:The intended vaccine has expired or is otherwise believed to no longer be effective.
+      <definition value="Definition:The intended vaccine has expired or is otherwise believed to no longer be effective.
 
         
          Example:Due to temperature exposure."></definition>
@@ -44303,7 +44303,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
     <concept>
      <code value="_ActSupplyFulfillmentRefusalReason"></code>
      <display value="ActSupplyFulfillmentRefusalReason"></display>
-     <definition value="Indicates why a fulfiller refused to fulfill a supply order, and considered it important to notify other providers of their decision.  E.g. &quot;Suspect fraud&quot;, &quot;Possible abuse&quot;, &quot;Contraindicated&quot;.
+     <definition value="Indicates why a fulfiller refused to fulfill a supply order, and considered it important to notify other providers of their decision.  E.g. &quot;Suspect fraud&quot;, &quot;Possible abuse&quot;, &quot;Contraindicated&quot;.
 
         (used when capturing 'refusal to fill' annotations)"></definition>
      <property>
@@ -44313,7 +44313,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="FRR01"></code>
       <display value="order stopped"></display>
-      <definition value="Definition:The order has been stopped by the prescriber but this fact has not necessarily captured electronically.
+      <definition value="Definition:The order has been stopped by the prescriber but this fact has not necessarily captured electronically.
 
         
          Example:A verbal stop, a fax, etc."></definition>
@@ -44326,7 +44326,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="FRR03"></code>
       <display value="incomplete data"></display>
-      <definition value="Definition:Data needed to safely act on the order which was expected to become available independent of the order is not yet available
+      <definition value="Definition:Data needed to safely act on the order which was expected to become available independent of the order is not yet available
 
         
          Example:Lab results, diagnostic imaging, etc."></definition>
@@ -44344,7 +44344,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="FRR06"></code>
       <display value="unable to provide care"></display>
-      <definition value="Definition:Fulfiller not able to provide appropriate care associated with fulfilling the order.
+      <definition value="Definition:Fulfiller not able to provide appropriate care associated with fulfilling the order.
 
         
          Example:Therapy requires ongoing monitoring by fulfiller and fulfiller will be ending practice, leaving town, unable to schedule necessary time, etc."></definition>
@@ -44382,7 +44382,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
     <concept>
      <code value="_ClinicalResearchObservationReason"></code>
      <display value="ClinicalResearchObservationReason"></display>
-     <definition value="Definition:SSpecifies the reason that a test was performed or observation collected in a clinical research study.
+     <definition value="Definition:SSpecifies the reason that a test was performed or observation collected in a clinical research study.
 
         
          Note:This set of codes are not strictly reasons, but are used in the currently Normative standard.  Future revisions of the specification will model these as ActRelationships and thes codes may subsequently be retired.  Thus, these codes should not be used for new specifications."></definition>
@@ -44487,7 +44487,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="ALTD"></code>
       <display value="altered decision"></display>
-      <definition value="Description:The decision on which the recorded information was based was changed before the decision had an effect.
+      <definition value="Description:The decision on which the recorded information was based was changed before the decision had an effect.
 
         
          Example:Aborted prescription before patient left office, released prescription before suspend took effect."></definition>
@@ -44638,7 +44638,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <concept>
        <code value="UNABLE"></code>
        <display value="unable to use"></display>
-       <definition value="Description:&lt;The patient is not (or is no longer) able to use the medication in a manner prescribed.
+       <definition value="Description:&lt;The patient is not (or is no longer) able to use the medication in a manner prescribed.
 
         
          Example:CanaTMt swallow."></definition>
@@ -44743,7 +44743,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <concept>
        <code value="PHARM"></code>
        <display value="pharmacy transfer"></display>
-       <definition value="Definition:The bulk supply is being transferred to another dispensing facility to.
+       <definition value="Definition:The bulk supply is being transferred to another dispensing facility to.
 
         
          Example:Alleviate a temporary shortage."></definition>
@@ -44751,7 +44751,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <concept>
        <code value="PROG"></code>
        <display value="program use"></display>
-       <definition value="Definition:The bulk supply is intended for dispensing according to a specific program.
+       <definition value="Definition:The bulk supply is intended for dispensing according to a specific program.
 
         
          Example:Mass immunization."></definition>
@@ -44927,7 +44927,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="VALIDATION"></code>
       <display value="validation review"></display>
-      <definition value="Description:To validate the patient's record.
+      <definition value="Description:To validate the patient's record.
 
         
          Example:Merging or unmerging records."></definition>
@@ -45145,9 +45145,9 @@ Example reasons that might qualify for being coded in this field might be: &quot
      <concept>
       <code value="_ActBillableClinicalServiceReason"></code>
       <display value="ActBillableClinicalServiceReason"></display>
-      <definition value="Reason for Clinical Service being performed.
+      <definition value="Reason for Clinical Service being performed.
 
-        This domain excludes reasons specified by diagnosed conditions.
+        This domain excludes reasons specified by diagnosed conditions.
 
         Examples of values from this domain include duplicate therapy and fraudulent prescription."></definition>
       <property>
@@ -45297,7 +45297,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
   <fullUrl value="http://hl7.org/fhir/v3/CompressionAlgorithm"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="CompressionAlgorithm"></id>
+    <id value="v3-CompressionAlgorithm"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -45366,7 +45366,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
   <fullUrl value="http://hl7.org/fhir/v3/hl7V3Conformance"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="hl7V3Conformance"></id>
+    <id value="v3-hl7V3Conformance"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -45393,7 +45393,7 @@ Example reasons that might qualify for being coded in this field might be: &quot
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  Description:
+    <description value="  Description:
 Identifies allowed codes for HL7aTMs v3 conformance property."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-hl7V3Conformance"></valueSet>
@@ -45436,7 +45436,7 @@ Identifies allowed codes for HL7aTMs v3 conformance property."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ManagedParticipationStatus"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ManagedParticipationStatus"></id>
+    <id value="v3-ManagedParticipationStatus"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -45505,7 +45505,7 @@ Identifies allowed codes for HL7aTMs v3 conformance property."></description>
   <fullUrl value="http://hl7.org/fhir/v3/EntityCode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EntityCode"></id>
+    <id value="v3-EntityCode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -45532,7 +45532,7 @@ Identifies allowed codes for HL7aTMs v3 conformance property."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing description."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-EntityCode"></valueSet>
@@ -46298,7 +46298,7 @@ Missing description."></description>
      <concept>
       <code value="NAT"></code>
       <display value="NationEntityType"></display>
-      <definition value="Codes identifying nation states.  Allows for finer grained specification of Entity with classcode &lt;= NAT
+      <definition value="Codes identifying nation states.  Allows for finer grained specification of Entity with classcode &lt;= NAT
 
         
          Example:ISO3166 country codes."></definition>
@@ -46346,9 +46346,9 @@ Missing description."></description>
     <concept>
      <code value="_ResourceGroupEntityType"></code>
      <display value="ResourceGroupEntityType"></display>
-     <definition value="Codes to characterize a Resource Group using categories that typify its membership and/or function
+     <definition value="Codes to characterize a Resource Group using categories that typify its membership and/or function
 
-        .
+        .
 
         
          Example: PractitionerGroup"></definition>
@@ -46369,7 +46369,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/EmployeeJobClass"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="EmployeeJobClass"></id>
+    <id value="v3-EmployeeJobClass"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -46418,7 +46418,7 @@ Missing description."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ActUncertainty"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActUncertainty"></id>
+    <id value="v3-ActUncertainty"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -46445,7 +46445,7 @@ Missing description."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value="  OpenIssue:
+    <description value="  OpenIssue:
 Missing Description"></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ActUncertainty"></valueSet>
@@ -46468,7 +46468,7 @@ Missing Description"></description>
   <fullUrl value="http://hl7.org/fhir/v3/SubstitutionCondition"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="SubstitutionCondition"></id>
+    <id value="v3-SubstitutionCondition"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -46542,7 +46542,7 @@ Missing Description"></description>
   <fullUrl value="http://hl7.org/fhir/v3/TableCellScope"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TableCellScope"></id>
+    <id value="v3-TableCellScope"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -46601,7 +46601,7 @@ Missing Description"></description>
   <fullUrl value="http://hl7.org/fhir/v3/ActUSPrivacyLaw"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActUSPrivacyLaw"></id>
+    <id value="v3-ActUSPrivacyLaw"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -46628,7 +46628,7 @@ Missing Description"></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A jurisdictional mandate in the US relating to privacy.   Deprecation Comment:
+    <description value=" A jurisdictional mandate in the US relating to privacy.   Deprecation Comment:
 Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ActUSPrivacyLaw"></valueSet>
@@ -46643,7 +46643,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
     <concept>
      <code value="_ActUSPrivacyLaw"></code>
      <display value="ActUSPrivacyLaw"></display>
-     <definition value="Definition: A jurisdictional mandate in the U.S. relating to privacy.
+     <definition value="Definition: A jurisdictional mandate in the U.S. relating to privacy.
 
         
          Usage Note: ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies.  May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1."></definition>
@@ -46654,10 +46654,10 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
      <concept>
       <code value="42CFRPart2"></code>
       <display value="42 CFR Part2"></display>
-      <definition value="42 CFR Part 2 stipulates the right of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program.
+      <definition value="42 CFR Part 2 stipulates the right of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program.
 
         
-         Definition: Non-disclosure of health information relating to health care paid for by a federally assisted substance abuse program without patient consent.
+         Definition: Non-disclosure of health information relating to health care paid for by a federally assisted substance abuse program without patient consent.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -46669,10 +46669,10 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
      <concept>
       <code value="CommonRule"></code>
       <display value="Common Rule"></display>
-      <definition value="U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46) that has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements.
+      <definition value="U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46) that has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements.
 
         
-         Definition: U.S. federal laws governing research-related privacy policies.
+         Definition: U.S. federal laws governing research-related privacy policies.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies."></definition>
@@ -46684,10 +46684,10 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
      <concept>
       <code value="HIPAANOPP"></code>
       <display value="HIPAA notice of privacy practices"></display>
-      <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Subpart E) permits access, use and disclosure of certain personal health information (PHI as defined under the law) for purposes of Treatment, Payment, and Operations, and requires that the provider ask that patients acknowledge the Provider's Notice of Privacy Practices as permitted conduct under the law.
+      <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Subpart E) permits access, use and disclosure of certain personal health information (PHI as defined under the law) for purposes of Treatment, Payment, and Operations, and requires that the provider ask that patients acknowledge the Provider's Notice of Privacy Practices as permitted conduct under the law.
 
         
-         Definition: Notification of HIPAA Privacy Practices.
+         Definition: Notification of HIPAA Privacy Practices.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies."></definition>
@@ -46699,10 +46699,10 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
      <concept>
       <code value="HIPAAPsyNotes"></code>
       <display value="HIPAA psychotherapy notes"></display>
-      <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Section 164.508) requires authorization for certain uses and disclosure of psychotherapy notes.
+      <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Section 164.508) requires authorization for certain uses and disclosure of psychotherapy notes.
 
         
-         Definition: Authorization that must be obtained for disclosure of psychotherapy notes.
+         Definition: Authorization that must be obtained for disclosure of psychotherapy notes.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -46714,10 +46714,10 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
      <concept>
       <code value="HIPAASelfPay"></code>
       <display value="HIPAA self-pay"></display>
-      <definition value="Section 13405(a) of the Health Information Technology for Economic and Clinical Health Act (HITECH) stipulates the right of an individual to have disclosures regarding certain health care items or services for which the individual pays out of pocket in full restricted from a health plan.
+      <definition value="Section 13405(a) of the Health Information Technology for Economic and Clinical Health Act (HITECH) stipulates the right of an individual to have disclosures regarding certain health care items or services for which the individual pays out of pocket in full restricted from a health plan.
 
         
-         Definition: Non-disclosure of health information to a health plan relating to health care items or services for which an individual pays out of pocket in full.
+         Definition: Non-disclosure of health information to a health plan relating to health care items or services for which an individual pays out of pocket in full.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -46729,13 +46729,13 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
      <concept>
       <code value="Title38Section7332"></code>
       <display value="Title 38 Section 7332"></display>
-      <definition value="Title 38 Part 1-protected information may only be disclosed to a third party with the special written consent of the patient except where expressly authorized by 38 USC 7332. VA may disclose this information for specific purposes to: VA employees on a need to know basis - more restrictive than Privacy Act need to know; contractors who need the information in order to perform or fulfill the duties of the contract; and researchers who provide assurances that the information will not be identified in any report.  This information may also be disclosed without consent where patient lacks decision-making capacity; in a medical emergency for the purpose of treating a condition which poses an immediate threat to the health of any individual and which requires immediate medical intervention; for eye, tissue, or organ donation purposes; and disclosure of HIV information for public health purposes.
+      <definition value="Title 38 Part 1-protected information may only be disclosed to a third party with the special written consent of the patient except where expressly authorized by 38 USC 7332. VA may disclose this information for specific purposes to: VA employees on a need to know basis - more restrictive than Privacy Act need to know; contractors who need the information in order to perform or fulfill the duties of the contract; and researchers who provide assurances that the information will not be identified in any report.  This information may also be disclosed without consent where patient lacks decision-making capacity; in a medical emergency for the purpose of treating a condition which poses an immediate threat to the health of any individual and which requires immediate medical intervention; for eye, tissue, or organ donation purposes; and disclosure of HIV information for public health purposes.
 
         
-         Definition: Title 38 Part 1 - §1.462 Confidentiality restrictions.
+         Definition: Title 38 Part 1 - §1.462 Confidentiality restrictions.
 
         
-(a) General. The patient records to which §§1.460 through 1.499 of this part apply may be disclosed or used only as permitted by these regulations and may not otherwise be disclosed or used in any civil, criminal, administrative, or legislative proceedings conducted by any Federal, State, or local authority. Any disclosure made under these regulations must be limited to that information which is necessary to carry out the purpose of the disclosure. SUBCHAPTER III--PROTECTION OF PATIENT RIGHTS Sec. 7332. Confidentiality of certain medical records (a)(1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b).
+(a) General. The patient records to which §§1.460 through 1.499 of this part apply may be disclosed or used only as permitted by these regulations and may not otherwise be disclosed or used in any civil, criminal, administrative, or legislative proceedings conducted by any Federal, State, or local authority. Any disclosure made under these regulations must be limited to that information which is necessary to carry out the purpose of the disclosure. SUBCHAPTER III--PROTECTION OF PATIENT RIGHTS Sec. 7332. Confidentiality of certain medical records (a)(1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b).
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -46752,7 +46752,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
   <fullUrl value="http://hl7.org/fhir/v3/ActCode"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="ActCode"></id>
+    <id value="v3-ActCode"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -46782,7 +46782,7 @@ Content moved to ActCode under _ActPrivacyLaw; use that instead."></description>
       <value value="http://hl7.org"></value>
      </telecom>
     </contact>
-    <description value=" A code specifying the particular kind of Act that the Act-instance represents within its class.  Constraints:
+    <description value=" A code specifying the particular kind of Act that the Act-instance represents within its class.  Constraints:
 The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems.  The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code &quot;potassium&quot; together with and Act.classCode for &quot;laboratory observation&quot; to somehow mean &quot;potassium laboratory observation&quot; and then use the same Act.code for &quot;potassium&quot; together with Act.classCode for &quot;medication&quot; to mean &quot;substitution of potassium&quot;. This mutually modifying use of Act.code and Act.classCode is not permitted."></description>
     <caseSensitive value="true"></caseSensitive>
     <valueSet value="http://hl7.org/fhir/ValueSet/v3-ActCode"></valueSet>
@@ -46920,19 +46920,19 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
      <concept>
       <code value="AA"></code>
       <display value="adjudicated with adjustments"></display>
-      <definition value="The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges).  
+      <definition value="The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges).  
 
-        Also includes the concept 'Adjudicate as zero' and items not covered under a particular Policy.  
+        Also includes the concept 'Adjudicate as zero' and items not covered under a particular Policy.  
 
-        Invoice element can be reversed (nullified).  
+        Invoice element can be reversed (nullified).  
 
         Recommend that the invoice element is saved for DUR (Drug Utilization Reporting)."></definition>
       <concept>
        <code value="ANF"></code>
        <display value="adjudicated with adjustments and no financial impact"></display>
-       <definition value="The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges) without changing the amount.  
+       <definition value="The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges) without changing the amount.  
 
-        Invoice element can be reversed (nullified).  
+        Invoice element can be reversed (nullified).  
 
         Recommend that the invoice element is saved for DUR (Drug Utilization Reporting)."></definition>
       </concept>
@@ -46940,28 +46940,28 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
      <concept>
       <code value="AR"></code>
       <display value="adjudicated as refused"></display>
-      <definition value="The invoice element has passed through the adjudication process but payment is refused due to one or more reasons.
+      <definition value="The invoice element has passed through the adjudication process but payment is refused due to one or more reasons.
 
-        Includes items such as patient not covered, or invoice element is not constructed according to payer rules (e.g. 'invoice submitted too late').
+        Includes items such as patient not covered, or invoice element is not constructed according to payer rules (e.g. 'invoice submitted too late').
 
-        If one invoice element line item in the invoice element structure is rejected, the remaining line items may not be adjudicated and the complete group is treated as rejected.
+        If one invoice element line item in the invoice element structure is rejected, the remaining line items may not be adjudicated and the complete group is treated as rejected.
 
-        A refused invoice element can be forwarded to the next payer (for Coordination of Benefits) or modified and resubmitted to refusing payer.
+        A refused invoice element can be forwarded to the next payer (for Coordination of Benefits) or modified and resubmitted to refusing payer.
 
-        Invoice element cannot be reversed (nullified) as there is nothing to reverse.  
+        Invoice element cannot be reversed (nullified) as there is nothing to reverse.  
 
         Recommend that the invoice element is not saved for DUR (Drug Utilization Reporting)."></definition>
      </concept>
      <concept>
       <code value="AS"></code>
       <display value="adjudicated as submitted"></display>
-      <definition value="The invoice element was/will be paid exactly as submitted, without financial adjustment(s).
+      <definition value="The invoice element was/will be paid exactly as submitted, without financial adjustment(s).
 
-        If the dollar amount stays the same, but the billing codes have been amended or financial adjustments have been applied through the adjudication process, the invoice element is treated as &quot;Adjudicated with Adjustment&quot;.
+        If the dollar amount stays the same, but the billing codes have been amended or financial adjustments have been applied through the adjudication process, the invoice element is treated as &quot;Adjudicated with Adjustment&quot;.
 
-        If information items are included in the adjudication results that do not affect the monetary amounts paid, then this is still Adjudicated as Submitted (e.g. 'reached Plan Maximum on this Claim').  
+        If information items are included in the adjudication results that do not affect the monetary amounts paid, then this is still Adjudicated as Submitted (e.g. 'reached Plan Maximum on this Claim').  
 
-        Invoice element can be reversed (nullified).  
+        Invoice element can be reversed (nullified).  
 
         Recommend that the invoice element is saved for DUR (Drug Utilization Reporting)."></definition>
      </concept>
@@ -47015,7 +47015,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
      <concept>
       <code value="BLK"></code>
       <display value="block funding"></display>
-      <definition value="A billing arrangement where a Provider charges a lump sum to provide a prescribed group (volume) of services to a single patient which occur over a period of time.  Services included in the block may vary.  
+      <definition value="A billing arrangement where a Provider charges a lump sum to provide a prescribed group (volume) of services to a single patient which occur over a period of time.  Services included in the block may vary.  
 
         This billing arrangement is also known as Program of Care for some specific Payors and Program Fees for other Payors."></definition>
      </concept>
@@ -47047,7 +47047,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
      <concept>
       <code value="FFS"></code>
       <display value="fee for service"></display>
-      <definition value="A billing arrangement where a Provider charges a separate fee for each intervention/procedure/event or product.
+      <definition value="A billing arrangement where a Provider charges a separate fee for each intervention/procedure/event or product.
 
         Fee for Service is used when an individual intervention/procedure/event is used for billing purposes.  In other words, fees are associated with the  intervention/procedure/event.  For example, a specific CCI (Canadian Classification of Interventions) code has an associated fee and is used for billing purposes."></definition>
       <property>
@@ -47101,7 +47101,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
      <concept>
       <code value="_ActCredentialedCareCode"></code>
       <display value="act credentialed care"></display>
-      <definition value="Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by a credentialing agency, i.e. government or non-government agency. Failure in executing this Act may result in loss of credential to the person or organization who participates as performer of the Act. Excludes employment agreements.
+      <definition value="Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by a credentialing agency, i.e. government or non-government agency. Failure in executing this Act may result in loss of credential to the person or organization who participates as performer of the Act. Excludes employment agreements.
 
         
          Example:Hospital license; physician license; clinic accreditation."></definition>
@@ -47559,7 +47559,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="PRENC"></code>
        <display value="pre-admission"></display>
-       <definition value="A patient encounter where patient is scheduled or planned to receive service delivery in the future, and the patient is given a pre-admission account number. When the patient comes back for subsequent service, the pre-admission encounter is selected and is encapsulated into the service registration, and a new account number is generated.
+       <definition value="A patient encounter where patient is scheduled or planned to receive service delivery in the future, and the patient is given a pre-admission account number. When the patient comes back for subsequent service, the pre-admission encounter is selected and is encapsulated into the service registration, and a new account number is generated.
 
         
          Usage Note: This is intended to be used in advance of encounter types such as ambulatory, inpatient encounter, virtual, etc."></definition>
@@ -47734,7 +47734,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="INFAO"></code>
        <display value="access only"></display>
-       <definition value="Definition: Consent to access or &quot;read&quot; only, which entails that the information is not to be copied, screen printed, saved, emailed, stored, re-disclosed or altered in any way.  This level ensures that data which is masked or to which access is restricted will not be.
+       <definition value="Definition: Consent to access or &quot;read&quot; only, which entails that the information is not to be copied, screen printed, saved, emailed, stored, re-disclosed or altered in any way.  This level ensures that data which is masked or to which access is restricted will not be.
 
         
          Example: Opened and then emailed or screen printed for use outside of the consent directive purpose."></definition>
@@ -47762,7 +47762,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="RSREID"></code>
        <display value="re-identifiable information access"></display>
-       <definition value="Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent.
+       <definition value="Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent.
 
         
          Example:: Where there is a need to inform the subject of potential health issues."></definition>
@@ -47816,7 +47816,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
     <concept>
      <code value="_ActControlVariable"></code>
      <display value="ActControlVariable"></display>
-     <definition value="An observation form that determines parameters or attributes of an Act. Examples are the settings of a ventilator machine as parameters of a ventilator treatment act; the controls on dillution factors of a chemical analyzer as a parameter of a laboratory observation act; the settings of a physiologic measurement assembly (e.g., time skew) or the position of the body while measuring blood pressure.
+     <definition value="An observation form that determines parameters or attributes of an Act. Examples are the settings of a ventilator machine as parameters of a ventilator treatment act; the controls on dillution factors of a chemical analyzer as a parameter of a laboratory observation act; the settings of a physiologic measurement assembly (e.g., time skew) or the position of the body while measuring blood pressure.
 
         Control variables are forms of observations because just as with clinical observations, the Observation.code determines the parameter and the Observation.value assigns the value. While control variables sometimes can be observed (by noting the control settings or an actually measured feedback loop) they are not primary observations, in the sense that a control variable without a primary act is of no use (e.g., it makes no sense to record a blood pressure position without recording a blood pressure, whereas it does make sense to record a systolic blood pressure without a diastolic blood pressure)."></definition>
      <property>
@@ -48023,14 +48023,14 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="DISEASEPRG"></code>
         <display value="public health program"></display>
-        <definition value="Definition: A public or government health program that administers and funds coverage for health and social services to assist program eligible who meet financial and health status criteria related to a particular disease.
+        <definition value="Definition: A public or government health program that administers and funds coverage for health and social services to assist program eligible who meet financial and health status criteria related to a particular disease.
 
         
          Example: Reproductive health, sexually transmitted disease, and end renal disease programs."></definition>
         <concept>
          <code value="CANPRG"></code>
          <display value="women's cancer detection program"></display>
-         <definition value="Definition: A program that provides low-income, uninsured, and underserved women access to timely, high-quality screening and diagnostic services, to detect breast and cervical cancer at the earliest stages.
+         <definition value="Definition: A program that provides low-income, uninsured, and underserved women access to timely, high-quality screening and diagnostic services, to detect breast and cervical cancer at the earliest stages.
 
         
          Example: To improve women's access to screening for breast and cervical cancers, Congress passed the Breast and Cervical Cancer Mortality Prevention Act of 1990, which guided CDC in creating the National Breast and Cervical Cancer Early Detection Program (NBCCEDP), which  provides access to critical breast and cervical cancer screening services for underserved women in the United States.  An estimated 7 to 10% of U.S. women of screening age are eligible to receive NBCCEDP services. Federal guidelines establish an eligibility baseline to direct services to uninsured and underinsured women at or below 250% of federal poverty level; ages 18 to 64 for cervical screening; ages 40 to 64 for breast screening."></definition>
@@ -48038,14 +48038,14 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="ENDRENAL"></code>
          <display value="end renal program"></display>
-         <definition value="Definition: A public or government program that administers publicly funded coverage of kidney dialysis and kidney transplant services.
+         <definition value="Definition: A public or government program that administers publicly funded coverage of kidney dialysis and kidney transplant services.
 
         Example: In the U.S., the Medicare End-stage Renal Disease program (ESRD), the National Kidney Foundation (NKF) American Kidney Fund (AKF) The Organ Transplant Fund."></definition>
         </concept>
         <concept>
          <code value="HIVAIDS"></code>
          <display value="HIV-AIDS program"></display>
-         <definition value="Definition: Government administered and funded HIV-AIDS program for beneficiaries meeting financial and health status criteria.  Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process.  Payer responsibilities for administering the program may be delegated to contractors.
+         <definition value="Definition: Government administered and funded HIV-AIDS program for beneficiaries meeting financial and health status criteria.  Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process.  Payer responsibilities for administering the program may be delegated to contractors.
 
         
          Example: In the U.S., the Ryan White program, which is administered by the Health Resources and Services Administration."></definition>
@@ -48059,7 +48059,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="MENTPRG"></code>
         <display value="mental health program"></display>
-        <definition value="Definition: Government administered and funded mental health program for beneficiaries meeting financial and mental health status criteria.  Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process.  Payer responsibilities for administering the program may be delegated to contractors.
+        <definition value="Definition: Government administered and funded mental health program for beneficiaries meeting financial and mental health status criteria.  Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process.  Payer responsibilities for administering the program may be delegated to contractors.
 
         
          Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA)."></definition>
@@ -48067,7 +48067,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="SAFNET"></code>
         <display value="safety net clinic program"></display>
-        <definition value="Definition: Government administered and funded program to support provision of care to underserved populations through safety net clinics.
+        <definition value="Definition: Government administered and funded program to support provision of care to underserved populations through safety net clinics.
 
         
          Example: In the U.S., safety net providers such as federally qualified health centers (FQHC) receive funding under PHSA Section 330 grants administered by the Health Resources and Services Administration."></definition>
@@ -48075,7 +48075,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="SUBPRG"></code>
         <display value="substance use program"></display>
-        <definition value="Definition: Government administered and funded substance use program for beneficiaries meeting financial, substance use behavior, and health status criteria.  Beneficiaries may be required to enroll as a result of legal proceedings.  Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process.  Payer responsibilities for administering the program may be delegated to contractors.
+        <definition value="Definition: Government administered and funded substance use program for beneficiaries meeting financial, substance use behavior, and health status criteria.  Beneficiaries may be required to enroll as a result of legal proceedings.  Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process.  Payer responsibilities for administering the program may be delegated to contractors.
 
         
          Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA)."></definition>
@@ -48087,7 +48087,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="SUBSIDMC"></code>
          <display value="subsidized managed care program"></display>
-         <definition value="Definition: A government health program that provides coverage through managed care contracts for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. 
+         <definition value="Definition: A government health program that provides coverage through managed care contracts for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. 
 
         
          Discussion: The structure and business processes for underwriting and administering a subsidized managed care program is further specified by the Underwriter and Payer Role.class and Role.code."></definition>
@@ -48095,10 +48095,10 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="SUBSUPP"></code>
          <display value="subsidized supplemental health program"></display>
-         <definition value="Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria for a supplemental health policy or program such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds.
+         <definition value="Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria for a supplemental health policy or program such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds.
 
         
-         Example:  Supplemental health coverage program may cover the cost of a health program or policy financial participations, such as the copays and the premiums, and may provide coverage for services in addition to those covered under the supplemented health program or policy.  In the U.S., Medicaid programs may pay the premium for a covered party who is also covered under the  Medicare program or a private health policy.
+         Example:  Supplemental health coverage program may cover the cost of a health program or policy financial participations, such as the copays and the premiums, and may provide coverage for services in addition to those covered under the supplemented health program or policy.  In the U.S., Medicaid programs may pay the premium for a covered party who is also covered under the  Medicare program or a private health policy.
 
         
          Discussion: The structure and business processes for underwriting and administering a subsidized supplemental retiree health program is further specified by the Underwriter and Payer Role.class and Role.code."></definition>
@@ -48117,7 +48117,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       </modifierExtension>
       <code value="_ActInsuranceTypeCode"></code>
       <display value="ActInsuranceTypeCode"></display>
-      <definition value="Definition: Set of codes indicating the type of insurance policy.  Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an individual or an organization enters into a contract with an underwriter which stipulates that, in exchange for payment of a sum of money (a premium), one or more covered parties (insureds) is guaranteed compensation for losses resulting from certain perils under specified conditions.  The underwriter analyzes the risk of loss, makes a decision as to whether the risk is insurable, and prices the premium accordingly.  A policy provides benefits that indemnify or cover the cost of a loss incurred by a covered party, and may include coverage for services required to remediate a loss.  An insurance policy contains pertinent facts about the policy holder, the insurance coverage, the covered parties, and the insurer.  A policy may include exemptions and provisions specifying the extent to which the indemnification clause cannot be enforced for intentional tortious conduct of a covered party, e.g., whether the covered parties are jointly or severably insured.
+      <definition value="Definition: Set of codes indicating the type of insurance policy.  Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an individual or an organization enters into a contract with an underwriter which stipulates that, in exchange for payment of a sum of money (a premium), one or more covered parties (insureds) is guaranteed compensation for losses resulting from certain perils under specified conditions.  The underwriter analyzes the risk of loss, makes a decision as to whether the risk is insurable, and prices the premium accordingly.  A policy provides benefits that indemnify or cover the cost of a loss incurred by a covered party, and may include coverage for services required to remediate a loss.  An insurance policy contains pertinent facts about the policy holder, the insurance coverage, the covered parties, and the insurer.  A policy may include exemptions and provisions specifying the extent to which the indemnification clause cannot be enforced for intentional tortious conduct of a covered party, e.g., whether the covered parties are jointly or severably insured.
 
         
          Discussion: In contrast to programs, an insurance policy has one or more policy holders, who own the policy.  The policy holder may be the covered party, a relative of the covered party, a partnership, or a corporation, e.g., an employer.  A subscriber of a self-insured health insurance policy is a policy holder.  A subscriber of an employer sponsored health insurance policy is holds a certificate of coverage, but is not a policy holder; the policy holder is the employer.  See CoveredRoleType."></definition>
@@ -48160,7 +48160,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="HIP"></code>
         <display value="health insurance plan policy"></display>
-        <definition value="Definition: A health insurance policy that covers healthcare benefits by protecting covered parties from medical expenses arising from health conditions, sickness, or accidental injury as well as preventive care. Health insurance policies explicitly exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy.
+        <definition value="Definition: A health insurance policy that covers healthcare benefits by protecting covered parties from medical expenses arising from health conditions, sickness, or accidental injury as well as preventive care. Health insurance policies explicitly exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy.
 
         
          Discussion: Health insurance policies are offered by health insurance plans that typically reimburse providers for covered services on a fee-for-service basis, that is, a fee that is the allowable amount that a provider may charge.  This is in contrast to managed care plans, which typically prepay providers a per-member/per-month amount or capitation as reimbursement for all covered services rendered.  Health insurance plans include indemnity and healthcare services plans."></definition>
@@ -48168,19 +48168,19 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="LTC"></code>
         <display value="long term care policy"></display>
-        <definition value="Definition: An insurance policy that covers benefits for long-term care services people need when they no longer can care for themselves. This may be due to an accident, disability, prolonged illness or the simple process of aging. Long-term care services assist with activities of daily living including:
+        <definition value="Definition: An insurance policy that covers benefits for long-term care services people need when they no longer can care for themselves. This may be due to an accident, disability, prolonged illness or the simple process of aging. Long-term care services assist with activities of daily living including:
 
         
          
-          Help at home with day-to-day activities, such as cooking, cleaning, bathing and dressing
+          Help at home with day-to-day activities, such as cooking, cleaning, bathing and dressing
 
          
          
-          Care in the community, such as in an adult day care facility
+          Care in the community, such as in an adult day care facility
 
          
          
-          Supervised care provided in an assisted living facility
+          Supervised care provided in an assisted living facility
 
          
          
@@ -48189,9 +48189,9 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="MCPOL"></code>
         <display value="managed care policy"></display>
-        <definition value="Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment.  Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program.  Employees may be required to pay premiums toward the cost of coverage as well.
+        <definition value="Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment.  Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program.  Employees may be required to pay premiums toward the cost of coverage as well.
 
-        Managed care policies specifically exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy.
+        Managed care policies specifically exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy.
 
         
          Discussion: Managed care policies are offered by managed care plans that contract with selected providers or health care organizations to provide comprehensive health care at a discount to covered parties and coordinate the financing and delivery of health care. Managed care uses medical protocols and procedures agreed on by the medical profession to be cost effective, also known as medical practice guidelines. Providers are typically reimbursed for covered services by a capitated amount on a per member per month basis that may reflect difference in the health status and level of services anticipated to be needed by the member."></definition>
@@ -48224,7 +48224,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="VISPOL"></code>
         <display value="vision care policy"></display>
-        <definition value="Definition: Set of codes for a policy that provides coverage for health care expenses arising from vision services.
+        <definition value="Definition: Set of codes for a policy that provides coverage for health care expenses arising from vision services.
 
         A health insurance policy that covers benefits for vision care services, prescriptions, and products."></definition>
        </concept>
@@ -48242,7 +48242,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="FLEXP"></code>
        <display value="flexible benefit plan policy"></display>
-       <definition value="Definition:  An insurance policy that covers qualified benefits under a Flexible Benefit plan such as group medical insurance, long and short term disability income insurance, group term life insurance for employees only up to $50,000 face amount, specified disease coverage such as a cancer policy, dental and/or vision insurance, hospital indemnity insurance, accidental death and dismemberment insurance, a medical expense reimbursement plan and a dependent care reimbursement plan.
+       <definition value="Definition:  An insurance policy that covers qualified benefits under a Flexible Benefit plan such as group medical insurance, long and short term disability income insurance, group term life insurance for employees only up to $50,000 face amount, specified disease coverage such as a cancer policy, dental and/or vision insurance, hospital indemnity insurance, accidental death and dismemberment insurance, a medical expense reimbursement plan and a dependent care reimbursement plan.
 
         
          Discussion: See UnderwriterRoleTypeCode flexible benefit plan which is defined as a benefit plan that allows employees to choose from several life, health, disability, dental, and other insurance plans according to their individual needs. Also known as cafeteria plans.  Authorized under Section 125 of the Revenue Act of 1978."></definition>
@@ -48250,14 +48250,14 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="LIFE"></code>
        <display value="life insurance policy"></display>
-       <definition value="Definition: A policy under which the insurer agrees to pay a sum of money upon the occurrence of the covered partys death. In return, the policyholder agrees to pay a stipulated amount called a premium at regular intervals.  Life insurance indemnifies the beneficiary for the loss of the insurable interest that a beneficiary has in the life of a covered party.  For persons related by blood, a substantial interest established through love and affection, and for all other persons, a lawful and substantial economic interest in having the life of the insured continue. An insurable interest is required when purchasing life insurance on another person. Specific exclusions are often written into the contract to limit the liability of the insurer; for example claims resulting from suicide or relating to war, riot and civil commotion.
+       <definition value="Definition: A policy under which the insurer agrees to pay a sum of money upon the occurrence of the covered partys death. In return, the policyholder agrees to pay a stipulated amount called a premium at regular intervals.  Life insurance indemnifies the beneficiary for the loss of the insurable interest that a beneficiary has in the life of a covered party.  For persons related by blood, a substantial interest established through love and affection, and for all other persons, a lawful and substantial economic interest in having the life of the insured continue. An insurable interest is required when purchasing life insurance on another person. Specific exclusions are often written into the contract to limit the liability of the insurer; for example claims resulting from suicide or relating to war, riot and civil commotion.
 
         
          Discussion:A life insurance policy may be used by the covered party as a source of health care coverage in the case of  a viatical settlement, which is the sale of a life insurance policy by the policy owner, before the policy matures. Such a sale, at a price discounted from the face amount of the policy but usually in excess of the premiums paid or current cash surrender value, provides the seller an immediate cash settlement. Generally, viatical settlements involve insured individuals with a life expectancy of less than two years. In countries without state-subsidized healthcare and high healthcare costs (e.g. United States), this is a practical way to pay extremely high health insurance premiums that severely ill people face. Some people are also familiar with life settlements, which are similar transactions but involve insureds with longer life expectancies (two to fifteen years)."></definition>
        <concept>
         <code value="ANNU"></code>
         <display value="annuity policy"></display>
-        <definition value="Definition: A policy that, after an initial premium or premiums, pays out a sum at pre-determined intervals.
+        <definition value="Definition: A policy that, after an initial premium or premiums, pays out a sum at pre-determined intervals.
 
         For example, a policy holder may pay $10,000, and in return receive $150 each month until he dies; or $1,000 for each of 14 years or death benefits if he dies before the full term of the annuity has elapsed."></definition>
        </concept>
@@ -48280,10 +48280,10 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="REI"></code>
        <display value="reinsurance policy"></display>
-       <definition value="Definition: An agreement between two or more insurance companies by which the risk of loss is proportioned. Thus the risk of loss is spread and a disproportionately large loss under a single policy does not fall on one insurance company. Acceptance by an insurer, called a reinsurer, of all or part of the risk of loss of another insurance company.
+       <definition value="Definition: An agreement between two or more insurance companies by which the risk of loss is proportioned. Thus the risk of loss is spread and a disproportionately large loss under a single policy does not fall on one insurance company. Acceptance by an insurer, called a reinsurer, of all or part of the risk of loss of another insurance company.
 
         
-         Discussion: Reinsurance is a means by which an insurance company can protect itself against the risk of losses with other insurance companies. Individuals and corporations obtain insurance policies to provide protection for various risks (hurricanes, earthquakes, lawsuits, collisions, sickness and death, etc.). Reinsurers, in turn, provide insurance to insurance companies.
+         Discussion: Reinsurance is a means by which an insurance company can protect itself against the risk of losses with other insurance companies. Individuals and corporations obtain insurance policies to provide protection for various risks (hurricanes, earthquakes, lawsuits, collisions, sickness and death, etc.). Reinsurers, in turn, provide insurance to insurance companies.
 
         For example, an HMO may purchase a reinsurance policy to protect itself from losing too much money from one insured's particularly expensive health care costs. An insurance company issuing an automobile liability policy, with a limit of $100,000 per accident may reinsure its liability in excess of $10,000. A fire insurance company which issues a large policy generally reinsures a portion of the risk with one or several other companies. Also called risk control insurance or stop-loss insurance."></definition>
       </concept>
@@ -48291,11 +48291,11 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <code value="SURPL"></code>
        <display value="surplus line insurance policy"></display>
        <definition value="Definition: 
-        
+        
 
         
          
-          A risk or part of a risk for which there is no normal insurance market available.
+          A risk or part of a risk for which there is no normal insurance market available.
 
          
          
@@ -48316,7 +48316,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       </modifierExtension>
       <code value="_ActProgramTypeCode"></code>
       <display value="ActProgramTypeCode"></display>
-      <definition value="Definition: A set of codes used to indicate coverage under a program.  A program is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health, financial, and demographic status. Programs are typically established or permitted by legislation with provisions for ongoing government oversight.  Regulations may mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation.  Risk of loss under a program in most cases would not meet what an underwriter would consider an insurable risk, i.e., the risk is not random in nature, not financially measurable, and likely requires subsidization with government funds.
+      <definition value="Definition: A set of codes used to indicate coverage under a program.  A program is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health, financial, and demographic status. Programs are typically established or permitted by legislation with provisions for ongoing government oversight.  Regulations may mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation.  Risk of loss under a program in most cases would not meet what an underwriter would consider an insurable risk, i.e., the risk is not random in nature, not financially measurable, and likely requires subsidization with government funds.
 
         
          Discussion: Programs do not have policy holders or subscribers.  Program eligibles are enrolled based on health status, statutory eligibility, financial status, or age.  Program eligibles who are covered parties under the program may be referred to as members, beneficiaries, eligibles, or recipients.  Programs risk are underwritten by not for profit organizations such as governmental entities, and the beneficiaries typically do not pay for any or some portion of the cost of coverage.  See CoveredPartyRoleType."></definition>
@@ -48342,7 +48342,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="GOVEMP"></code>
        <display value="government employee health program"></display>
-       <definition value="Definition: A set of codes used to indicate a government program that is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health and financial status. Government programs are established or permitted by legislation with provisions for ongoing government oversight.  Regulation mandates the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency is charged with implementing the program in accordance to the regulation
+       <definition value="Definition: A set of codes used to indicate a government program that is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health and financial status. Government programs are established or permitted by legislation with provisions for ongoing government oversight.  Regulation mandates the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency is charged with implementing the program in accordance to the regulation
 
         
          Example: Federal employee health benefit program in the U.S."></definition>
@@ -48355,7 +48355,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="IND"></code>
        <display value="indigenous peoples health program"></display>
-       <definition value="Definition: Services provided directly and through contracted and operated indigenous peoples health programs.
+       <definition value="Definition: Services provided directly and through contracted and operated indigenous peoples health programs.
 
         
          Example: Indian Health Service in the U.S."></definition>
@@ -48363,7 +48363,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="MILITARY"></code>
        <display value="military health program"></display>
-       <definition value="Definition: A government program that provides coverage for health services to military personnel, retirees, and dependents.  A covered party who is a subscriber can choose from among Fee-for-Service (FFS) plans, and their Preferred Provider Organizations (PPO), or Plans offering a Point of Service (POS) Product, or Health Maintenance Organizations.
+       <definition value="Definition: A government program that provides coverage for health services to military personnel, retirees, and dependents.  A covered party who is a subscriber can choose from among Fee-for-Service (FFS) plans, and their Preferred Provider Organizations (PPO), or Plans offering a Point of Service (POS) Product, or Health Maintenance Organizations.
 
         
          Example: In the U.S., TRICARE, CHAMPUS."></definition>
@@ -48376,7 +48376,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="SOCIAL"></code>
        <display value="social service program"></display>
-       <definition value="Definition: A social service program funded by a public or governmental entity.
+       <definition value="Definition: A social service program funded by a public or governmental entity.
 
         
          Example: Programs providing habilitation, food, lodging, medicine, transportation, equipment, devices, products, education, training, counseling, alteration of living or work space, and other resources to persons meeting eligibility criteria."></definition>
@@ -49307,7 +49307,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
      <concept>
       <code value="_ActInvoiceGroupCode"></code>
       <display value="ActInvoiceGroupCode"></display>
-      <definition value="Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.
+      <definition value="Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.
 
         Invoice elements of this type signify a grouping of one or more children (detail) invoice elements.  They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements."></definition>
       <property>
@@ -49317,9 +49317,9 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="_ActInvoiceInterGroupCode"></code>
        <display value="ActInvoiceInterGroupCode"></display>
-       <definition value="Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.
+       <definition value="Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.
 
-        Invoice elements of this type signify a grouping of one or more children (detail) invoice elements.  They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements.
+        Invoice elements of this type signify a grouping of one or more children (detail) invoice elements.  They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements.
 
         The domain is only specified for an intermediate invoice element group (non-root or non-top level) for an Invoice."></definition>
        <property>
@@ -49365,9 +49365,9 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="_ActInvoiceRootGroupCode"></code>
        <display value="ActInvoiceRootGroupCode"></display>
-       <definition value="Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.
+       <definition value="Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.
 
-        Invoice elements of this type signify a grouping of one or more children (detail) invoice elements.  They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements.
+        Invoice elements of this type signify a grouping of one or more children (detail) invoice elements.  They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements.
 
         Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product.  The domain is only specified for the root (top level) invoice element group for an Invoice."></definition>
        <property>
@@ -49377,47 +49377,47 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="CPINV"></code>
         <display value="clinical product invoice"></display>
-        <definition value="Clinical product invoice where the Invoice Grouping contains one or more billable item and is supported by clinical product(s).
+        <definition value="Clinical product invoice where the Invoice Grouping contains one or more billable item and is supported by clinical product(s).
 
         For example, a crutch or a wheelchair."></definition>
        </concept>
        <concept>
         <code value="CSINV"></code>
         <display value="clinical service invoice"></display>
-        <definition value="Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services.
+        <definition value="Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services.
 
-        [1] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service.
+        [1] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service.
 
-        For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization).
+        For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization).
 
-        [2] Multiple Clinical services invoice where the Invoice Grouping contains more than one billable item, supported by one or more clinical services.  The services can be distinct and over multiple dates, but for the same patient. This type of invoice includes a series of treatments which must be adjudicated together.
+        [2] Multiple Clinical services invoice where the Invoice Grouping contains more than one billable item, supported by one or more clinical services.  The services can be distinct and over multiple dates, but for the same patient. This type of invoice includes a series of treatments which must be adjudicated together.
 
-        For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together.
+        For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together.
 
-        [3] Repeated Clinical services invoice where the Invoice Grouping contains one or more billable item, supported by the same clinical service repeated over a period of time.
+        [3] Repeated Clinical services invoice where the Invoice Grouping contains one or more billable item, supported by the same clinical service repeated over a period of time.
 
         For example, the same Chiropractic adjustment (service or treatment) delivered on 3 separate occasions over a period of time at the discretion of the provider (e.g. month)."></definition>
        </concept>
        <concept>
         <code value="CSPINV"></code>
         <display value="clinical service and product"></display>
-        <definition value="A clinical Invoice Grouping consisting of one or more services and one or more product.  Billing for these service(s) and product(s) are supported by multiple clinical billable events (acts).
+        <definition value="A clinical Invoice Grouping consisting of one or more services and one or more product.  Billing for these service(s) and product(s) are supported by multiple clinical billable events (acts).
 
-        All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator.
+        All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator.
 
         For example , a brace (product) invoiced together with the fitting (service)."></definition>
        </concept>
        <concept>
         <code value="FININV"></code>
         <display value="financial invoice"></display>
-        <definition value="Invoice Grouping without clinical justification.  These will not require identification of participants and associations from a clinical context such as patient and provider.
+        <definition value="Invoice Grouping without clinical justification.  These will not require identification of participants and associations from a clinical context such as patient and provider.
 
         Examples are interest charges and mileage."></definition>
        </concept>
        <concept>
         <code value="OHSINV"></code>
         <display value="oral health service"></display>
-        <definition value="A clinical Invoice Grouping consisting of one or more oral health services. Billing for these service(s) are supported by multiple clinical billable events (acts).
+        <definition value="A clinical Invoice Grouping consisting of one or more oral health services. Billing for these service(s) are supported by multiple clinical billable events (acts).
 
         All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator."></definition>
        </concept>
@@ -49937,7 +49937,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="_ActMedicationTherapyDurationWorkingListCode"></code>
        <display value="act medication therapy duration working list"></display>
-       <definition value="Definition:A collection of concepts that identifies different types of 'duration-based' mediation working lists.
+       <definition value="Definition:A collection of concepts that identifies different types of 'duration-based' mediation working lists.
 
         
          Examples:&quot;Continuous/Chronic&quot; &quot;Short-Term&quot; and &quot;As Needed&quot;"></definition>
@@ -50069,39 +50069,39 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
     <concept>
      <code value="_ActObservationVerificationType"></code>
      <display value="act observation verification"></display>
-     <definition value="Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity.
+     <definition value="Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity.
 
         
          Examples:
-        
+        
 
         
          
-          Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program
+          Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program
 
          
          
-          Verification of record - e.g., person has record in an immunization registry
+          Verification of record - e.g., person has record in an immunization registry
 
          
          
-          Verification of enumeration - e.g. NPI
+          Verification of enumeration - e.g. NPI
 
          
          
-          Verification of Board Certification - provider specific
+          Verification of Board Certification - provider specific
 
          
          
-          Verification of Certification - e.g. JAHCO, NCQA, URAC
+          Verification of Certification - e.g. JAHCO, NCQA, URAC
 
          
          
-          Verification of Conformance - e.g. entity use with HIPAA, conformant to the CCHIT EHR system criteria
+          Verification of Conformance - e.g. entity use with HIPAA, conformant to the CCHIT EHR system criteria
 
          
          
-          Verification of Provider Credentials
+          Verification of Provider Credentials
 
          
          
@@ -50119,7 +50119,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
     <concept>
      <code value="_ActPaymentCode"></code>
      <display value="ActPaymentCode"></display>
-     <definition value="Code identifying the method or the movement of payment instructions.
+     <definition value="Code identifying the method or the movement of payment instructions.
 
         Codes are drawn from X12 data element 591 (PaymentMethodCode)"></definition>
      <property>
@@ -50304,13 +50304,13 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
      <concept>
       <code value="_ActPrivacyPolicy"></code>
       <display value="ActPrivacyPolicy"></display>
-      <definition value="A policy deeming certain information to be private to an individual or organization.
+      <definition value="A policy deeming certain information to be private to an individual or organization.
 
         
-         Definition: A mandate, obligation, requirement, rule, or expectation relating to privacy.
+         Definition: A mandate, obligation, requirement, rule, or expectation relating to privacy.
 
         
-         Discussion: ActPrivacyPolicyType codes support the designation of the 1..* policies that are applicable to an Act such as a Consent Directive, a Role such as a VIP Patient, or an Entity such as a patient who is a minor.  1..* ActPrivacyPolicyType values may be associated with an Act or Role to indicate the policies that govern the assignment of an Act or Role confidentialityCode.  Use of multiple ActPrivacyPolicyType values enables fine grain specification of applicable policies, but must be carefully assigned to ensure cogency and avoid creation of conflicting policy mandates.
+         Discussion: ActPrivacyPolicyType codes support the designation of the 1..* policies that are applicable to an Act such as a Consent Directive, a Role such as a VIP Patient, or an Entity such as a patient who is a minor.  1..* ActPrivacyPolicyType values may be associated with an Act or Role to indicate the policies that govern the assignment of an Act or Role confidentialityCode.  Use of multiple ActPrivacyPolicyType values enables fine grain specification of applicable policies, but must be carefully assigned to ensure cogency and avoid creation of conflicting policy mandates.
 
         
          Usage Note: Statutory title may be named in the ActClassPolicy Act Act.title to specify which privacy policy is being referenced."></definition>
@@ -50321,14 +50321,14 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="_ActConsentDirective"></code>
        <display value="ActConsentDirective"></display>
-       <definition value="Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated.
+       <definition value="Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated.
 
         
-         Usage Note: Such agreements may be considered &quot;consent directives&quot; or &quot;contracts&quot; depending on the context, and are considered closely related or synonymous from a legal perspective.
+         Usage Note: Such agreements may be considered &quot;consent directives&quot; or &quot;contracts&quot; depending on the context, and are considered closely related or synonymous from a legal perspective.
 
         
          Examples: 
-        
+        
 
         
          Healthcare Privacy Consent Directive permitting or restricting in whole or part the collection, access, use, and disclosure of health information, and any associated handling caveats.
@@ -50345,7 +50345,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="EMRGONLY"></code>
         <display value="emergency only"></display>
-        <definition value="This general consent directive specifically limits disclosure of health information for purpose of emergency treatment. Additional parameters may further limit the disclosure to specific users, roles, duration, types of information, and impose uses obligations.
+        <definition value="This general consent directive specifically limits disclosure of health information for purpose of emergency treatment. Additional parameters may further limit the disclosure to specific users, roles, duration, types of information, and impose uses obligations.
 
         
          Definition: Opt-in to disclosure of health information for emergency only consent directive."></definition>
@@ -50353,17 +50353,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="GRANTORCHOICE"></code>
         <display value="grantor choice"></display>
-        <definition value="A grantor's terms of agreement to which a grantee may assent or dissent, and which may include an opportunity for a grantee to request restrictions or extensions.
+        <definition value="A grantor's terms of agreement to which a grantee may assent or dissent, and which may include an opportunity for a grantee to request restrictions or extensions.
 
         
-         Comment: A grantor typically is able to stipulate preferred terms of agreement when the grantor has control over the topic of the agreement, which a grantee must accept in full or may be offered an opportunity to extend or restrict certain terms.
+         Comment: A grantor typically is able to stipulate preferred terms of agreement when the grantor has control over the topic of the agreement, which a grantee must accept in full or may be offered an opportunity to extend or restrict certain terms.
 
         
-         Usage Note: If the grantor's term of agreement must be accepted in full, then this is considered &quot;basic consent&quot;.  If a grantee is offered an opportunity to extend or restrict certain terms, then the agreement is considered &quot;granular consent&quot;.
+         Usage Note: If the grantor's term of agreement must be accepted in full, then this is considered &quot;basic consent&quot;.  If a grantee is offered an opportunity to extend or restrict certain terms, then the agreement is considered &quot;granular consent&quot;.
 
         
          Examples: 
-        
+        
 
         
          Healthcare: A PHR account holder [grantor] may require any PHR user [grantee]  to accept the terms of agreement in full, or may permit a PHR user to extend or restrict terms selected by the account holder or requested by the PHR user.
@@ -50372,17 +50372,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="IMPLIED"></code>
         <display value="implied consent"></display>
-        <definition value="A grantor's presumed assent to the grantee's terms of agreement is based on the grantor's behavior, which may result from not expressly assenting to the consent directive offered, or from having no right to assent or dissent offered by the grantee.
+        <definition value="A grantor's presumed assent to the grantee's terms of agreement is based on the grantor's behavior, which may result from not expressly assenting to the consent directive offered, or from having no right to assent or dissent offered by the grantee.
 
         
-         Comment: Implied or &quot;implicit&quot; consent occurs when the behavior of the grantor is understood by a reasonable person to signal agreement to the grantee's terms.
+         Comment: Implied or &quot;implicit&quot; consent occurs when the behavior of the grantor is understood by a reasonable person to signal agreement to the grantee's terms.
 
         
-         Usage Note: Implied consent with no opportunity to assent or dissent to certain terms is considered &quot;basic consent&quot;.
+         Usage Note: Implied consent with no opportunity to assent or dissent to certain terms is considered &quot;basic consent&quot;.
 
         
          Examples: 
-        
+        
 
         
          Healthcare: A patient schedules an appointment with a provider, and either does not take the opportunity to expressly assent or dissent to the provider's consent directive, does not have an opportunity to do so, as in the case where emergency care is required, or simply behaves as though the patient [grantor] agrees to the rights granted to the provider [grantee] in an implicit consent directive.
@@ -50393,17 +50393,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="IMPLIEDD"></code>
         <display value="implied consent with opportunity to dissent"></display>
-        <definition value="A grantor's presumed assent to the grantee's terms of agreement, which is based on the grantor's behavior, and includes a right to dissent to certain terms. 
+        <definition value="A grantor's presumed assent to the grantee's terms of agreement, which is based on the grantor's behavior, and includes a right to dissent to certain terms. 
 
         
-         Comment: A grantor assenting to the grantee's terms of agreement may or may not exercise a right to dissent to grantor selected terms or to grantee's selected terms to which a grantor may dissent.
+         Comment: A grantor assenting to the grantee's terms of agreement may or may not exercise a right to dissent to grantor selected terms or to grantee's selected terms to which a grantor may dissent.
 
         
-         Usage Note: Implied or &quot;implicit&quot; consent with an &quot;opportunity to dissent&quot; occurs when the grantor's behavior is understood by a reasonable person to signal assent to the grantee's terms of agreement whether the grantor requests or the grantee approves further restrictions, is considered &quot;granular consent&quot;.
+         Usage Note: Implied or &quot;implicit&quot; consent with an &quot;opportunity to dissent&quot; occurs when the grantor's behavior is understood by a reasonable person to signal assent to the grantee's terms of agreement whether the grantor requests or the grantee approves further restrictions, is considered &quot;granular consent&quot;.
 
         
          Examples: 
-        
+        
 
         
          Healthcare Examples: A healthcare provider deems a patient's assent to disclosure of health information to family members and friends, but offers an opportunity or permits the patient to dissent to such disclosures.
@@ -50413,17 +50413,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="NOCONSENT"></code>
         <display value="no consent"></display>
-        <definition value="No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement.
+        <definition value="No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement.
 
         
-         Comment: A &quot;No Consent&quot; policy scheme provides no opportunity for accommodation of an individual's preferences, and may not comply with Fair Information Practice Principles [FIPP] by enabling the data subject to object, access collected information, correct errors, or have accounting of disclosures.
+         Comment: A &quot;No Consent&quot; policy scheme provides no opportunity for accommodation of an individual's preferences, and may not comply with Fair Information Practice Principles [FIPP] by enabling the data subject to object, access collected information, correct errors, or have accounting of disclosures.
 
         
-         Usage Note: The grantee's terms of agreement, may be available to the grantor by reviewing the grantee's privacy policies, but there is no notice by which a grantor is apprised of the policy directly or able to acknowledge.
+         Usage Note: The grantee's terms of agreement, may be available to the grantor by reviewing the grantee's privacy policies, but there is no notice by which a grantor is apprised of the policy directly or able to acknowledge.
 
         
          Examples: 
-        
+        
 
         
          Healthcare: Without notification or an opportunity to assent or dissent, a patient's health information is automatically included in and available (often according to certain rules) through a health information exchange.  Note that this differs from implied consent, where the patient is assumed to have consented.
@@ -50434,7 +50434,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="NOPP"></code>
         <display value="notice of privacy practices"></display>
-        <definition value="Acknowledgement of custodian notice of privacy practices.
+        <definition value="Acknowledgement of custodian notice of privacy practices.
 
         
          Usage Notes: This type of consent directive acknowledges a custodian's notice of privacy practices including its permitted collection, access, use and disclosure of health information to users and for purposes of use specified."></definition>
@@ -50442,17 +50442,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="OPTIN"></code>
         <display value="opt-in"></display>
-        <definition value="A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms.
+        <definition value="A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms.
 
         
-         Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies.
+         Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies.
 
         
-         Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered &quot;basic consent&quot;.
+         Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered &quot;basic consent&quot;.
 
         
          Examples: 
-        
+        
 
         
          Healthcare: A patient [grantor] signs a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, and revocation policies.
@@ -50461,17 +50461,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="OPTINR"></code>
         <display value="opt-in with restrictions"></display>
-        <definition value="A grantor's assent to the grantee's terms of an agreement with an opportunity for to dissent to certain grantor or grantee selected terms.
+        <definition value="A grantor's assent to the grantee's terms of an agreement with an opportunity for to dissent to certain grantor or grantee selected terms.
 
         
-         Comment: A grantor dissenting to the grantee's terms of agreement may or may not exercise a right to assent to grantor's pre-approved restrictions or to grantee's selected terms to which a grantor may dissent.
+         Comment: A grantor dissenting to the grantee's terms of agreement may or may not exercise a right to assent to grantor's pre-approved restrictions or to grantee's selected terms to which a grantor may dissent.
 
         
-         Usage Note: Opt-in with restrictions is considered &quot;granular consent&quot; because the grantor has an opportunity to narrow the permissions sought by the grantee.
+         Usage Note: Opt-in with restrictions is considered &quot;granular consent&quot; because the grantor has an opportunity to narrow the permissions sought by the grantee.
 
         
          Examples: 
-        
+        
 
         
          Healthcare:  A patient assent to grantee's consent directive terms for collection, access, use, or disclosure of health information, and dissents to disclosure to certain recipients as allowed by the provider's pre-approved restriction list.
@@ -50480,17 +50480,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="OPTOUT"></code>
         <display value="op-out"></display>
-        <definition value="A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms.
+        <definition value="A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms.
 
         
-         Comment: Rejection of a grantee's terms of agreement pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies.
+         Comment: Rejection of a grantee's terms of agreement pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies.
 
         
-         Usage Note: Opt-out with no opportunity for a grantor to permit certain permissions sought by the grantee is considered &quot;basic consent&quot;.
+         Usage Note: Opt-out with no opportunity for a grantor to permit certain permissions sought by the grantee is considered &quot;basic consent&quot;.
 
         
          Examples: 
-        
+        
 
         
          Healthcare: A patient [grantor] declines to sign a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, revocation policies, and consequences of not assenting.
@@ -50500,17 +50500,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="OPTOUTE"></code>
         <display value="opt-out with exceptions"></display>
-        <definition value="A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms.
+        <definition value="A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms.
 
         
-         Comment: A rejection of a grantee's terms of agreement while assenting to certain permissions sought by the grantee or requesting approval of additional grantor terms.
+         Comment: A rejection of a grantee's terms of agreement while assenting to certain permissions sought by the grantee or requesting approval of additional grantor terms.
 
         
-         Usage Note: Opt-out with exceptions is considered a &quot;granular consent&quot; because the grantor has an opportunity to accept certain permissions sought by the grantee or request additional grantor terms, while rejecting other grantee terms.
+         Usage Note: Opt-out with exceptions is considered a &quot;granular consent&quot; because the grantor has an opportunity to accept certain permissions sought by the grantee or request additional grantor terms, while rejecting other grantee terms.
 
         
          Examples: 
-        
+        
 
         
          Healthcare: A patient [grantor] dissents to a health information exchange consent directive with the exception of disclosure based on a limited &quot;time to live&quot; shared secret [e.g., a token or password], which the patient can give to a provider when seeking care.
@@ -50520,7 +50520,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="_ActPrivacyLaw"></code>
        <display value="ActPrivacyLaw"></display>
-       <definition value="A jurisdictional mandate, regulation, obligation, requirement, rule, or expectation deeming certain information to be private to an individual or organization, which is imposed on:
+       <definition value="A jurisdictional mandate, regulation, obligation, requirement, rule, or expectation deeming certain information to be private to an individual or organization, which is imposed on:
 
         
          The activity of a governed party
@@ -50533,17 +50533,17 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="_ActUSPrivacyLaw"></code>
         <display value="_ActUSPrivacyLaw"></display>
-        <definition value="Definition: A jurisdictional mandate in the U.S. relating to privacy.
+        <definition value="Definition: A jurisdictional mandate in the U.S. relating to privacy.
 
         
          Usage Note: ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies.  May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1."></definition>
         <concept>
          <code value="42CFRPart2"></code>
          <display value="42 CFR Part2"></display>
-         <definition value="42 CFR Part 2 stipulates the right of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program.
+         <definition value="42 CFR Part 2 stipulates the right of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program.
 
         
-         Definition: Non-disclosure of health information relating to health care paid for by a federally assisted substance abuse program without patient consent.
+         Definition: Non-disclosure of health information relating to health care paid for by a federally assisted substance abuse program without patient consent.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -50551,10 +50551,10 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="CommonRule"></code>
          <display value="Common Rule"></display>
-         <definition value="U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46) that has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements.
+         <definition value="U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46) that has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements.
 
         
-         Definition: U.S. federal laws governing research-related privacy policies.
+         Definition: U.S. federal laws governing research-related privacy policies.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies."></definition>
@@ -50562,10 +50562,10 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="HIPAANOPP"></code>
          <display value="HIPAA notice of privacy practices"></display>
-         <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Subpart E) permits access, use and disclosure of certain personal health information (PHI as defined under the law) for purposes of Treatment, Payment, and Operations, and requires that the provider ask that patients acknowledge the Provider's Notice of Privacy Practices as permitted conduct under the law.
+         <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Subpart E) permits access, use and disclosure of certain personal health information (PHI as defined under the law) for purposes of Treatment, Payment, and Operations, and requires that the provider ask that patients acknowledge the Provider's Notice of Privacy Practices as permitted conduct under the law.
 
         
-         Definition: Notification of HIPAA Privacy Practices.
+         Definition: Notification of HIPAA Privacy Practices.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies."></definition>
@@ -50573,10 +50573,10 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="HIPAAPsyNotes"></code>
          <display value="HIPAA psychotherapy notes"></display>
-         <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Section 164.508) requires authorization for certain uses and disclosure of psychotherapy notes.
+         <definition value="The U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Part 164 Section 164.508) requires authorization for certain uses and disclosure of psychotherapy notes.
 
         
-         Definition: Authorization that must be obtained for disclosure of psychotherapy notes.
+         Definition: Authorization that must be obtained for disclosure of psychotherapy notes.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -50584,10 +50584,10 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="HIPAASelfPay"></code>
          <display value="HIPAA self-pay"></display>
-         <definition value="Section 13405(a) of the Health Information Technology for Economic and Clinical Health Act (HITECH) stipulates the right of an individual to have disclosures regarding certain health care items or services for which the individual pays out of pocket in full restricted from a health plan.
+         <definition value="Section 13405(a) of the Health Information Technology for Economic and Clinical Health Act (HITECH) stipulates the right of an individual to have disclosures regarding certain health care items or services for which the individual pays out of pocket in full restricted from a health plan.
 
         
-         Definition: Non-disclosure of health information to a health plan relating to health care items or services for which an individual pays out of pocket in full.
+         Definition: Non-disclosure of health information to a health plan relating to health care items or services for which an individual pays out of pocket in full.
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -50595,12 +50595,12 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="Title38Section7332"></code>
          <display value="Title 38 Section 7332"></display>
-         <definition value="Title 38 Part 1-protected information may only be disclosed to a third party with the special written consent of the patient except where expressly authorized by 38 USC 7332. VA may disclose this information for specific purposes to: VA employees on a need to know basis - more restrictive than Privacy Act need to know; contractors who need the information in order to perform or fulfil the duties of the contract; and researchers who provide assurances that the information will not be identified in any report. This information may also be disclosed without consent where patient lacks decision-making capacity; in a medical emergency for the purpose of treating a condition which poses an immediate threat to the health of any individual and which requires immediate medical intervention; for eye, tissue, or organ donation purposes; and disclosure of HIV information for public health purposes.
+         <definition value="Title 38 Part 1-protected information may only be disclosed to a third party with the special written consent of the patient except where expressly authorized by 38 USC 7332. VA may disclose this information for specific purposes to: VA employees on a need to know basis - more restrictive than Privacy Act need to know; contractors who need the information in order to perform or fulfil the duties of the contract; and researchers who provide assurances that the information will not be identified in any report. This information may also be disclosed without consent where patient lacks decision-making capacity; in a medical emergency for the purpose of treating a condition which poses an immediate threat to the health of any individual and which requires immediate medical intervention; for eye, tissue, or organ donation purposes; and disclosure of HIV information for public health purposes.
 
         
-         Definition: Title 38 Part 1 - Section 1.462 Confidentiality restrictions.
+         Definition: Title 38 Part 1 - Section 1.462 Confidentiality restrictions.
 
-        (a) General. The patient records to which Sections 1.460 through 1.499 of this part apply may be disclosed or used only as permitted by these regulations and may not otherwise be disclosed or used in any civil, criminal, administrative, or legislative proceedings conducted by any Federal, State, or local authority. Any disclosure made under these regulations must be limited to that information which is necessary to carry out the purpose of the disclosure. SUBCHAPTER III--PROTECTION OF PATIENT RIGHTS Sec. 7332. Confidentiality of certain medical records (a)(1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b).
+        (a) General. The patient records to which Sections 1.460 through 1.499 of this part apply may be disclosed or used only as permitted by these regulations and may not otherwise be disclosed or used in any civil, criminal, administrative, or legislative proceedings conducted by any Federal, State, or local authority. Any disclosure made under these regulations must be limited to that information which is necessary to carry out the purpose of the disclosure. SUBCHAPTER III--PROTECTION OF PATIENT RIGHTS Sec. 7332. Confidentiality of certain medical records (a)(1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b).
 
         
          Usage Note: May be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialityCode complies."></definition>
@@ -50610,7 +50610,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
       <concept>
        <code value="_InformationSensitivityPolicy"></code>
        <display value="InformationSensitivityPolicy"></display>
-       <definition value="A mandate, obligation, requirement, rule, or expectation characterizing the value or importance of a resource and may include its vulnerability. (Based on ISO7498-2:1989. Note: The vulnerability of personally identifiable sensitive information may be based on concerns that the unauthorized disclosure may result in social stigmatization or discrimination.) Description:  Types of Sensitivity policy that apply to Acts or Roles.  A sensitivity policy is adopted by an enterprise or group of enterprises (a 'policy domain') through a formal data use agreement that stipulates the value, importance, and vulnerability of information. A sensitivity code representing a sensitivity policy may be associated with criteria such as categories of information or sets of information identifiers (e.g., a value set of clinical codes or branch in a code system hierarchy).   These criteria may in turn be used for the Policy Decision Point in a Security Engine.  A sensitivity code may be used to set the confidentiality code used on information about Acts and Roles to trigger the security mechanisms required to control how security principals (i.e., a person, a machine, a software application) may act on the information (e.g., collection, access, use, or disclosure). Sensitivity codes are never assigned to the transport or business envelope containing patient specific information being exchanged outside of a policy domain as this would disclose the information intended to be protected by the policy.  When sensitive information is exchanged with others outside of a policy domain, the confidentiality code on the transport or business envelope conveys the receiver's responsibilities and indicates the how the information is to be safeguarded without unauthorized disclosure of the sensitive information.  This ensures that sensitive information is treated by receivers as the sender intends, accomplishing interoperability without point to point negotiations.
+       <definition value="A mandate, obligation, requirement, rule, or expectation characterizing the value or importance of a resource and may include its vulnerability. (Based on ISO7498-2:1989. Note: The vulnerability of personally identifiable sensitive information may be based on concerns that the unauthorized disclosure may result in social stigmatization or discrimination.) Description:  Types of Sensitivity policy that apply to Acts or Roles.  A sensitivity policy is adopted by an enterprise or group of enterprises (a 'policy domain') through a formal data use agreement that stipulates the value, importance, and vulnerability of information. A sensitivity code representing a sensitivity policy may be associated with criteria such as categories of information or sets of information identifiers (e.g., a value set of clinical codes or branch in a code system hierarchy).   These criteria may in turn be used for the Policy Decision Point in a Security Engine.  A sensitivity code may be used to set the confidentiality code used on information about Acts and Roles to trigger the security mechanisms required to control how security principals (i.e., a person, a machine, a software application) may act on the information (e.g., collection, access, use, or disclosure). Sensitivity codes are never assigned to the transport or business envelope containing patient specific information being exchanged outside of a policy domain as this would disclose the information intended to be protected by the policy.  When sensitive information is exchanged with others outside of a policy domain, the confidentiality code on the transport or business envelope conveys the receiver's responsibilities and indicates the how the information is to be safeguarded without unauthorized disclosure of the sensitive information.  This ensures that sensitive information is treated by receivers as the sender intends, accomplishing interoperability without point to point negotiations.
 
         
          Usage Note: Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements.  For example, an employee's sensitivity code would make little sense for use outside of a policy domain.   'Taboo' would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly.  Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply.  Newer systems may have a security engine that uses a sensitivity policy's criteria directly.  The specializable InformationSensitivityPolicy Act.code may be useful in some scenarios if used in combination with a sensitivity identifier and/or Act.title."></definition>
@@ -50621,7 +50621,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
        <concept>
         <code value="_ActInformationSensitivityPolicy"></code>
         <display value="ActInformationSensitivityPolicy"></display>
-        <definition value="Types of sensitivity policies that apply to Acts.  Act.confidentialityCode is defined in the RIM as &quot;constraints around appropriate disclosure of information about this Act, regardless of mood.&quot;
+        <definition value="Types of sensitivity policies that apply to Acts.  Act.confidentialityCode is defined in the RIM as &quot;constraints around appropriate disclosure of information about this Act, regardless of mood.&quot;
 
         
          Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises.  Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are  able to use information tagged with these sensitivity values."></definition>
@@ -50632,7 +50632,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="ETH"></code>
          <display value="substance abuse information sensitivity"></display>
-         <definition value="Policy for handling alcohol or drug-abuse information, which will be afforded heightened confidentiality.  Information handling protocols based on organizational policies related to alcohol or drug-abuse information that is deemed sensitive.
+         <definition value="Policy for handling alcohol or drug-abuse information, which will be afforded heightened confidentiality.  Information handling protocols based on organizational policies related to alcohol or drug-abuse information that is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50640,7 +50640,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="GDIS"></code>
          <display value="genetic disease information sensitivity"></display>
-         <definition value="Policy for handling genetic disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to genetic disease information that is deemed sensitive.
+         <definition value="Policy for handling genetic disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to genetic disease information that is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50648,7 +50648,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="HIV"></code>
          <display value="HIV/AIDS information sensitivity"></display>
-         <definition value="Policy for handling HIV or AIDS information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to HIV or AIDS information that is deemed sensitive.
+         <definition value="Policy for handling HIV or AIDS information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to HIV or AIDS information that is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50656,7 +50656,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="PSY"></code>
          <display value="psychiatry information sensitivity"></display>
-         <definition value="Policy for handling psychiatry information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to psychiatry information that is deemed sensitive.
+         <definition value="Policy for handling psychiatry information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to psychiatry information that is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50664,7 +50664,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="SCA"></code>
          <display value="sickle cell anemia"></display>
-         <definition value="Policy for handling sickle cell disease information, which is afforded heightened confidentiality.  Information handling protocols are based on organizational policies related to sickle cell disease information, which is deemed sensitive.
+         <definition value="Policy for handling sickle cell disease information, which is afforded heightened confidentiality.  Information handling protocols are based on organizational policies related to sickle cell disease information, which is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then the Act valued with this ActCode should be associated with an Act valued with any applicable laws from the ActPrivacyLaw code system."></definition>
@@ -50672,7 +50672,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="SOC"></code>
          <display value="social services sensitivity"></display>
-         <definition value="Information about provision of social services.
+         <definition value="Information about provision of social services.
 
         
          Usage Note: This is a temporary addition to FHIR to be proposed in harmonization."></definition>
@@ -50680,7 +50680,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="SDV"></code>
          <display value="sexual assault, abuse, or domestic violence information sensitivity"></display>
-         <definition value="Policy for handling sexual assault, abuse, or domestic violence information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexual assault, abuse, or domestic violence information that is deemed sensitive.
+         <definition value="Policy for handling sexual assault, abuse, or domestic violence information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexual assault, abuse, or domestic violence information that is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50688,7 +50688,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
         <concept>
          <code value="SEX"></code>
          <display value="sexuality and reproductive health information sensitivity"></display>
-         <definition value="Policy for handling sexuality and reproductive health information, which will be afforded heightened confidentiality.  Information handling protocols based on organizational policies related to sexuality and reproductive health information that is deemed sensitive.
+         <definition value="Policy for handling sexuality and reproductive health information, which will be afforded heightened confidentiality.  Information handling protocols based on organizational policies related to sexuality and reproductive health information that is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50697,7 +50697,7 @@ The kind of Act (e.g. physical examination, serum potassium, inpatient encounter
          <code value="STD"></code>
          <display value="sexually transmitted disease information sensitivity"></display>
          <definition value="Policy for handling sexually transmitted disease information, which will be afforded heightened confidentiality.
-Information handling protocols based on organizational policies related to sexually transmitted disease information that is deemed sensitive.
+Information handling protocols based on organizational policies related to sexually transmitted disease information that is deemed sensitive.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50705,10 +50705,10 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="TBOO"></code>
          <display value="taboo"></display>
-         <definition value="Policy for handling information not to be initially disclosed or discussed with patient except by a physician assigned to patient in this case. Information handling protocols based on organizational policies related to sensitive patient information that must be initially discussed with the patient by an attending physician before being disclosed to the patient.
+         <definition value="Policy for handling information not to be initially disclosed or discussed with patient except by a physician assigned to patient in this case. Information handling protocols based on organizational policies related to sensitive patient information that must be initially discussed with the patient by an attending physician before being disclosed to the patient.
 
         
-         Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
+         Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
 
         
          Open Issue: This definition conflates a rule and a characteristic, and there may be a similar issue with ts sibling codes."></definition>
@@ -50716,7 +50716,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="SICKLE"></code>
          <display value="sickle cell"></display>
-         <definition value="Types of sensitivity policies that apply to Acts.  Act.confidentialityCode is defined in the RIM as &quot;constraints around appropriate disclosure of information about this Act, regardless of mood.&quot;
+         <definition value="Types of sensitivity policies that apply to Acts.  Act.confidentialityCode is defined in the RIM as &quot;constraints around appropriate disclosure of information about this Act, regardless of mood.&quot;
 
         
          Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises.  Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values."></definition>
@@ -50729,7 +50729,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="_EntitySensitivityPolicyType"></code>
         <display value="EntityInformationSensitivityPolicy"></display>
-        <definition value="Types of sensitivity policies that may apply to a sensitive attribute on an Entity.
+        <definition value="Types of sensitivity policies that may apply to a sensitive attribute on an Entity.
 
         
          Usage Note: EntitySensitivity codes are used to convey a policy that is applicable to sensitive information conveyed by an entity attribute.  May be used to bind a Role.confidentialityCode associated with an Entity per organizational policy.  Role.confidentialityCode is defined in the RIM as &quot;an indication of the appropriate disclosure of information about this Role with respect to the playing Entity.&quot;"></definition>
@@ -50740,7 +50740,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="DEMO"></code>
          <display value="all demographic information sensitivity"></display>
-         <definition value="Policy for handling all demographic information about an information subject, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to all demographic about an information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling all demographic information about an information subject, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to all demographic about an information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50748,7 +50748,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="DOB"></code>
          <display value="date of birth information sensitivity"></display>
-         <definition value="Policy for handling information related to an information subject's date of birth, which will be afforded heightened confidentiality.Policies may govern sensitivity of information related to an information subject's date of birth, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling information related to an information subject's date of birth, which will be afforded heightened confidentiality.Policies may govern sensitivity of information related to an information subject's date of birth, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50756,7 +50756,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="GENDER"></code>
          <display value="gender and sexual orientation information sensitivity"></display>
-         <definition value="Policy for handling information related to an information subject's gender and sexual orientation, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's gender and sexual orientation, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling information related to an information subject's gender and sexual orientation, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's gender and sexual orientation, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50764,7 +50764,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="LIVARG"></code>
          <display value="living arrangement information sensitivity"></display>
-         <definition value="Policy for handling information related to an information subject's living arrangement, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's living arrangement, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling information related to an information subject's living arrangement, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's living arrangement, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50772,7 +50772,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="MARST"></code>
          <display value="marital status information sensitivity"></display>
-         <definition value="Policy for handling information related to an information subject's marital status, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's marital status, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling information related to an information subject's marital status, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's marital status, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50780,7 +50780,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="RACE"></code>
          <display value="race information sensitivity"></display>
-         <definition value="Policy for handling information related to an information subject's race, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's race, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling information related to an information subject's race, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's race, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50788,7 +50788,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="REL"></code>
          <display value="religion information sensitivity"></display>
-         <definition value="Policy for handling information related to an information subject's religious affiliation, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's religion, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling information related to an information subject's religious affiliation, which will be afforded heightened confidentiality.  Policies may govern sensitivity of information related to an information subject's religion, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50797,7 +50797,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="_RoleInformationSensitivityPolicy"></code>
         <display value="RoleInformationSensitivityPolicy"></display>
-        <definition value="Types of sensitivity policies that apply to Roles.
+        <definition value="Types of sensitivity policies that apply to Roles.
 
         
          Usage Notes: RoleSensitivity codes are used to bind information to a Role.confidentialityCode per organizational policy.  Role.confidentialityCode is defined in the RIM as &quot;an indication of the appropriate disclosure of information about this Role with respect to the playing Entity.&quot;"></definition>
@@ -50808,7 +50808,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="B"></code>
          <display value="business information sensitivity"></display>
-         <definition value="Policy for handling trade secrets such as financial information or intellectual property, which will be afforded heightened confidentiality.  Description:  Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality.
+         <definition value="Policy for handling trade secrets such as financial information or intellectual property, which will be afforded heightened confidentiality.  Description:  Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality.
 
         
          Usage Notes: No patient related information may ever be of this confidentiality level.   If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50816,7 +50816,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="EMPL"></code>
          <display value="employer information sensitivity"></display>
-         <definition value="Policy for handling information related to an employer which is deemed classified to protect an employee who is the information subject, and which will be afforded heightened confidentiality.  Description:  Policies may govern sensitivity of information related to an employer, such as law enforcement or national security, the identity of which could impact the privacy, well-being, or safety of an information subject who is an employee.
+         <definition value="Policy for handling information related to an employer which is deemed classified to protect an employee who is the information subject, and which will be afforded heightened confidentiality.  Description:  Policies may govern sensitivity of information related to an employer, such as law enforcement or national security, the identity of which could impact the privacy, well-being, or safety of an information subject who is an employee.
 
         
          Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50824,7 +50824,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="LOCIS"></code>
          <display value="location information sensitivity"></display>
-         <definition value="Policy for handling information related to the location of the information subject, which will be afforded heightened confidentiality.  Description:  Policies may govern sensitivity of information related to the location of the information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject.
+         <definition value="Policy for handling information related to the location of the information subject, which will be afforded heightened confidentiality.  Description:  Policies may govern sensitivity of information related to the location of the information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject.
 
         
          Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50832,7 +50832,7 @@ Information handling protocols based on organizational policies related to sexua
         <concept>
          <code value="SSP"></code>
          <display value="sensitive service provider information sensitivity"></display>
-         <definition value="Policy for handling information related to a provider of sensitive services, which will be afforded heightened confidentiality.  Description:  Policies may govern sensitivity of information related to providers who deliver sensitive healthcare services in order to protect the privacy, well-being, and safety of the provider and of patients receiving sensitive services.
+         <definition value="Policy for handling information related to a provider of sensitive services, which will be afforded heightened confidentiality.  Description:  Policies may govern sensitivity of information related to providers who deliver sensitive healthcare services in order to protect the privacy, well-being, and safety of the provider and of patients receiving sensitive services.
 
         
          Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50841,7 +50841,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="ADOL"></code>
         <display value="adolescent information sensitivity"></display>
-        <definition value="Policy for handling information related to an adolescent, which will be afforded heightened confidentiality per applicable organizational or jurisdictional policy.  An enterprise may have a policy that requires that adolescent patient information be provided heightened confidentiality.  Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location.
+        <definition value="Policy for handling information related to an adolescent, which will be afforded heightened confidentiality per applicable organizational or jurisdictional policy.  An enterprise may have a policy that requires that adolescent patient information be provided heightened confidentiality.  Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location.
 
         
          Usage Note: For use within an enterprise in which an adolescent is the information subject.  If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50849,7 +50849,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="CEL"></code>
         <display value="celebrity information sensitivity"></display>
-        <definition value="Policy for handling information related to a celebrity (people of public interest (VIP), which will be afforded heightened confidentiality.  Celebrities are people of public interest (VIP) about whose information an enterprise may have a policy that requires heightened confidentiality.  Information deemed sensitive may include health information and patient role information including patient status, demographics, next of kin, and location.
+        <definition value="Policy for handling information related to a celebrity (people of public interest (VIP), which will be afforded heightened confidentiality.  Celebrities are people of public interest (VIP) about whose information an enterprise may have a policy that requires heightened confidentiality.  Information deemed sensitive may include health information and patient role information including patient status, demographics, next of kin, and location.
 
         
          Usage Note:  For use within an enterprise in which the information subject is deemed a celebrity or very important person.  If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50857,7 +50857,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="DIA"></code>
         <display value="diagnosis information sensitivity"></display>
-        <definition value="Policy for handling information related to a diagnosis, health condition or health problem, which will be afforded heightened confidentiality.  Diagnostic, health condition or health problem related information may be deemed sensitive by organizational policy, and require heightened confidentiality.
+        <definition value="Policy for handling information related to a diagnosis, health condition or health problem, which will be afforded heightened confidentiality.  Diagnostic, health condition or health problem related information may be deemed sensitive by organizational policy, and require heightened confidentiality.
 
         
          Usage Note: For use within an enterprise that provides heightened confidentiality to  diagnostic, health condition or health problem related information deemed sensitive.   If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50865,7 +50865,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="DRGIS"></code>
         <display value="drug information sensitivity"></display>
-        <definition value="Policy for handling information related to a drug, which will be afforded heightened confidentiality. Drug information may be deemed sensitive by organizational policy, and require heightened confidentiality.
+        <definition value="Policy for handling information related to a drug, which will be afforded heightened confidentiality. Drug information may be deemed sensitive by organizational policy, and require heightened confidentiality.
 
         
          Usage Note: For use within an enterprise that provides heightened confidentiality to drug information deemed sensitive.   If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50873,7 +50873,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="EMP"></code>
         <display value="employee information sensitivity"></display>
-        <definition value="Policy for handling information related to an employee, which will be afforded heightened confidentiality. When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality.  Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location.
+        <definition value="Policy for handling information related to an employee, which will be afforded heightened confidentiality. When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality.  Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location.
 
         
          Usage Note: Policy for handling information related to an employee, which will be afforded heightened confidentiality.  Description:  When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality.  Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location."></definition>
@@ -50881,7 +50881,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="PDS"></code>
         <display value="patient default sensitivity"></display>
-        <definition value="Policy for handling information reported by the patient about another person, e.g., a family member, which will be afforded heightened confidentiality. Sensitive information reported by the patient about another person, e.g., family members may be deemed sensitive by default.  The flag may be set or cleared on patient's request.  
+        <definition value="Policy for handling information reported by the patient about another person, e.g., a family member, which will be afforded heightened confidentiality. Sensitive information reported by the patient about another person, e.g., family members may be deemed sensitive by default.  The flag may be set or cleared on patient's request.  
 
         
          Usage Note: For sensitive information relayed by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whether the patient requested that the information be deemed sensitive.)   If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50889,7 +50889,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="PRS"></code>
         <display value="patient requested sensitivity"></display>
-        <definition value="For sensitive information relayed by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whether the patient requested that the information be deemed sensitive.)   If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
+        <definition value="For sensitive information relayed by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whether the patient requested that the information be deemed sensitive.)   If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
 
         
          Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a patient as sensitive.   If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code."></definition>
@@ -50898,7 +50898,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="COMPT"></code>
        <display value="compartment"></display>
-       <definition value="This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program.  Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field.
+       <definition value="This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program.  Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field.
 
         Map: Aligns with ISO 2382-8 definition of Compartment - &quot;A division of data into isolated blocks with separate security controls for the purpose of reducing risk.&quot;"></definition>
        <concept>
@@ -50921,11 +50921,11 @@ Information handling protocols based on organizational policies related to sexua
      <concept>
       <code value="ActTrustPolicyType"></code>
       <display value="trust policy"></display>
-      <definition value="A mandate, obligation, requirement, rule, or expectation conveyed as security metadata between senders and receivers required to establish the reliability, authenticity, and trustworthiness of their transactions.
+      <definition value="A mandate, obligation, requirement, rule, or expectation conveyed as security metadata between senders and receivers required to establish the reliability, authenticity, and trustworthiness of their transactions.
 
-        Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability).
+        Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability).
 
-        Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain's trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. [Based on ISO IEC 10181-1 and NIST SP 800-63-2]
+        Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain's trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. [Based on ISO IEC 10181-1 and NIST SP 800-63-2]
 
         For example, identity proofing , level of assurance, and Trust Framework."></definition>
       <property>
@@ -50966,19 +50966,19 @@ Information handling protocols based on organizational policies related to sexua
      <concept>
       <code value="COVPOL"></code>
       <display value="benefit policy"></display>
-      <definition value="Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed on benefit coverage under a policy or program by a sponsor, underwriter or payor on:
+      <definition value="Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed on benefit coverage under a policy or program by a sponsor, underwriter or payor on:
 
         
          
-          The activity of another party
+          The activity of another party
 
          
          
-          The behavior of another party
+          The behavior of another party
 
          
          
-          The manner in which an act is executed
+          The manner in which an act is executed
 
          
         
@@ -50988,11 +50988,11 @@ Information handling protocols based on organizational policies related to sexua
      <concept>
       <code value="SecurityPolicy"></code>
       <display value="security policy"></display>
-      <definition value="Types of security policies that further specify the ActClassPolicy value set.
+      <definition value="Types of security policies that further specify the ActClassPolicy value set.
 
         
          Examples:
-        
+        
 
         
          obligation to encrypt
@@ -51000,7 +51000,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="ObligationPolicy"></code>
        <display value="obligation policy"></display>
-       <definition value="Conveys the mandated workflow action that an information custodian, receiver, or user must perform.  
+       <definition value="Conveys the mandated workflow action that an information custodian, receiver, or user must perform.  
 
         
          Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model:  This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision."></definition>
@@ -51082,9 +51082,9 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="ENCRYPT"></code>
         <display value="encrypt"></display>
-        <definition value="Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext.  
+        <definition value="Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext.  
 
-        
+        
 
         
          Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all.  (Per Infoway.)"></definition>
@@ -51112,7 +51112,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="LABEL"></code>
         <display value="assign security label"></display>
-        <definition value="Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding.
+        <definition value="Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding.
 
         
          Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes."></definition>
@@ -51125,7 +51125,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="MINEC"></code>
         <display value="minimum necessary"></display>
-        <definition value="Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use.  
+        <definition value="Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use.  
 
         
          Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver &quot;needs to know&quot; in order to perform permitted workflow or purpose of use."></definition>
@@ -51138,7 +51138,7 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="PRIVMARK"></code>
         <display value="privacy mark"></display>
-        <definition value="Custodian must create and/or maintain human readable security label tags as required by policy.
+        <definition value="Custodian must create and/or maintain human readable security label tags as required by policy.
 
         Map:  Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark:  &quot;If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label.&quot;"></definition>
        </concept>
@@ -51161,9 +51161,9 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="RefrainPolicy"></code>
        <display value="refrain policy"></display>
-       <definition value="Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances.
+       <definition value="Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances.
 
-        
+        
 
         
          Usage Notes: ISO 22600-2 species that a Refrain Policy &quot;defines actions the subjects must refrain from performing&quot;.  Per HL7 Composite Security and Privacy Domain Analysis Model:  May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc."></definition>
@@ -51210,14 +51210,14 @@ Information handling protocols based on organizational policies related to sexua
        <concept>
         <code value="NOPAT"></code>
         <display value="no disclosure to patient, family or caregivers without attending provider's authorization"></display>
-        <definition value="Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization.
+        <definition value="Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization.
 
         
-         Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access.
+         Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access.
 
-        Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance.
+        Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance.
 
-        FHIR print name is &quot;keep information from patient&quot;. Maps to the French realm - code: INVISIBLE_PATIENT.
+        FHIR print name is &quot;keep information from patient&quot;. Maps to the French realm - code: INVISIBLE_PATIENT.
 
         
          displayName: Document non visible par le patient
@@ -51609,7 +51609,7 @@ Information handling protocols based on organizational policies related to sexua
     <concept>
      <code value="_ActTransportationModeCode"></code>
      <display value="ActTransportationModeCode"></display>
-     <definition value="Characterizes how a transportation act was or will be carried out.
+     <definition value="Characterizes how a transportation act was or will be carried out.
 
         
          Examples: Via private transport, via public transit, via courier."></definition>
@@ -51620,7 +51620,7 @@ Information handling protocols based on organizational policies related to sexua
      <concept>
       <code value="_ActPatientTransportationModeCode"></code>
       <display value="ActPatientTransportationModeCode"></display>
-      <definition value="Definition: Characterizes how a patient was or will be transported to the site of a patient encounter.
+      <definition value="Definition: Characterizes how a patient was or will be transported to the site of a patient encounter.
 
         
          Examples: Via ambulance, via public transit, on foot."></definition>
@@ -51843,7 +51843,7 @@ Information handling protocols based on organizational policies related to sexua
      <concept>
       <code value="_IndividualCaseSafetyReportType"></code>
       <display value="Individual Case Safety Report Type"></display>
-      <definition value="A code that is used to indicate the type of case safety report received from sender. The current code example reference is from the International Conference on Harmonisation (ICH) Expert Workgroup guideline on Clinical Safety Data Management: Data Elements for Transmission of Individual Case Safety Reports. The unknown/unavailable option allows the transmission of information from a secondary sender where the initial sender did not specify the type of report.
+      <definition value="A code that is used to indicate the type of case safety report received from sender. The current code example reference is from the International Conference on Harmonisation (ICH) Expert Workgroup guideline on Clinical Safety Data Management: Data Elements for Transmission of Individual Case Safety Reports. The unknown/unavailable option allows the transmission of information from a secondary sender where the initial sender did not specify the type of report.
 
         Example concepts include: Spontaneous, Report from study, Other."></definition>
       <property>
@@ -51911,7 +51911,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="SPLCOATING"></code>
        <display value="coating"></display>
-       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, indicating whether it has one or more coatings such as sugar coating, film coating, or enteric coating.  Only coatings to the external surface or the dosage form should be considered (for example, coatings to individual pellets or granules inside a capsule or tablet are excluded from consideration).
+       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, indicating whether it has one or more coatings such as sugar coating, film coating, or enteric coating.  Only coatings to the external surface or the dosage form should be considered (for example, coatings to individual pellets or granules inside a capsule or tablet are excluded from consideration).
 
         
          Constraints: The Observation.value must be a Boolean (BL) with true for the presence or false for the absence of one or more coatings on a solid dosage form."></definition>
@@ -51919,7 +51919,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="SPLCOLOR"></code>
        <display value="color"></display>
-       <definition value="Definition:  A characteristic of an oral solid dosage form of a medicinal product, specifying the color or colors that most predominantly define the appearance of the dose form. SPLCOLOR is not an FDA specification for the actual color of solid dosage forms or the names of colors that can appear in labeling.
+       <definition value="Definition:  A characteristic of an oral solid dosage form of a medicinal product, specifying the color or colors that most predominantly define the appearance of the dose form. SPLCOLOR is not an FDA specification for the actual color of solid dosage forms or the names of colors that can appear in labeling.
 
         
          Constraints: The Observation.value must be a single coded value or a list of multiple coded values, specifying one or more distinct colors that approximate of the color(s) of distinct areas of the solid dosage form, such as the different sides of a tablet or one-part capsule, or the different halves of a two-part capsule.  Bands on banded capsules, regardless of the color, are not considered when assigning an SPLCOLOR. Imprints on the dosage form, regardless of their color are not considered when assigning an SPLCOLOR. If more than one color exists on a particular side or half, then the most predominant color on that side or half is recorded.  If the gelatin capsule shell is colorless and transparent, use the predominant color of the contents that appears through the colorless and transparent capsule shell. Colors can include: Black;Gray;White;Red;Pink;Purple;Green;Yellow;Orange;Brown;Blue;Turquoise."></definition>
@@ -51932,10 +51932,10 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="SPLIMPRINT"></code>
        <display value="imprint"></display>
-       <definition value="Definition:  A characteristic of an oral solid dosage form of a medicinal product, specifying the alphanumeric text that appears on the solid dosage form, including text that is embossed, debossed, engraved or printed with ink. The presence of other non-textual distinguishing marks or symbols is recorded by SPLSYMBOL.
+       <definition value="Definition:  A characteristic of an oral solid dosage form of a medicinal product, specifying the alphanumeric text that appears on the solid dosage form, including text that is embossed, debossed, engraved or printed with ink. The presence of other non-textual distinguishing marks or symbols is recorded by SPLSYMBOL.
 
         
-         Examples: Included in SPLIMPRINT are alphanumeric text that appears on the bands of banded capsules and logos and other symbols that can be interpreted as letters or numbers.
+         Examples: Included in SPLIMPRINT are alphanumeric text that appears on the bands of banded capsules and logos and other symbols that can be interpreted as letters or numbers.
 
         
          Constraints: The Observation.value must be of type Character String (ST). Excluded from SPLIMPRINT are internal and external cut-outs in the form of alphanumeric text and the letter 'R' with a circle around it (when referring to a registered trademark) and the letters 'TM' (when referring to a 'trade mark').  To record text, begin on either side or part of the dosage form. Start at the top left and progress as one would normally read a book.  Enter a semicolon to show separation between words or line divisions."></definition>
@@ -51943,10 +51943,10 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="SPLSCORING"></code>
        <display value="scoring"></display>
-       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the number of equal pieces that the solid dosage form can be divided into using score line(s). 
+       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the number of equal pieces that the solid dosage form can be divided into using score line(s). 
 
         
-         Example: One score line creating two equal pieces is given a value of 2, two parallel score lines creating three equal pieces is given a value of 3.
+         Example: One score line creating two equal pieces is given a value of 2, two parallel score lines creating three equal pieces is given a value of 3.
 
         
          Constraints: Whether three parallel score lines create four equal pieces or two intersecting score lines create two equal pieces using one score line and four equal pieces using both score lines, both have the scoring value of 4. Solid dosage forms that are not scored are given a value of 1. Solid dosage forms that can only be divided into unequal pieces are given a null-value with nullFlavor other (OTH)."></definition>
@@ -51959,7 +51959,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="SPLSIZE"></code>
        <display value="size"></display>
-       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the longest single dimension of the solid dosage form as a physical quantity in the dimension of length (e.g., 3 mm). The length is should be specified in millimeters and should be rounded to the nearest whole millimeter.
+       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the longest single dimension of the solid dosage form as a physical quantity in the dimension of length (e.g., 3 mm). The length is should be specified in millimeters and should be rounded to the nearest whole millimeter.
 
         
          Example: SPLSIZE for a rectangular shaped tablet is the length and SPLSIZE for a round shaped tablet is the diameter."></definition>
@@ -51967,10 +51967,10 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="SPLSYMBOL"></code>
        <display value="symbol"></display>
-       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, to describe whether or not the medicinal product has a mark or symbol appearing on it for easy and definite recognition.  Score lines, letters, numbers, and internal and external cut-outs are not considered marks or symbols. See SPLSCORING and SPLIMPRINT for these characteristics.
+       <definition value="Definition: A characteristic of an oral solid dosage form of a medicinal product, to describe whether or not the medicinal product has a mark or symbol appearing on it for easy and definite recognition.  Score lines, letters, numbers, and internal and external cut-outs are not considered marks or symbols. See SPLSCORING and SPLIMPRINT for these characteristics.
 
         
-         Constraints: The Observation.value must be a Boolean (BL) with &lt;u&gt;true&lt;/u&gt; indicating the presence and &lt;u&gt;false&lt;/u&gt; for the absence of marks or symbols.
+         Constraints: The Observation.value must be a Boolean (BL) with &lt;u&gt;true&lt;/u&gt; indicating the presence and &lt;u&gt;false&lt;/u&gt; for the absence of marks or symbols.
 
         
          Example:"></definition>
@@ -52177,7 +52177,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="MSRAGG"></code>
        <display value="rate aggregation"></display>
-       <definition value="Describes how to combine information calculated based on logic in each of several populations into one summarized result. It can also be used to describe how to risk adjust the data based on supplemental data elements described in the eMeasure. (e.g., pneumonia hospital measures antibiotic selection in the ICU versus non-ICU and then the roll-up of the two). 
+       <definition value="Describes how to combine information calculated based on logic in each of several populations into one summarized result. It can also be used to describe how to risk adjust the data based on supplemental data elements described in the eMeasure. (e.g., pneumonia hospital measures antibiotic selection in the ICU versus non-ICU and then the roll-up of the two). 
 
         
          Open Issue: The description does NOT align well with the definition used in the HQMF specfication; correct the MSGAGG definition, and the possible distinction of MSRAGG as a child of AGGREGATE."></definition>
@@ -52211,7 +52211,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="MSRSET"></code>
        <display value="health quality measure care setting"></display>
-       <definition value="Location(s) in which care being measured is rendered
+       <definition value="Location(s) in which care being measured is rendered
 
         Usage Note: MSRSET is used rather than RoleCode because the setting applies to what is being measured, as opposed to participating directly in the health quality measure documantion itself)."></definition>
       </concept>
@@ -52355,7 +52355,7 @@ Information handling protocols based on organizational policies related to sexua
       <concept>
        <code value="DENEXCEP"></code>
        <display value="denominator exceptions"></display>
-       <definition value="Criteria which specify the removal of a subject, procedure or unit of measurement from the denominator, only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories:
+       <definition value="Criteria which specify the removal of a subject, procedure or unit of measurement from the denominator, only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories:
 
         
          Medical reasons
@@ -52431,7 +52431,7 @@ the measure population as a narrative description (e.g., all patients seen in th
      <concept>
       <code value="CDIO"></code>
       <display value="case disease imported observation"></display>
-      <definition value="An observation that states whether the disease was likely acquired outside the jurisdiction of observation, and if so, the nature of the inter-jurisdictional relationship.
+      <definition value="An observation that states whether the disease was likely acquired outside the jurisdiction of observation, and if so, the nature of the inter-jurisdictional relationship.
 
         
          OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it."></definition>
@@ -52444,7 +52444,7 @@ the measure population as a narrative description (e.g., all patients seen in th
      <concept>
       <code value="CTMO"></code>
       <display value="case transmission mode observation"></display>
-      <definition value="An observation that states the mechanism by which disease was acquired by the living subject involved in the public health case.
+      <definition value="An observation that states the mechanism by which disease was acquired by the living subject involved in the public health case.
 
         
          OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it."></definition>
@@ -52487,7 +52487,7 @@ the measure population as a narrative description (e.g., all patients seen in th
      <concept>
       <code value="ISSUE"></code>
       <display value="detected issue"></display>
-      <definition value="There is a clinical issue for the therapy that makes continuation of the therapy inappropriate.
+      <definition value="There is a clinical issue for the therapy that makes continuation of the therapy inappropriate.
 
         
          Open Issue: The definition of this code does not correctly represent the concept space of its specializations (children)"></definition>
@@ -52725,7 +52725,7 @@ the measure population as a narrative description (e.g., all patients seen in th
           <concept>
            <code value="CREACT"></code>
            <display value="common reaction alert"></display>
-           <definition value="Description:Proposed therapy may be inappropriate or contraindicated because of a common but non-patient specific reaction to the product.
+           <definition value="Description:Proposed therapy may be inappropriate or contraindicated because of a common but non-patient specific reaction to the product.
 
         
          Example:There is no record of a specific sensitivity for the patient, but the presence of the sensitivity is common and therefore caution is warranted."></definition>
@@ -53407,10 +53407,10 @@ the measure population as a narrative description (e.g., all patients seen in th
     <concept>
      <code value="SECOBS"></code>
      <display value="SecurityObservationType"></display>
-     <definition value="An observation identifying security metadata about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Security metadata are used to name security labels.  
+     <definition value="An observation identifying security metadata about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Security metadata are used to name security labels.  
 
         
-         Rationale: According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator's clearance to the target's security label.  All of the following must be true for authorization to be granted:
+         Rationale: According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator's clearance to the target's security label.  All of the following must be true for authorization to be granted:
 
         
          The security policy identifiers shall be identical
@@ -53418,7 +53418,7 @@ the measure population as a narrative description (e.g., all patients seen in th
          For each security category in the target label, there shall be a security category of the same type in the initiator's clearance and the initiator's classification level shall dominate that of the target.
         
         
-         Examples: SecurityObservationType  security label fields include:
+         Examples: SecurityObservationType  security label fields include:
 
         
          Confidentiality classification
@@ -53436,13 +53436,13 @@ the measure population as a narrative description (e.g., all patients seen in th
      <concept>
       <code value="SECCATOBS"></code>
       <display value="security category observation"></display>
-      <definition value="Type of security metadata observation made about the category of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security category metadata is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: &quot;A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone.&quot;
+      <definition value="Type of security metadata observation made about the category of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security category metadata is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: &quot;A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone.&quot;
 
         
-         Rationale: A security category observation supports requirement to specify the type of IT resource to facilitate application of appropriate levels of information security according to a range of levels of impact or consequences that might result from the unauthorized disclosure, modification, or use of the information or information system.  A resource is assigned to a specific category of information (e.g., privacy, medical, proprietary, financial, investigative, contractor sensitive, security management) defined by an organization or in some instances, by a specific law, Executive Order, directive, policy, or regulation. [FIPS 199]
+         Rationale: A security category observation supports requirement to specify the type of IT resource to facilitate application of appropriate levels of information security according to a range of levels of impact or consequences that might result from the unauthorized disclosure, modification, or use of the information or information system.  A resource is assigned to a specific category of information (e.g., privacy, medical, proprietary, financial, investigative, contractor sensitive, security management) defined by an organization or in some instances, by a specific law, Executive Order, directive, policy, or regulation. [FIPS 199]
 
         
-         Examples: Types of security categories include:
+         Examples: Types of security categories include:
 
         
          Compartment:  A division of data into isolated blocks with separate security controls for the purpose of reducing risk. (ISO 2382-8).  A security label tag that &quot;segments&quot; an IT resource by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Classification System)  
@@ -53451,13 +53451,13 @@ the measure population as a narrative description (e.g., all patients seen in th
      <concept>
       <code value="SECCLASSOBS"></code>
       <display value="security classification observation"></display>
-      <definition value="Type of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: &quot;The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection.&quot;  Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure.
+      <definition value="Type of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: &quot;The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection.&quot;  Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure.
 
         
-         Rationale: A security classification observation may indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for ascribing the SecurityClassificationObservationValue.  This supports the business requirement for increasing or decreasing the level of confidentiality (classification or declassification) based on parameters beyond the original assignment of an Act or Role confidentiality.
+         Rationale: A security classification observation may indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for ascribing the SecurityClassificationObservationValue.  This supports the business requirement for increasing or decreasing the level of confidentiality (classification or declassification) based on parameters beyond the original assignment of an Act or Role confidentiality.
 
         
-         Examples: Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal.  Intelligence community examples include top secret, secret, and confidential.
+         Examples: Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal.  Intelligence community examples include top secret, secret, and confidential.
 
         
          Usage Note: Security classification observation type codes designate security label field types, which are valued with an applicable SecurityClassificationObservationValue code as the &quot;security label tag&quot;."></definition>
@@ -53465,13 +53465,13 @@ the measure population as a narrative description (e.g., all patients seen in th
      <concept>
       <code value="SECCONOBS"></code>
       <display value="security control observation"></display>
-      <definition value="Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Security control metadata convey instructions to users and receivers for secure distribution, transmission, and storage; dictate obligations or mandated actions; specify any action prohibited by refrain policy such as dissemination controls; and stipulate the permissible purpose of use of an IT resource.  
+      <definition value="Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Security control metadata convey instructions to users and receivers for secure distribution, transmission, and storage; dictate obligations or mandated actions; specify any action prohibited by refrain policy such as dissemination controls; and stipulate the permissible purpose of use of an IT resource.  
 
         
-         Rationale: A security control observation supports requirement to specify applicable management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. [FIPS 199]
+         Rationale: A security control observation supports requirement to specify applicable management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. [FIPS 199]
 
         
-         Examples: Types of security control metadata include: 
+         Examples: Types of security control metadata include: 
 
         
          handling caveats
@@ -53483,13 +53483,13 @@ the measure population as a narrative description (e.g., all patients seen in th
      <concept>
       <code value="SECINTOBS"></code>
       <display value="security integrity observation"></display>
-      <definition value="Type of security metadata observation made about the integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.
+      <definition value="Type of security metadata observation made about the integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.
 
         
-         Rationale: A security integrity observation supports the requirement to guard against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. (44 U.S.C., SEC. 3542)
+         Rationale: A security integrity observation supports the requirement to guard against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. (44 U.S.C., SEC. 3542)
 
         
-         Examples: Types of security integrity metadata include: 
+         Examples: Types of security integrity metadata include: 
 
         
          Integrity status, which indicates the completeness or workflow status of an IT resource (data, information object, service, or system capability)
@@ -53501,10 +53501,10 @@ the measure population as a narrative description (e.g., all patients seen in th
       <concept>
        <code value="SECALTINTOBS"></code>
        <display value="security alteration integrity observation"></display>
-       <definition value="Type of security metadata observation made about the alteration integrity of an IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformations of the resource.
+       <definition value="Type of security metadata observation made about the alteration integrity of an IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformations of the resource.
 
         
-         Examples: Types of security alteration integrity observation metadata, which may value the observation with a code used to indicate the mechanism used for authorized transformation of an IT resource, including: 
+         Examples: Types of security alteration integrity observation metadata, which may value the observation with a code used to indicate the mechanism used for authorized transformation of an IT resource, including: 
 
         
          translation
@@ -53518,7 +53518,7 @@ the measure population as a narrative description (e.g., all patients seen in th
       <concept>
        <code value="SECDATINTOBS"></code>
        <display value="security data integrity observation"></display>
-       <definition value="Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency.  Data integrity is defined by ISO 22600-23.3.21 as: &quot;The property that data has not been altered or destroyed in an unauthorized manner&quot;, and by ISO/IEC 2382-8:  The property of data whose accuracy and consistency are preserved regardless of changes made.&quot;
+       <definition value="Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency.  Data integrity is defined by ISO 22600-23.3.21 as: &quot;The property that data has not been altered or destroyed in an unauthorized manner&quot;, and by ISO/IEC 2382-8:  The property of data whose accuracy and consistency are preserved regardless of changes made.&quot;
 
         
          Examples: Types of security data integrity observation metadata, which may value the observation, include cryptographic hash function and digital signature."></definition>
@@ -53526,10 +53526,10 @@ the measure population as a narrative description (e.g., all patients seen in th
       <concept>
        <code value="SECINTCONOBS"></code>
        <display value="security integrity confidence observation"></display>
-       <definition value="Type of security metadata observation made about the integrity confidence of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.
+       <definition value="Type of security metadata observation made about the integrity confidence of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.
 
         
-         Examples: Types of security integrity confidence observation metadata, which may value the observation, include highly reliable, uncertain reliability, and not reliable.
+         Examples: Types of security integrity confidence observation metadata, which may value the observation, include highly reliable, uncertain reliability, and not reliable.
 
         
          Usage Note: A security integrity confidence observation on an Act may indicate that a valued Act.uncertaintycode attribute has been overridden by the entity responsible for ascribing the SecurityIntegrityConfidenceObservationValue.  This supports the business requirements for increasing or decreasing the assessment of the reliability or trustworthiness of an IT resource based on parameters beyond the original assignment of an Act statement level of uncertainty."></definition>
@@ -53537,10 +53537,10 @@ the measure population as a narrative description (e.g., all patients seen in th
       <concept>
        <code value="SECINTPRVOBS"></code>
        <display value="security integrity provenance observation"></display>
-       <definition value="Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness of an IT resource in terms of workflow status such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure.  Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness.
+       <definition value="Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness of an IT resource in terms of workflow status such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure.  Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness.
 
         
-         Examples: Types of security integrity provenance observation metadata, which may value the observation about an IT resource, include: 
+         Examples: Types of security integrity provenance observation metadata, which may value the observation about an IT resource, include: 
 
         
          completeness or workflow status, such as authentication
@@ -53554,10 +53554,10 @@ the measure population as a narrative description (e.g., all patients seen in th
        <concept>
         <code value="SECINTPRVABOBS"></code>
         <display value="security integrity provenance asserted by observation"></display>
-        <definition value="Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource.  The asserting entity may not be the original informant about the resource.
+        <definition value="Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource.  The asserting entity may not be the original informant about the resource.
 
         
-         Examples: Types of security integrity provenance asserted by observation metadata, which may value the observation, including: 
+         Examples: Types of security integrity provenance asserted by observation metadata, which may value the observation, including: 
 
         
          assertions about an IT resource by a patient
@@ -53567,10 +53567,10 @@ the measure population as a narrative description (e.g., all patients seen in th
        <concept>
         <code value="SECINTPRVRBOBS"></code>
         <display value="security integrity provenance reported by observation"></display>
-        <definition value="Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource.  The reporting entity may not be the original author of the resource.
+        <definition value="Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource.  The reporting entity may not be the original author of the resource.
 
         
-         Examples: Types of security integrity provenance reported by observation metadata, which may value the observation, include: 
+         Examples: Types of security integrity provenance reported by observation metadata, which may value the observation, include: 
 
         
          reports about an IT resource by a patient
@@ -53581,7 +53581,7 @@ the measure population as a narrative description (e.g., all patients seen in th
       <concept>
        <code value="SECINTSTOBS"></code>
        <display value="security integrity status observation"></display>
-       <definition value="Type of security metadata observation made about the integrity status of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Indicates the completeness of an IT resource in terms of workflow status, which may impact users that are authorized to access and use the resource.
+       <definition value="Type of security metadata observation made about the integrity status of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.  Indicates the completeness of an IT resource in terms of workflow status, which may impact users that are authorized to access and use the resource.
 
         
          Examples: Types of security integrity status observation metadata, which may value the observation, include codes from the HL7 DocumentCompletion code system such as legally authenticated, in progress, and incomplete."></definition>
@@ -53608,11 +53608,11 @@ the measure population as a narrative description (e.g., all patients seen in th
       <concept>
        <code value="TRSTCERTOBS"></code>
        <display value="trust certificate observation"></display>
-       <definition value="Type of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1]
+       <definition value="Type of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1]
 
         
          For example,
-        
+        
 
         
          A Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. For example, a particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.
@@ -53638,7 +53638,7 @@ the measure population as a narrative description (e.g., all patients seen in th
     <concept>
      <code value="SUBSIDFFS"></code>
      <display value="subsidized fee for service program"></display>
-     <definition value="Definition: A government health program that provides coverage on a fee for service basis for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds.
+     <definition value="Definition: A government health program that provides coverage on a fee for service basis for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds.
 
         
          Discussion: The structure and business processes for underwriting and administering a subsidized fee for service program is further specified by the Underwriter and Payer Role.class and Role.code."></definition>
@@ -53735,7 +53735,7 @@ the measure population as a narrative description (e.g., all patients seen in th
   <fullUrl value="http://hl7.org/fhir/v3/TableRules"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TableRules"></id>
+    <id value="v3-TableRules"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -53799,7 +53799,7 @@ the measure population as a narrative description (e.g., all patients seen in th
   <fullUrl value="http://hl7.org/fhir/v3/CodingRationale"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="CodingRationale"></id>
+    <id value="v3-CodingRationale"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
@@ -53896,7 +53896,7 @@ the measure population as a narrative description (e.g., all patients seen in th
   <fullUrl value="http://hl7.org/fhir/v3/TableFrame"></fullUrl>
   <resource>
    <CodeSystem xmlns="http://hl7.org/fhir">
-    <id value="TableFrame"></id>
+    <id value="v3-TableFrame"></id>
     <meta>
      <lastUpdated value="2016-11-11T00:00:00.000+11:00"></lastUpdated>
     </meta>
diff --git a/hapi-fhir-validation/src/test/java/org/hl7/fhir/dstu3/hapi/validation/FhirInstanceValidatorDstu3Test.java b/hapi-fhir-validation/src/test/java/org/hl7/fhir/dstu3/hapi/validation/FhirInstanceValidatorDstu3Test.java
index 5b939bbab29..75405d94a95 100644
--- a/hapi-fhir-validation/src/test/java/org/hl7/fhir/dstu3/hapi/validation/FhirInstanceValidatorDstu3Test.java
+++ b/hapi-fhir-validation/src/test/java/org/hl7/fhir/dstu3/hapi/validation/FhirInstanceValidatorDstu3Test.java
@@ -667,8 +667,6 @@ public class FhirInstanceValidatorDstu3Test {
 					} else if (t.getMessage().contains("ValueSet as a URI SHALL start with http:// or https:// or urn:")) {
 						// Some DSTU3 structures have missing binding information
 						return false;
-					} else if (t.getMessage().contains("The valueSet reference http://www.rfc-editor.org/bcp/bcp13.txt on element")) {
-						return false;
 					} else if (t.getMessage().contains("The Unicode sequence has unterminated bi-di control characters")) {
 						// Some DSTU3 structures contain bi-di control characters, and a check for this was added recently.
 						return false;
@@ -678,7 +676,14 @@ public class FhirInstanceValidatorDstu3Test {
 					} else if (t.getMessage().startsWith("value should not start or finish with whitespace") && t.getMessage().endsWith("\\u00a0'")) {
 						// Some DSTU3 messages end with a unicode Non-breaking space character
 						return false;
-					} else {
+					}  else if (t.getMessage().contains("Found # expecting a token name")) {
+						// Some DSTU3 messages contain incomplete encoding for single quotes (#39 vs &#39)
+						return false;
+					} else if (t.getMessage().contains("sdf-15") && t.getMessage().contains("The name 'kind' is not valid for any of the possible types")) {
+						// Find constraint sdf-15 fails with stricter core validation.
+						return false;
+					}
+					else {
 						return true;
 					}
 				})
diff --git a/hapi-tinder-plugin/src/main/java/ca/uhn/fhir/tinder/ResourceMinimizerMojo.java b/hapi-tinder-plugin/src/main/java/ca/uhn/fhir/tinder/ResourceMinimizerMojo.java
index 57ce394f3d4..3824a76e37a 100644
--- a/hapi-tinder-plugin/src/main/java/ca/uhn/fhir/tinder/ResourceMinimizerMojo.java
+++ b/hapi-tinder-plugin/src/main/java/ca/uhn/fhir/tinder/ResourceMinimizerMojo.java
@@ -198,6 +198,7 @@ public class ResourceMinimizerMojo extends AbstractMojo {
 		//		byteCount += m.getByteCount();
 		//		fileCount += m.getFileCount();
 		//
+
 		//		m = new ResourceMinimizerMojo();
 		//		m.myCtx = ctxDstu3;
 		//		m.targetDirectory = new