Operation Definition for Code System DefinitionResourceType

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


  
  
    
  
  
    

<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="Resource-graph"/> 
  <text> 
    <status value="extensions"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      
      
        

      
      
      

      <p> URL: [base]/Resource/[id]/$graph</p> 
      <p> Parameters</p> 
      <table class="grid">
        <tr> 
          
            

          <td> 
            <b> Use</b> 
          </td> 
          <td> 
            

            <b> Name</b> 
          </td> 
          <td> 
            

            <b> Cardinality</b> 
          </td> 
        
        
          ActivityDefinition
            

          <td> 
            <b> Type</b> 
          </td> 
          
          This resource allows for the definition of some activity to be performed, independent
             of a particular patient, practitioner, or other performance context.
        
        
          EventDefinition
            

          <td> 
            <b> Binding</b> 
          </td> 
          
          The EventDefinition resource provides a reusable description of when a particular event
             can occur.
        
        
          Measure
            

          <td> 
            <b> Documentation</b> 
          </td> 
          
          

        </tr> 
        <tr> 
          OperationDefinition
            

          <td> IN</td> 
          <td> graph</td> 
          <td> 1..1</td> 
          <td> 
            <a href="datatypes.html#uri">uri</a> 
          </td> 
          
          A formal computable definition of an operation (on the RESTful interface) or a named query
             (using the search interaction).
        
        
          PlanDefinition
            

          <td/>  
          <td> 
            <div> 
              <p> Servers MAY choose to allow any graph definition to be specified, but MAY require
                 that the client choose a graph definition from a specific list of known supported
                 definitions. The server is not required to support a formal definition of the graph
                 on the end point</p> 

            </div> 
          </td> 
          
          This resource allows for the definition of various types of plans as a sharable, consumable,
             and executable artifact. The resource is general enough to support the description of
             a broad range of clinical artifacts such as clinical decision support rules, order sets
             and protocols.

        </tr> 
        <tr> 
          Questionnaire
            

          <td> OUT</td> 
          <td> result</td> 
          <td> 1..1</td> 
          <td> 
            <a href="bundle.html">Bundle</a> 
          </td> 
          <td/>  
          <td> 
            <div> 
              <p> The set of resources that were in the graph based on the provided definition</p> 

            </div> 
          </td> 
          
          A structured set of questions intended to guide the collection of answers from end-users.
             Questionnaires provide detailed control over order, presentation, phraseology and grouping
             to allow coherent, consistent data collection.

        </tr> 
      </table> 
      <div/>  
    </div> 
  
  
    
  
  
  
    
    
  
  
  
  
  
  
  
  
  
  
  
  
    
    
    This resource allows for the definition of some activity to be performed, independent
     of a particular patient, practitioner, or other performance context.
  
  
    
    
    The EventDefinition resource provides a reusable description of when a particular event
     can occur.
  
  
    
    
    
  
  
    
    
    A formal computable definition of an operation (on the RESTful interface) or a named query
     (using the search interaction).
  
  
    
    
    This resource allows for the definition of various types of plans as a sharable, consumable,
     and executable artifact. The resource is general enough to support the description of
     a broad range of clinical artifacts such as clinical decision support rules, order sets
     and protocols.
  
  
    
    
    A structured set of questions intended to guide the collection of answers from end-users.
     Questionnaires provide detailed control over order, presentation, phraseology and grouping
     to allow coherent, consistent data collection.
  

  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/> 
  </extension> 
  <url value="http://hl7.org/fhir/OperationDefinition/Resource-graph"/> 
  <version value="5.0.0-ballot"/> 
  <name value="Graph"/> 
  <title value="Return a graph of resources"/> 
  <status value="draft"/> 
  <kind value="operation"/> 
  <experimental value="false"/> 
  <date value="2022-09-10T04:52:37+10:00"/> 
  <publisher value="HL7 (FHIR Project)"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
    <telecom> 
      <system value="email"/> 
      <value value="fhir@lists.hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="Return an entire graph of resources based on a [GraphDefinition](graphdefinition.html).
   The operation is invoked on a specific instance of a resource, and the graph definition
   tells the server what other resources to return in the same packaage"/> 
  <affectsState value="false"/> 
  <code value="graph"/> 
  <resource value="Resource"/> 
  <system value="false"/> 
  <type value="false"/> 
  <instance value="true"/> 
  <parameter> 
    <name value="graph"/> 
    <use value="in"/> 
    <min value="1"/> 
    <max value="1"/> 
    <documentation value="Servers MAY choose to allow any graph definition to be specified, but MAY require

     that the client choose a graph definition from a specific list of known supported
     definitions. The server is not required to support a formal definition of the graph
     on the end point"/> 
    <type value="uri"/> 
  </parameter> 
  <parameter> 
    <name value="result"/> 
    <use value="out"/> 
    <min value="1"/> 
    <max value="1"/> 
    <documentation value="The set of resources that were in the graph based on the provided definition"/> 
    <type value="Bundle"/> 
  </parameter> 


</
CodeSystem


OperationDefinition


>