StructureDefinition: C-CDA on FHIR History and Physical - XML

C-CDA on FHIR History and Physical

<StructureDefinition xmlns="http://hl7.org/fhir">
  <id value="ccda-history-and-physical-composition"/>
  <url value="http://hl7.org/fhir/StructureDefinition/ccda-history-and-physical-composition"/>
  <name value="C-CDA on FHIR History and Physical"/>
  <status value="draft"/>
  <contact>
    <name value="Sarah Gaunt"/>
    <telecom>
      <system value="phone"/>
      <value value="+6 141-029-2506"/>
      <use value="work"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="sarah.gaunt@lantanagroup.com"/>
      <use value="work"/>
    </telecom>
  </contact>
  <date value="2016-03-31T08:01:25+11:00"/>
  <description value="A History and Physical (H&amp;P) note is a medical report that documents the current and
   past conditions of the patient. It contains essential information that helps determine
   an individual's health status.    The first portion of the report is a current collection
   of organized information unique to an individual. This is typically supplied by the patient
   or the caregiver, concerning the current medical problem or the reason for the patient
   encounter. This information is followed by a description of any past or ongoing medical
   issues, including current medications and allergies. Information is also obtained about
   the patient's lifestyle, habits, and diseases among family members. The next portion of
   the report contains information obtained by physically examining the patient and gathering
   diagnostic information in the form of laboratory tests, imaging, or other diagnostic procedures.
     The report ends with the clinician's assessment of the patient's situation and the intended
   plan to address those issues.   A History and Physical Examination is required upon hospital
   admission as well as before operative procedures. An initial evaluation in an ambulatory
   setting is often documented in the form of an H&amp;P note.  The H&amp;P Note recommends
   use of a single document type code, 34117-2 display: History and physical note"/>
  <fhirVersion value="1.4.0"/>
  <kind value="resource"/>
  <abstract value="false"/>
  <baseType value="Composition"/>
  <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Composition"/>
  <derivation value="constraint"/>
  <snapshot>
    <element>
      <path value="Composition"/>
      <short value="A set of resources composed into a single coherent clinical statement with clinical attestation"/>
      <definition value="A set of healthcare-related information that is assembled together into a single logical
       document that provides a single coherent statement of meaning, establishes its own context
       and that has clinical attestation with regard to who is making the statement. While a
       Composition defines the structure, it does not actually contain the content: rather the
       full content of a document is contained in a Bundle, of which the Composition is the first
       resource contained."/>
      <comments value="While the focus of this specification is on patient-specific clinical statements, this
       resource can also apply to other healthcare-related statements such as study protocol
       designs, healthcare invoices and other activities that are not necessarily patient-specific
       or clinical."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="DomainResource"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value="ClinicalDocument"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="Document[classCode=&quot;DOC&quot; and moodCode=&quot;EVN&quot; and isNormalAct()]"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="infrastructure.documents"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.id"/>
      <short value="Logical id of this artifact"/>
      <definition value="The logical id of the resource, as used in the URL for the resource. Once assigned, this
       value never changes."/>
      <comments value="The only time that a resource does not have an id is when it is being submitted to the
       server using a create operation. Bundles always have an id, though it is usually a generated
       UUID."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Resource.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <isSummary value="true"/>
    </element>
    <element>
      <path value="Composition.meta"/>
      <short value="Metadata about the resource"/>
      <definition value="The metadata about the resource. This is content that is maintained by the infrastructure.
       Changes to the content may not always be associated with version changes to the resource."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Resource.meta"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Meta"/>
      </type>
      <isSummary value="true"/>
    </element>
    <element>
      <path value="Composition.implicitRules"/>
      <short value="A set of rules under which this content was created"/>
      <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."/>
      <comments 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 as much as possible."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Resource.implicitRules"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="uri"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
    </element>
    <element>
      <path value="Composition.language"/>
      <short value="Language of the resource content"/>
      <definition value="The base language in which the resource is written."/>
      <comments value="Language is provided to support indexing and accessibility (typically, services such as
       text to speech use the language tag). The html language tag in the narrative applies 
       to the narrative. The language tag on the resource may be used to specify the language
       of other presentations generated from the data in the resource  Not all the content has
       to be in the base language. The Resource.language should not be assumed to apply to the
       narrative automatically. If a language is specified, it should it also be specified on
       the div element in the html (see rules in HTML5 for information about the relationship
       between xml:lang and the html lang attribute)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Resource.language"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <binding>
        <strength value="required"/>
        <description value="A human language."/>
        <valueSetUri value="http://tools.ietf.org/html/bcp47"/>
      </binding>
    </element>
    <element>
      <path value="Composition.text"/>
      <short value="Text summary of the resource, for human interpretation"/>
      <definition value="A human-readable narrative that contains a summary of the resource, and may be used to
       represent the content of the resource to a human. The narrative need not encode all the
       structured data, but is required to contain sufficient detail to make it &quot;clinically
       safe&quot; for a human to just read the narrative. Resource definitions may define what
       content should be represented in the narrative to ensure clinical safety."/>
      <comments value="Contained resources do not have narrative. Resources that are not contained SHOULD have
       a narrative."/>
      <alias value="narrative"/>
      <alias value="html"/>
      <alias value="xhtml"/>
      <alias value="display"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="DomainResource.text"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="dom-1"/>
      <mapping>
        <identity value="rim"/>
        <map value="Act.text?"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.contained"/>
      <short value="Contained, inline Resources"/>
      <definition value="These resources do not have an independent existence apart from the resource that contains
       them - they cannot be identified independently, and nor can they have their own independent
       transaction scope."/>
      <comments value="This should never be done when the content can be identified properly, as once identification
       is lost, it is extremely difficult (and context dependent) to restore it again."/>
      <alias value="inline resources"/>
      <alias value="anonymous resources"/>
      <alias value="contained resources"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="DomainResource.contained"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Resource"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the resource. In order to make the use of extensions safe and manageable, there is
       a strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="DomainResource.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the resource, and that modifies the understanding of the element that contains it.
       Usually modifier elements provide negation or qualification. In order to make the use
       of extensions safe and manageable, there is a strict set of governance applied to the
       definition and use of extensions. Though any implementer is allowed to define an extension,
       there is a set of requirements that SHALL be met as part of the definition of the extension.
       Applications processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="DomainResource.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.identifier"/>
      <short value="Logical identifier of composition (version-independent)"/>
      <definition value="Logical identifier for the composition, assigned when created. This identifier stays constant
       as the composition is changed over time."/>
      <comments value="See discussion in resource definition for how these relate."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.identifier"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Identifier"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".setId"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="Document.id / Document.setId"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="id"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.date"/>
      <short value="Composition editing time"/>
      <definition value="The composition editing time, when the composition was last logically changed by the author."/>
      <comments value="The Last Modified Date on the composition may be after the date of the document was attested
       without being changed."/>
      <requirements value="dateTime is used for tracking, organizing versions and searching."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.date"/>
        <min value="1"/>
        <max value="1"/>
      </base>
      <type>
        <code value="dateTime"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".effectiveTime"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".effectiveTime[type=&quot;TS&quot;]"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="when.done"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.type"/>
      <label value="History and Physical"/>
      <short value="type"/>
      <definition value="SHALL contain exactly one [1..1] type, which SHALL be selected from ValueSet HPDocumentType
       urn:oid:2.16.840.1.113883.1.11.20.22 DYNAMIC (CONF:2219-1820)."/>
      <comments value="For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation
       guides will require a specific LOINC code, or use LOINC as an extensible binding."/>
      <requirements value="Key metadata element describing the composition, used in searching/filtering."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.type"/>
        <min value="1"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/2.16.840.1.113883.1.11.20.22"/>
          <display value="HPDocumentType"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.class"/>
      <short value="Categorization of Composition"/>
      <definition value="A categorization for the type of the composition - helps for indexing and searching. This
       may be implied by or derived from the code specified in the Composition Type."/>
      <comments value="This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_
      Documents_(MHD))."/>
      <requirements value="Helps humans to assess whether the composition is of interest when viewing an index of
       compositions or documents."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.class"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <isSummary value="true"/>
      <binding>
        <strength value="example"/>
        <description value="High-level kind of a clinical document at a macro level."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-classcodes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=&quot;COMP].target[classCode=&quot;LIST&quot;, moodCode=&quot;EVN&quo
        t;].code"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.title"/>
      <short value="Human Readable name/title"/>
      <definition value="Official human-readable label for the composition."/>
      <comments value="For many compositions, the title is the same as the text or a display name of Composition.type
       (e.g. a &quot;consultation&quot; or &quot;progress note&quot;). Note that CDA does not
       make title mandatory, but there are no known cases where it is useful for title to be
       omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial
       use period."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.title"/>
        <min value="1"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.status"/>
      <short value="preliminary | final | amended | entered-in-error"/>
      <definition value="The workflow/clinical status of this composition. The status is a marker for the clinical
       standing of the document."/>
      <comments 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;withdrawn&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."/>
      <requirements value="Need to be able to mark interim, amended, or withdrawn compositions or documents."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.status"/>
        <min value="1"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The workflow/clinical status of the composition."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/composition-status"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="interim: .completionCode=&quot;IN&quot; &amp; ./statusCode[isNormalDatatype()]=&quot;active&quot;;
          final: .completionCode=&quot;AU&quot; &amp;&amp;  ./statusCode[isNormalDatatype()]=&quot;complete&q
        uot; and not(./inboundRelationship[typeCode=&quot;SUBJ&quot; and isNormalActRelationship()]/source[su
        bsumesCode(&quot;ActClass#CACT&quot;) and moodCode=&quot;EVN&quot; and domainMember(&quot;ReviseCompo
        sition&quot;, code) and isNormalAct()]);  amended: .completionCode=&quot;AU&quot; &amp;&amp;
          ./statusCode[isNormalDatatype()]=&quot;complete&quot; and ./inboundRelationship[typeCode=&quot;SUBJ
        &quot; and isNormalActRelationship()]/source[subsumesCode(&quot;ActClass#CACT&quot;) and
         moodCode=&quot;EVN&quot; and domainMember(&quot;ReviseComposition&quot;, code) and isNormalAct()
         and statusCode=&quot;completed&quot;];  withdrawn : .completionCode=NI &amp;&amp;  ./statusCode[isNo
        rmalDatatype()]=&quot;obsolete&quot;"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="status"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.confidentiality"/>
      <short value="As defined by affinity domain"/>
      <definition value="The code specifying the level of confidentiality of the Composition."/>
      <comments 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)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.confidentiality"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="Codes specifying the level of confidentiality of the composition."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/v3-Confidentiality"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".confidentialityCode"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".confidentialityCode"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.subject"/>
      <short value="Who and/or what the composition is about"/>
      <definition value="Who or what the composition is about. The composition can be about a person, (patient
       or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such
       as a document about a herd of livestock, or a set of patients that share a common exposure)."/>
      <comments value="For clinical documents, this is usually the patient."/>
      <requirements value="Essential metadata for searching for the composition. Identifies who and/or what the composition/doc
      ument is about."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.subject"/>
        <min value="1"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".recordTarget"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".participation[typeCode=&quot;SBJ&quot;].role[typeCode=&quot;PAT&quot;]"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="who.focus"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.author"/>
      <short value="Who and/or what authored the composition"/>
      <definition value="Identifies who is responsible for the information in the composition, not necessarily
       who typed it in."/>
      <requirements value="Identifies who is responsible for the content."/>
      <min value="1"/>
      <max value="*"/>
      <base>
        <path value="Composition.author"/>
        <min value="1"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Practitioner"/>
      </type>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Device"/>
      </type>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Patient"/>
      </type>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/RelatedPerson"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".author.assignedAuthor"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".participation[typeCode=&quot;AUT&quot;].role[classCode=&quot;ASSIGNED&quot;]"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="who.author"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.attester"/>
      <short value="Attests to accuracy of composition"/>
      <definition value="A participant who has attested to the accuracy of the composition/document."/>
      <comments value="Only list each attester once."/>
      <requirements value="Identifies responsibility for the accuracy of the composition content."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.attester"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".authenticator/.legalAuthenticator"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".participation[typeCode=&quot;AUTHEN&quot;].role[classCode=&quot;ASSIGNED&quot;]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.attester.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.attester.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.attester.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.attester.mode"/>
      <short value="personal | professional | legal | official"/>
      <definition value="The type of attestation the authenticator offers."/>
      <comments value="Use more than one code where a single attester has more than one mode (professional and
       legal are often paired)."/>
      <requirements value="Indicates the level of authority of the attestation."/>
      <min value="1"/>
      <max value="*"/>
      <base>
        <path value="Composition.attester.mode"/>
        <min value="1"/>
        <max value="*"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The way in which a person authenticated a composition."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/composition-attestation-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="implied by .authenticator/.legalAuthenticator"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="unique(./modeCode)"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.attester.time"/>
      <short value="When composition attested"/>
      <definition value="When composition was attested by the party."/>
      <requirements value="Identifies when the information in the composition was deemed accurate.  (Things may have
       changed since then.)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.attester.time"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="dateTime"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".authenticator.time"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./time[type=&quot;TS&quot; and isNormalDatatype()]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.attester.party"/>
      <short value="Who attested the composition"/>
      <definition value="Who attested the composition in the specified way."/>
      <requirements value="Identifies who has taken on the responsibility for accuracy of the composition content."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.attester.party"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Patient"/>
      </type>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Practitioner"/>
      </type>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Organization"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".authenticator.assignedEnttty"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./role[classCode=&quot;ASSIGNED&quot; and isNormalRole]/player[determinerCode=&quot;INST&quot;
         and classCode=(&quot;DEV&quot;, &quot;PSN&quot;) and isNormalEntity()] or ./role[classCode=&quot;ASS
        IGNED&quot; and isNormalRole and not(player)]/scoper[determinerCode=&quot;INST&quot; and
         classCode=&quot;ORG&quot; and isNormalEntity()]"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="who.witness"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.custodian"/>
      <short value="Organization which maintains the composition"/>
      <definition value="Identifies the organization or group who is responsible for ongoing maintenance of and
       access to the composition/document information."/>
      <comments value="This is useful when documents are derived from a composition - provides guidance for how
       to get the latest version of the document. This is optional because this is sometimes
       not known by the authoring system, and can be inferred by context. However it is important
       that this information be known when working with a derived document, so providing a custodian
       is encouraged."/>
      <requirements value="Identifies where to go to find the current version, where to report issues, etc."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.custodian"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Organization"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".custodian.assignedCustodian"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".participation[typeCode=&quot;RCV&quot;].role[classCode=&quot;CUST&quot;].scoper[classCode=&quot;ORG
        &quot; and determinerCode=&quot;INST&quot;]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.event"/>
      <short value="The clinical service(s) being documented"/>
      <definition value="The clinical service, such as a colonoscopy or an appendectomy, being documented."/>
      <comments value="The event needs to be consistent with the type element, though can provide further information
       if desired."/>
      <requirements value="Provides context for the composition and creates a linkage between a resource describing
       an event and the composition created describing the event."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.event"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".documentationOf.serviceEvent"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="outboundRelationship[typeCode=&quot;SUBJ&quot;].target[classCode&lt;'ACT']"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.event.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.event.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.event.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.event.code"/>
      <short value="Code(s) that apply to the event being documented"/>
      <definition value="This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy,
       being documented. In some cases, the event is inherent in the typeCode, such as a &quot;History
       and Physical Report&quot; in which the procedure being documented is necessarily a &quot;History
       and Physical&quot; act."/>
      <comments value="An event can further specialize the act inherent in the typeCode, such as where it is
       simply &quot;Procedure Report&quot; and the procedure was a &quot;colonoscopy&quot;. If
       one or more eventCodes are included, they SHALL NOT conflict with the values inherent
       in the classCode, practiceSettingCode or typeCode, as such a conflict would create an
       ambiguous situation. This short list of codes is provided to be used as key words for
       certain types of queries."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.event.code"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <isSummary value="true"/>
      <binding>
        <strength value="example"/>
        <description value="This list of codes represents the main clinical acts being documented."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/v3-ActCode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.event.period"/>
      <short value="The period covered by the documentation"/>
      <definition value="The period of time covered by the documentation. There is no assertion that the documentation
       is a complete representation for this period, only that it documents events during this
       time."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.event.period"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Period"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".effectiveTime"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".effectiveTime"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.event.detail"/>
      <short value="The event(s) being documented"/>
      <definition value="The description and/or reference of the event(s) being documented. For example, this could
       be used to document such a colonoscopy or an appendectomy."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.event.detail"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=&quot;SUBJ&quot;].target"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.encounter"/>
      <short value="Context of the Composition"/>
      <definition value="Describes the clinical encounter or type of care this documentation is associated with."/>
      <requirements value="Provides context for the composition and supports searching."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.encounter"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Encounter"/>
      </type>
      <isSummary value="true"/>
      <mapping>
        <identity value="cda"/>
        <map value=".componentOf.encompassingEncounter"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="unique(highest(./outboundRelationship[typeCode=&quot;SUBJ&quot; and isNormalActRelationship()],
         priorityNumber)/target[moodCode=&quot;EVN&quot; and classCode=(&quot;ENC&quot;, &quot;PCPR&quot;)
         and isNormalAct])"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="context"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <slicing>
        <discriminator value="Composition.section.code"/>
        <rules value="open"/>
      </slicing>
      <short value="Composition is broken into sections"/>
      <definition value="The root of the sections that make up the composition."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos2"/>
      <label value="Allergies and Intolerances Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1739) such that it"/>
      <comments value="Allergies and Intolerances Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos2"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1760)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos2"/>
      <label value="Allergies, adverse reactions, alerts"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;48765-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1761)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="48765-2"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos2"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1762)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos3"/>
      <label value="Assessment and Plan Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1740) such that it"/>
      <comments value="Assessment and Plan Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos3"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1763)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos3"/>
      <label value="Assessment and Plan"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;51847-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1764)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="51847-2"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos3"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1765)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos4"/>
      <label value="Assessment Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1741) such that it"/>
      <comments value="Assessment Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos4"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1766)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos4"/>
      <label value="Assessments"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;51848-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1767)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="51848-0"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos4"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1768)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos5"/>
      <label value="Chief Complaint and Reason for Visit Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1742) such that it"/>
      <comments value="Chief Complaint and Reason for Visit Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos5"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1769)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos5"/>
      <label value="Chief Complaint and Reason for Visit"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;46239-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1770)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="46239-0"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos5"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1771)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos6"/>
      <label value="Chief Complaint Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1743) such that it"/>
      <comments value="Chief Complaint Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos6"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1772)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos6"/>
      <label value="Chief Complaint"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10154-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1773)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10154-3"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos6"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1774)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos7"/>
      <label value="Family History Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1744) such that it"/>
      <comments value="Family History Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos7"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1775)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos7"/>
      <label value="Family History"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10157-6&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1776)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10157-6"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos7"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1777)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos8"/>
      <label value="General Status Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1745) such that it"/>
      <comments value="General Status Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos8"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1778)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos8"/>
      <label value="General Status"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10210-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1779)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10210-3"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos8"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1780)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos9"/>
      <label value="History of Past Illness Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1746) such that it"/>
      <comments value="History of Past Illness Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos9"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1781)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos9"/>
      <label value="History of Past Illness"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;11348-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1782)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="11348-0"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos9"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1783)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos10"/>
      <label value="History of Present Illness Section"/>
      <short value="section"/>
      <definition value="SHOULD contain zero or one [0..1] section (CONF:2219-1747) such that it"/>
      <comments value="History of Present Illness Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos10"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1784)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos10"/>
      <label value="History of Present Illness"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10164-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1785)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10164-2"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos10"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1786)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos11"/>
      <label value="Immunizations Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1748) such that it"/>
      <comments value="Immunizations Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos11"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1787)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos11"/>
      <label value="Immunizations"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;11369-6&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1788)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="11369-6"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos11"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1789)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos12"/>
      <label value="Medications Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1749) such that it"/>
      <comments value="Medications Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos12"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1790)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos12"/>
      <label value="History of medication use"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10160-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1791)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10160-0"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos12"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1792)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos13"/>
      <label value="Physical Exam Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1750) such that it"/>
      <comments value="Physical Exam Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos13"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1793)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos13"/>
      <label value="Physical Findings"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;29545-1&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1794)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="29545-1"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos13"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1795)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos14"/>
      <label value="Plan of Treatment Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1751) such that it"/>
      <comments value="Plan of Treatment Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos14"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1796)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos14"/>
      <label value="Plan of Treatment"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;18776-5&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1797)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="18776-5"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos14"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1798)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos15"/>
      <label value="Problem Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1752) such that it"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos15"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1799)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos15"/>
      <label value="Problem List"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;11450-4&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1800)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="11450-4"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos15"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1801)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos16"/>
      <label value="Procedures Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1753) such that it"/>
      <comments value="Procedures Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos16"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1802)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos16"/>
      <label value="History of Procedures"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;47519-4&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1803)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="47519-4"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos16"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1804)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos17"/>
      <label value="Reason for Visit Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1754) such that it"/>
      <comments value="Reason for Visit Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos17"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1805)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos17"/>
      <label value="Reason for Visit"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;29299-5&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1806)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="29299-5"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos17"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1807)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos18"/>
      <label value="Results Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1755) such that it"/>
      <comments value="Results Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos18"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1808)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos18"/>
      <label value="Relevant diagnostic tests and/or laboratory data"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;30954-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1809)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="30954-2"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos18"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1810)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos19"/>
      <label value="Review of Systems Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1756) such that it"/>
      <comments value="Review of Systems Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos19"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1811)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos19"/>
      <label value="Review of Systems"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10187-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1812)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10187-3"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos19"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1813)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos20"/>
      <label value="Social History Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1757) such that it"/>
      <comments value="Social History Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos20"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1814)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos20"/>
      <label value="Social History"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;29762-2&quot; (CONF:2219-1815)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <code value="29762-2"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos20"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1816)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos21"/>
      <label value="Vital Signs Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1758) such that it"/>
      <comments value="Vital Signs Section"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos21"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1817)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos21"/>
      <label value="Vital Signs"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;8716-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.11388
      3.6.1) (CONF:2219-1818)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="8716-3"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos21"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1819)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element id="section">
      <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-explicit-type-name">
        <valueString value="Section"/>
      </extension>
      <path value="Composition.section"/>
      <name value="section_slice_pos22"/>
      <label value="Instructions Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1759) such that it"/>
      <comments value="Instructions Section"/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="BackboneElement"/>
      </type>
      <constraint>
        <key value="cmp-2"/>
        <severity value="error"/>
        <human value="A section can only have an emptyReason if it is empty"/>
        <expression value="emptyReason.empty() or entry.empty()"/>
        <xpath value="not(exists(f:emptyReason) and exists(f:entry))"/>
      </constraint>
      <constraint>
        <key value="cmp-1"/>
        <severity value="error"/>
        <human value="A section must at least one of text, entries, or sub-sections"/>
        <expression value="text or entry or section"/>
        <xpath value="exists(f:text) or exists(f:entry) or exists(f:section)"/>
      </constraint>
      <mapping>
        <identity value="cda"/>
        <map value=".component.structuredBody.component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.id"/>
      <representation value="xmlAttr"/>
      <short value="xml:id (or equivalent in JSON)"/>
      <definition value="unique id for the element within a resource (for internal references)."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Element.id"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="id"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.extension"/>
      <short value="Additional Content defined by implementations"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element. In order to make the use of extensions safe and manageable, there is a
       strict set of governance  applied to the definition and use of extensions. Though any
       implementer is allowed to define an extension, there is a set of requirements that SHALL
       be met as part of the definition of the extension."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Element.extension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <mapping>
        <identity value="rim"/>
        <map value="n/a"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.modifierExtension"/>
      <short value="Extensions that cannot be ignored"/>
      <definition value="May be used to represent additional information that is not part of the basic definition
       of the element, and that modifies the understanding of the element that contains it. Usually
       modifier elements provide negation or qualification. In order to make the use of extensions
       safe and manageable, there is a strict set of governance applied to the definition and
       use of extensions. Though any implementer is allowed to define an extension, there is
       a set of requirements that SHALL be met as part of the definition of the extension. Applications
       processing a resource are required to check for modifier extensions."/>
      <comments value="There can be no stigma associated with the use of extensions by any application, project,
       or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
        The use of extensions is what allows the FHIR specification to retain a core level of
       simplicity for everyone."/>
      <alias value="extensions"/>
      <alias value="user content"/>
      <alias value="modifiers"/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="BackboneElement.modifierExtension"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Extension"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <mapping>
        <identity value="rim"/>
        <map value="N/A"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos22"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1821)."/>
      <comments value="The title identifies the section for a human reader. The title must be consistent with
       the narrative of the resource that is the target of the section.content reference. Generally,
       sections SHOULD have titles, but in some documents it is unnecessary or inappropriate.
       Typically, this is where a section has subsections that have their own adequately distinguishing
       title,  or documents that only have a single section. Most Implementation Guides will
       make section title to be a required element."/>
      <requirements value="Section headings are often standardized for different types of documents.  They give guidance
       to humans on how the document is organized."/>
      <alias value="header"/>
      <alias value="label"/>
      <alias value="caption"/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.title"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="string"/>
      </type>
      <mapping>
        <identity value="cda"/>
        <map value=".title"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./title"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos22"/>
      <label value="Instructions"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;69730-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1822)."/>
      <comments value="The code identifies the section for an automated processor of the document. This is particularly
       relevant when using profiles to control the structure of the document.   If the section
       has content (instead of sub-sections), the section.code does not change the meaning or
       interpretation of the resource that is the content of the section in the comments for
       the section.code."/>
      <requirements value="Provides computable standardized labels to topics within the document."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.code"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="69730-0"/>
        </coding>
      </fixedCodeableConcept>
      <binding>
        <strength value="example"/>
        <description value="Classification of a section of a composition/document."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/doc-section-codes"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value=".code"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./code"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos22"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1823)."/>
      <comments value="Document profiles may define what content should be represented in the narrative to ensure
       clinical safety."/>
      <min value="1"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.text"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="Narrative"/>
      </type>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".text"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".text"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.mode"/>
      <short value="working | snapshot | changes"/>
      <definition value="How the entry list was prepared - whether it is a working list that is suitable for being
       maintained on an ongoing basis, or if it represents a snapshot of a list of items from
       another source, or whether it is a prepared list where items may be marked as added, modified
       or deleted."/>
      <requirements value="Sections are used in various ways, and it must be known in what way it is safe to use
       the entries in them."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.mode"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="code"/>
      </type>
      <isModifier value="true"/>
      <isSummary value="true"/>
      <binding>
        <strength value="required"/>
        <description value="The processing mode that applies to this section."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-mode"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outBoundRelationship[typeCode=COMP].target[classCode=OBS&quot;].value"/>
      </mapping>
      <mapping>
        <identity value="w5"/>
        <map value="class"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.orderedBy"/>
      <short value="Order of section entries"/>
      <definition value="Specifies the order applied to the items in the section entries."/>
      <comments value="Applications SHOULD render ordered lists in the order provided, but MAY allow users to
       re-order based on their own preferences as well. If there is no order specified, the order
       is unknown, though there may still be some order."/>
      <requirements value="Important for presentation and rendering.  Lists may be sorted to place more important
       information first or to group related entries."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.orderedBy"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="preferred"/>
        <description value="What order applies to the items in the entry."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-order"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP].sequenceNumber &gt; 1"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.entry"/>
      <short value="A reference to data that supports this section"/>
      <definition value="A reference to the actual resource from which the narrative in the section is derived."/>
      <comments value="If there are no entries in the list, an emptyReason SHOULD be provided."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.entry"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <type>
        <code value="Reference"/>
        <profile value="http://hl7.org/fhir/StructureDefinition/Resource"/>
      </type>
      <condition value="cmp-2"/>
      <mapping>
        <identity value="cda"/>
        <map value=".entry"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".outboundRelationship[typeCode=COMP] or  .participation[typeCode=SBJ]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.emptyReason"/>
      <short value="Why the section is empty"/>
      <definition value="If the section is empty, why the list is empty. An empty section typically has some text
       explaining the empty reason."/>
      <comments value="The various reasons for an empty section make a significant interpretation to its interpretation.
       Note that this code is for use when the entire section content has been suppressed, and
       not for when individual items are omitted - implementers may consider using a text note
       or a flag on an entry in these cases."/>
      <requirements value="Allows capturing things like &quot;none exist&quot; or &quot;not asked&quot; which can
       be important for most lists."/>
      <min value="0"/>
      <max value="1"/>
      <base>
        <path value="Composition.section.emptyReason"/>
        <min value="0"/>
        <max value="1"/>
      </base>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <condition value="cmp-2"/>
      <binding>
        <strength value="preferred"/>
        <description value="If a section is empty, why it is empty."/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/list-empty-reason"/>
        </valueSetReference>
      </binding>
      <mapping>
        <identity value="cda"/>
        <map value="n/a"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value=".inboundRelationship[typeCode=SUBJ,code&lt;{ListEmptyReason}].value[type=CD]"/>
      </mapping>
    </element>
    <element>
      <path value="Composition.section.section"/>
      <short value="Nested Section"/>
      <definition value="A nested sub-section within this section."/>
      <comments value="Nested sections are primarily used to help human readers navigate to particular portions
       of the document."/>
      <min value="0"/>
      <max value="*"/>
      <base>
        <path value="Composition.section.section"/>
        <min value="0"/>
        <max value="*"/>
      </base>
      <contentReference value="#section"/>
      <condition value="cmp-1"/>
      <mapping>
        <identity value="cda"/>
        <map value=".component.section"/>
      </mapping>
      <mapping>
        <identity value="rim"/>
        <map value="./outboundRelationship[typeCode=&quot;COMP&quot; and isNormalActRelationship()]/target[moodCode=&quo
        t;EVN&quot; and classCode=&quot;DOCSECT&quot; and isNormalAct]"/>
      </mapping>
    </element>
  </snapshot>
  <differential>
    <element>
      <path value="Composition"/>
    </element>
    <element>
      <path value="Composition.type"/>
      <label value="History and Physical"/>
      <short value="type"/>
      <definition value="SHALL contain exactly one [1..1] type, which SHALL be selected from ValueSet HPDocumentType
       urn:oid:2.16.840.1.113883.1.11.20.22 DYNAMIC (CONF:2219-1820)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <binding>
        <strength value="required"/>
        <valueSetReference>
          <reference value="http://hl7.org/fhir/ValueSet/2.16.840.1.113883.1.11.20.22"/>
          <display value="HPDocumentType"/>
        </valueSetReference>
      </binding>
    </element>
    <element>
      <path value="Composition.section"/>
      <slicing>
        <discriminator value="Composition.section.code"/>
        <rules value="open"/>
      </slicing>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos2"/>
      <label value="Allergies and Intolerances Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1739) such that it"/>
      <comments value="Allergies and Intolerances Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos2"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1760)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos2"/>
      <label value="Allergies, adverse reactions, alerts"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;48765-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1761)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="48765-2"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos2"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1762)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos3"/>
      <label value="Assessment and Plan Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1740) such that it"/>
      <comments value="Assessment and Plan Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos3"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1763)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos3"/>
      <label value="Assessment and Plan"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;51847-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1764)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="51847-2"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos3"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1765)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos4"/>
      <label value="Assessment Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1741) such that it"/>
      <comments value="Assessment Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos4"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1766)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos4"/>
      <label value="Assessments"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;51848-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1767)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="51848-0"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos4"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1768)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos5"/>
      <label value="Chief Complaint and Reason for Visit Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1742) such that it"/>
      <comments value="Chief Complaint and Reason for Visit Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos5"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1769)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos5"/>
      <label value="Chief Complaint and Reason for Visit"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;46239-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1770)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="46239-0"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos5"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1771)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos6"/>
      <label value="Chief Complaint Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1743) such that it"/>
      <comments value="Chief Complaint Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos6"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1772)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos6"/>
      <label value="Chief Complaint"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10154-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1773)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10154-3"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos6"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1774)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos7"/>
      <label value="Family History Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1744) such that it"/>
      <comments value="Family History Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos7"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1775)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos7"/>
      <label value="Family History"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10157-6&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1776)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10157-6"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos7"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1777)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos8"/>
      <label value="General Status Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1745) such that it"/>
      <comments value="General Status Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos8"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1778)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos8"/>
      <label value="General Status"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10210-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1779)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10210-3"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos8"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1780)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos9"/>
      <label value="History of Past Illness Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1746) such that it"/>
      <comments value="History of Past Illness Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos9"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1781)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos9"/>
      <label value="History of Past Illness"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;11348-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1782)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="11348-0"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos9"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1783)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos10"/>
      <label value="History of Present Illness Section"/>
      <short value="section"/>
      <definition value="SHOULD contain zero or one [0..1] section (CONF:2219-1747) such that it"/>
      <comments value="History of Present Illness Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos10"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1784)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos10"/>
      <label value="History of Present Illness"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10164-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1785)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10164-2"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos10"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1786)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos11"/>
      <label value="Immunizations Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1748) such that it"/>
      <comments value="Immunizations Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos11"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1787)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos11"/>
      <label value="Immunizations"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;11369-6&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1788)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="11369-6"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos11"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1789)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos12"/>
      <label value="Medications Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1749) such that it"/>
      <comments value="Medications Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos12"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1790)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos12"/>
      <label value="History of medication use"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10160-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1791)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10160-0"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos12"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1792)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos13"/>
      <label value="Physical Exam Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1750) such that it"/>
      <comments value="Physical Exam Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos13"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1793)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos13"/>
      <label value="Physical Findings"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;29545-1&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1794)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="29545-1"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos13"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1795)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos14"/>
      <label value="Plan of Treatment Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1751) such that it"/>
      <comments value="Plan of Treatment Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos14"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1796)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos14"/>
      <label value="Plan of Treatment"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;18776-5&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1797)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="18776-5"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos14"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1798)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos15"/>
      <label value="Problem Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1752) such that it"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos15"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1799)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos15"/>
      <label value="Problem List"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;11450-4&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1800)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="11450-4"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos15"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1801)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos16"/>
      <label value="Procedures Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1753) such that it"/>
      <comments value="Procedures Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos16"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1802)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos16"/>
      <label value="History of Procedures"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;47519-4&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1803)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="47519-4"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos16"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1804)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos17"/>
      <label value="Reason for Visit Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1754) such that it"/>
      <comments value="Reason for Visit Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos17"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1805)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos17"/>
      <label value="Reason for Visit"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;29299-5&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1806)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="29299-5"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos17"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1807)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos18"/>
      <label value="Results Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1755) such that it"/>
      <comments value="Results Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos18"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1808)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos18"/>
      <label value="Relevant diagnostic tests and/or laboratory data"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;30954-2&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1809)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="30954-2"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos18"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1810)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos19"/>
      <label value="Review of Systems Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1756) such that it"/>
      <comments value="Review of Systems Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos19"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1811)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos19"/>
      <label value="Review of Systems"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;10187-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1812)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="10187-3"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos19"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1813)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos20"/>
      <label value="Social History Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1757) such that it"/>
      <comments value="Social History Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos20"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1814)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos20"/>
      <label value="Social History"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;29762-2&quot; (CONF:2219-1815)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <code value="29762-2"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos20"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1816)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos21"/>
      <label value="Vital Signs Section"/>
      <short value="section"/>
      <definition value="SHALL contain exactly one [1..1] section (CONF:2219-1758) such that it"/>
      <comments value="Vital Signs Section"/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos21"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1817)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos21"/>
      <label value="Vital Signs"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;8716-3&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.11388
      3.6.1) (CONF:2219-1818)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="8716-3"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos21"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1819)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section"/>
      <name value="section_slice_pos22"/>
      <label value="Instructions Section"/>
      <short value="section"/>
      <definition value="MAY contain zero or one [0..1] section (CONF:2219-1759) such that it"/>
      <comments value="Instructions Section"/>
      <min value="0"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.title"/>
      <name value="section_slice_pos22"/>
      <short value="title"/>
      <definition value="SHALL contain exactly one [1..1] title (CONF:2219-1821)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
    <element>
      <path value="Composition.section.code"/>
      <name value="section_slice_pos22"/>
      <label value="Instructions"/>
      <short value="code"/>
      <definition value="SHALL contain exactly one [1..1] code=&quot;69730-0&quot; (CodeSystem: LOINC urn:oid:2.16.840.1.1138
      83.6.1) (CONF:2219-1822)."/>
      <min value="1"/>
      <max value="1"/>
      <type>
        <code value="CodeableConcept"/>
      </type>
      <fixedCodeableConcept>
        <coding>
          <system value="urn:oid:2.16.840.1.113883.6.1"/>
          <code value="69730-0"/>
        </coding>
      </fixedCodeableConcept>
    </element>
    <element>
      <path value="Composition.section.text"/>
      <name value="section_slice_pos22"/>
      <short value="text"/>
      <definition value="SHALL contain exactly one [1..1] text (CONF:2219-1823)."/>
      <min value="1"/>
      <max value="1"/>
    </element>
  </differential>
</StructureDefinition>