<!--  The following section is fictitious - it exists solely for the purpose of showing examples of text/reference and originalText/reference from discrete entry children. As such, many elements are omitted and replaced by ... comments. The text and content in the discrete entry elements does not use actual clinical content, but instead relies on filler text commonly used in publishing and graphic design.  -->
<section xmlns="urn:hl7-org:v3">
  <text>
    <!--  The text in this section is created strictly to illustrate how discrete entry child elements make references into the human readable text.  -->
    <!--  this paragraph is used for a simple act; the ID values are meant to be unique across the whole document  -->
    <paragraph ID="simpleActFullTextReference1">
      <content ID="simpleActCodeReference1">Lorem ipsum dolor sit amet</content>, consectetur adipiscing elit.
    </paragraph> labetText: DD-mmm-YYYY
  
  </text>
  <!--  this illustrates an act, the basic class of the RIM, but in C-CDA terms the act is used for both Allergy and Problem Concerns, Authorization Activity, Comment Activity and a few other acts.
        -->
  <entry>
    <!--  illustrating a simple act  -->
    <!--  ...  -->
    <act moodCode="EVN" classCode="ACT">
      <!--  ...  -->
      <!--  the code is a required element of act; @displayName is an optional attribute, and when present it should represent a name (some say the name) as defined for the @code in the given @codeSystem  -->
      <code displayName="loreum ipsum" codeSystem="1.2.3.4.5.6.7.8.42"
            code="12345">
        <!--  it is not unusual for the code of an act to be specified in an Implementation Guide and often times text of the code is not in the human readable text, so originalText SHALL NOT be present in those cases
             however, If some of the human readable text is a representation of the code, we SHOULD include a reference to that text using the originalText/reference construct
              -->
        <originalText>
          <!--  the value of this reference begins with hashtag, and is followed by text that is the value of an ID element in the human readable text
               notice that the referenced text is similar to but different than the @displayName  of the code element
               from an interoperability perspective, this pattern is a SHOULD as access to the human readable text reflecting the (code, codeSystem) in use is beneficial to consuming systems
                -->
          <reference value="#simpleActCodeReference1"/>
        </originalText>
      </code>
      <!--  when present, the text/reference points to the entire text of the act
           from an interoperability perspective, this pattern is a MAY as access to the entire human readable text of the act is sometimes useful, but generally not programatically useful (NLP may be needed)
            -->
      <text>
        <!--  notice that the ID containing the referenced value is on an element that includes all text of the act.
             in this case, the element is a paragraph, but might be a table, tbody, tr, etc....elements that typically wrap more entire concepts, not just pieces of content
             Example referenced content, using Comment Activity: Patient is having difficulty paying co-pays for these medications.  -->
        <reference value="#simpleActFullTextReference1"/>
      </text>
    </act>
  </entry>
</section>