Release 5 Preview #3


FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

GraphDefinition example (id = "example")

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

<GraphDefinition xmlns="">
  <id value="example"/> 
  <text> <status value="generated"/> <div xmlns=""><p> <b> Generated Narrative</b> </p> <p> <b> url</b> : <code></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></a> </p> <p> <b> description</b> : Specify to include list references when generating a document using the $document operation</p> <p> <b> start</b> : Composition</p> <blockquote> <p> <b> link</b> </p> <p> <b> path</b> : Composition.section.entry</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> <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> <h3> Links</h3> <table> <tr> <td> -</td> </tr> <tr> <td> *</td> </tr> </table> </blockquote> </blockquote> </div> </text> <url value=""/> 
  <name value="Document Generation Template"/> 
  <status value="draft"/> 
  <date value="2015-08-04"/> 
  <publisher value="FHIR Project"/> 
      <system value="url"/> 
      <value value=""/> 
  <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
    In our case, we want any resources referred to by lists referenced from the composition
    be included as well. 
    We do this by defining a 'graph' of resources - and then we'll say to the $document
    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
    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    -->
    <!--    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
      <type value="List"/> 
        <use value="requirement"/> 
        <code value="Patient"/> 
        <rule value="identical"/> 
      <!--    and inside this list, any references    -->
        <path value="List.entry.item"/> 
        <description value="Include any list entries"/> 
          <type value="Resource"/>  <!--    todo: is this the right way to do 'Any'?    -->
            <use value="requirement"/> 
            <code value="Patient"/> 
            <rule value="identical"/> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.