<StructureDefinition xmlns="http://hl7.org/fhir">
  <url value="http://telus.com/fhir/patientChart/StructureDefinition/profile-clinical-impression" />
  <name value="ClinicalImpressionFuture" />
  <status value="draft" />
  <description value="NOT TO BE USED INITIALLY" />
  <fhirVersion value="4.0.1" />
  <kind value="resource" />
  <abstract value="false" />
  <type value="ClinicalImpression" />
  <baseDefinition value="http://hl7.org/fhir/StructureDefinition/ClinicalImpression" />
  <derivation value="constraint" />
  <differential>
    <element id="ClinicalImpression.id">
      <path value="ClinicalImpression.id" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.meta">
      <path value="ClinicalImpression.meta" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.meta.lastUpdated">
      <path value="ClinicalImpression.meta.lastUpdated" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.meta.source">
      <path value="ClinicalImpression.meta.source" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.meta.profile">
      <path value="ClinicalImpression.meta.profile" />
      <max value="1" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.text">
      <path value="ClinicalImpression.text" />
      <comment value="Conformance Rule:     This must be formatted, as closely as possible what was presented to the user in the originating system and must include all clinical data.    &#xD;&#xA;&#xD;&#xA;Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded information is added later." />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.status">
      <path value="ClinicalImpression.status" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.subject">
      <path value="ClinicalImpression.subject" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.subject.reference">
      <path value="ClinicalImpression.subject.reference" />
      <min value="1" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.subject.display">
      <path value="ClinicalImpression.subject.display" />
      <comment value="Usage Note:   This should contain the name of the Patient, which can then be used in narrative where applicable&#xD;&#xA;&#xD;&#xA;This is generally not the same as the Resource.text of the referenced resource.  The purpose is to identify what's being referenced, not to fully describe it." />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.effective[x]">
      <path value="ClinicalImpression.effective[x]" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.date">
      <path value="ClinicalImpression.date" />
      <min value="1" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.problem">
      <path value="ClinicalImpression.problem" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.problem.reference">
      <path value="ClinicalImpression.problem.reference" />
      <comment value="Usage Note:  This will be a reference to the condition resource&#xD;&#xA;&#xD;&#xA;Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries.   Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure &quot;/[type]/[id]&quot; then it should be assumed that the reference is to a FHIR RESTful server." />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.problem.display">
      <path value="ClinicalImpression.problem.display" />
      <comment value="Usage Note:  This is a user-friendly textual representation of the reference that should be used in the narrative&#xD;&#xA;&#xD;&#xA;This is generally not the same as the Resource.text of the referenced resource.  The purpose is to identify what's being referenced, not to fully describe it." />
      <min value="1" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.investigation">
      <path value="ClinicalImpression.investigation" />
      <comment value="MA - may be able to support - text only? -  Subjective, Objective" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.investigation.code.text">
      <path value="ClinicalImpression.investigation.code.text" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.investigation.item">
      <path value="ClinicalImpression.investigation.item" />
      <comment value="Usage; MA may be able to reference an observation; not great value; ; we will be exporting the results of investigation which is much more valuable&#xD;&#xA;&#xD;&#xA;Most investigations are observations of one kind or another but some other specific types of data collection resources can also be used." />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.investigation.item.reference">
      <path value="ClinicalImpression.investigation.item.reference" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.investigation.item.display">
      <path value="ClinicalImpression.investigation.item.display" />
      <mustSupport value="true" />
    </element>
    <element id="ClinicalImpression.summary">
      <path value="ClinicalImpression.summary" />
      <min value="1" />
      <mustSupport value="true" />
    </element>
  </differential>
</StructureDefinition>