Operation Definition

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


  
  
    
    
      
      
      
      
      
        The submit-data operation is used to submit data-of-interest for a measure. There is no
           expectation that the submitted data represents all the data-of-interest, only that all
           the data submitted is relevant to the calculation of the measure for a particular subject
           or population

      
      
      
      
      
        
          
            
          
          
            
          
          
            
          
          
            
          
          
            
          
          
            
          
        
        
          
          
          
          
            
          
          
          
            
              

            
          
        
        
          
          
          
          
            
          
          
          
            
              

            
          
        
      
      
        The effect of invoking this operation is that the submitted data is posted to the receiving
           system and can be used for subsequent calculation of the relevant quality measure. The
           data-of-interest for a measure can be determined by examining the measure definition,
           or by invoking the $data-requirements operation

      
    
  
  
    
  
  
    
  
  
  
  
  
  
  
  
  
    
      
      
    
    
      
      
    
  
  The submit-data operation is used to submit data-of-interest for a measure. There is no
   expectation that the submitted data represents all the data-of-interest, only that all
   the data submitted is relevant to the calculation of the measure for a particular subject
   or population
  
  The effect of invoking this operation is that the submitted data is posted to the receiving
   system and can be used for subsequent calculation of the relevant quality measure. The
   data-of-interest for a measure can be determined by examining the measure definition,
   or by invoking the $data-requirements operation
  
  
  
  
  
    
    
    
    
    
    
  
  
    
    
    
    
    
    
  

<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="Measure-submit-data"/> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p class="res-header-id">
        <b> Generated Narrative: OperationDefinition Measure-submit-data</b> 
      </p> 
      <a name="Measure-submit-data"> </a> 
      <a name="hcMeasure-submit-data"> </a> 
      <p> URL: [base]/Measure/$submit-data</p> 
      <h3> Parameters</h3> 
      <table class="grid">
        <tr> 
          <td> 
            <b> Use</b> 
          </td> 
          <td> 
            <b> Name</b> 
          </td> 
          <td> 
            <b> Scope</b> 
          </td> 
          <td> 
            <b> Cardinality</b> 
          </td> 
          <td> 
            <b> Type</b> 
          </td> 
          <td> 
            <b> Binding</b> 
          </td> 
          <td> 
            <b> Documentation</b> 
          </td> 
        </tr> 
        <tr> 
          <td> IN</td> 
          <td> bundle</td> 
          <td/>  
          <td> 1..*</td> 
          <td> 
            <a href="measurereport.html">MeasureReport</a> 
          </td> 
          <td/>  
          <td> 
            <div> 
              <p> Bundles for each subject, containing a MeasureReport resource for each Measure
                 being submitted, followed by entries for the data-of-interest for that subject.</p> 
            </div>           </td>         </tr>       </table>       <div>         <p> The effect of invoking this operation is that the submitted data is posted to the

           receiving system and can be used for subsequent calculation of the relevant quality
           measure. The data-of-interest for a measure can be determined by examining the
           measure definition, or by invoking the $data-requirements operation.</p> 
      </div>     </div>   </text>   <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">    <valueInteger value="3"/>   </extension>   <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">    <valueCode value="deprecated"/>   </extension>   <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">    <valueCode value="cqi"/>   </extension>   <url value="http://hl7.org/fhir/OperationDefinition/Measure-submit-data"/>   <version value="6.0.0-ballot3"/>   <name value="SubmitData"/>   <title value="Submit Data"/>   <status value="draft"/>   <kind value="operation"/>   <experimental value="false"/>   <date value="2025-11-24T20:46:00+00:00"/>   <publisher value="HL7 International / Clinical Quality Information"/>   <contact>     <telecom>       <system value="url"/>       <value value="http://hl7.org/fhir"/>     </telecom>     <telecom>       <system value="email"/>       <value value="fhir@lists.hl7.org"/>     </telecom>   </contact>   <contact>     <telecom>       <system value="url"/>       <value value="http://www.hl7.org/Special/committees/cqi"/>     </telecom>   </contact>   <description value="The submit-data operation is used to submit data-of-interest for one or more measures

   for one or more subjects. Each submitted Bundle **SHOULD** contain resources for
   a single subject and **SHOULD** contain all of the MeasureReports and data of interest
   related to that subject. There is no expectation that the submitted data represents
   all the data-of-interest, only that all the data submitted is relevant to the calculation
   of the measure for a particular subject or population. The dataUpdateType element
   of the MeasureReport resource is used to indicate whether the data being submitted
   is a snapshot or incremental update. Additional guidance about data exchange for
   quality reporting can be found in the Data Exchange for Quality Measures implementation
   guide. Note that the use of the [X-Provenance header data](https://hl7.org/fhir/6.0.0-ballot3
  /provenance.html#header) with data that establishes provenance being submitted/collected
   **SHOULD** be supported. This provides the capability for associating the provider
   with the data submitted through the $submit-data transaction. If the X-Provenance
   header is used it should be consistent with the reporter element in the DEQM Data
   Exchange MeasureReport Profile. This operation is purposefully not allowed on a
   Measure instance because the MeasureReport included in the Bundle specifies the
   measure.\n\nNOTE: This operation is being deprecated in favor of just posting the
   bundles to the root of the server, either as collection or transaction bundles."/> 
  <jurisdiction>     <coding>       <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>       <code value="001"/>       <display value="World"/>     </coding>   </jurisdiction>   <affectsState value="false"/>   <code value="submit-data"/>   <comment value="The effect of invoking this operation is that the submitted data is posted to the

   receiving system and can be used for subsequent calculation of the relevant quality
   measure. The data-of-interest for a measure can be determined by examining the
   measure definition, or by invoking the $data-requirements operation."/> 
  <resource value="Measure"/>   <system value="false"/>   <type value="true"/>   <instance value="false"/>   <parameter>     <name value="bundle"/>     <use value="in"/>     <min value="1"/>     <max value="*"/>     <documentation value="Bundles for each subject, containing a MeasureReport resource for each Measure

     being submitted, followed by entries for the data-of-interest for that subject."/> 
    <type value="MeasureReport"/>   </parameter> 


</

OperationDefinition

>