Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-39901

Add Bulk Submit Data Operation to Data Exchange Narrative

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DEQM (FHIR)
    • 4.0.0-ballot
    • Clinical Quality Information
    • Data Exchange
    • 2.2.3
    • Hide

      In section 2.2.3 Submit Data, add the paragraph below after the existing introductory paragraph ending in "[...] These update methods are described in detail below."

      Alternatively, data may be submitted in bulk with the $bulk-submit-data operation. This supports both synchronous and asynchronous messaging as described in the operation definition.

      Show
      In section 2.2.3 Submit Data, add the paragraph below after the existing introductory paragraph ending in " [...] These update methods are described in detail below." Alternatively, data may be submitted in bulk with the $bulk-submit-data operation. This supports both synchronous and asynchronous messaging as described in the operation definition.
    • Matt Tiller/Abdullah Rafiqi: 16-0-0
    • Clarification
    • Non-substantive

    Description

      The data exchange section for submitting data currently describes how to use $submit-data to submit data for a single measure. While this is useful, it makes no reference to the $bulk-submit-data operation defined in the FHIR artifacts (http://hl7.org/fhir/us/davinci-deqm/2023Jan/OperationDefinition-bulk-submit-data.html, https://jira.hl7.org/browse/FHIR-38036) for submitting measurereports asynchronously. 

      Consider adding additional narrative to mention the asynchronous bulk option in the data exchange section.

      Attachments

        Activity

          People

            yanheras Yan Heras
            weiyuzh Weiyu Zhang
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: