GraphDefinition example (id = "example")

<?xml version="1.0" encoding="UTF-8"?>

<GraphDefinition xmlns="http://hl7.org/fhir">
  <id value="example"/> 
  <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: GraphDefinition</b> <a name="example"> </a> </p> <div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border:
       1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Resource GraphDefinition &quot;example&quot; </p> </div> <p> <b> url</b> : <code> http://h7.org/fhir/GraphDefinition/example</code> </p> <p> <b> name</b> : Document Generation Template</p> <p> <b> status</b> : draft</p> <p> <b> date</b> : 2015-08-04</p> <p> <b> publisher</b> : FHIR Project</p> <p> <b> contact</b> : <a href="http://hl7.org/fhir">http://hl7.org/fhir</a> </p> <p> <b> description</b> : Specify to include list references when generating a document using the $document
         operation</p> <p> <b> start</b> : <span title="  
    the $document operation will include everything directly linked to by the composition
         resource.
    In our case, we want any resources referred to by lists referenced from the
         composition to 
    be included as well. 
    
    We do this by defining a 'graph' of resources - and then we'll say to the $document
         server,
    aggregate this graph as well as other resources. So we define a graph that
         starts at composition,
    goes from section to list, and includes all the resources the list includes.
         
    
    While we're at it, we're going to say that all these resources must be about
         the same patient.
    Note that there are use cases for crossing patient record boundaries in documents,
         but not *this case*.
    
   &amp;#10;  this graph starts with a composition. We don't care what the specific
         profile is
     (though the statement above 'this case doesn't cross patients' implies that
         we do care a little)  ">Composition</span> </p> <blockquote> <p> <b> link</b> </p> <p> <b> path</b> : <span title="  any section entry. Todo: this recurses; are we profiling this at all levels?
            ">Composition.section.entry</span> </p> <p> <b> description</b> : Link to List</p> <blockquote> <p> <b> target</b> </p> <p> <b> type</b> : List</p> <h3> Compartments</h3> <table class="grid"><tr> <td> -</td> <td> <b> Use</b> </td> <td> <b> Code</b> </td> <td> <b> Rule</b> </td> </tr> <tr> <td> *</td> <td> requirement</td> <td> Patient</td> <td> identical</td> </tr> </table> <blockquote> <p> <b> link</b> </p> <p> <b> path</b> : List.entry.item</p> <p> <b> description</b> : Include any list entries</p> </blockquote> </blockquote> </blockquote> </div> </text> <url value="http://h7.org/fhir/GraphDefinition/example"/> 
  <name value="Document Generation Template"/> 
  <status value="draft"/> 
  <date value="2015-08-04"/> 
  <publisher value="FHIR Project"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
  </contact> 
  <description value="Specify to include list references when generating a document using the $document
   operation"/> 
  <!--    
    the $document operation will include everything directly linked to by the composition
   resource.
    In our case, we want any resources referred to by lists referenced from the
   composition to 
    be included as well. 
    
    We do this by defining a 'graph' of resources - and then we'll say to the $document
   server,
    aggregate this graph as well as other resources. So we define a graph that
   starts at composition,
    goes from section to list, and includes all the resources the list includes.
   
    
    While we're at it, we're going to say that all these resources must be about
   the same patient.
    Note that there are use cases for crossing patient record boundaries in documents,
   but not *this case*.
    
     -->
  
  <!--    this graph starts with a composition. We don't care what the specific profile
   is
     (though the statement above 'this case doesn't cross patients' implies that
   we do care a little)    -->
  <start value="Composition"/> 
  
  <!--    define the section -> list link    -->
  <link> 
    <!--    any section entry. Todo: this recurses; are we profiling this at all levels?
        --> 
    <path value="Composition.section.entry"/> 
    <description value="Link to List"/> 
    <!--    
      one target. This graph is not making rules about the content of the section
     entries - that
      would be done in a profile. it's just saying, if you see a reference to a
     list in a section
      entry, these are the rules that describe the graph
       -->
    <target> 
      <type value="List"/> 
      <compartment> 
        <use value="requirement"/> 
        <code value="Patient"/> 
        <rule value="identical"/> 
      </compartment> 
      
      <!--    and inside this list, any references    -->
      <link> 
        <path value="List.entry.item"/> 
        <description value="Include any list entries"/> 
        <target> 
          <type value="Resource"/>  <!--    todo: is this the right way to do 'Any'?    -->
          <compartment> 
            <use value="requirement"/> 
            <code value="Patient"/> 
            <rule value="identical"/> 
          </compartment> 
        </target> 
      </link>       
    </target> 
  </link> 
</GraphDefinition>