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

Transactions in content sharing

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Considered for Future Use
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.1.0-ballot [deprecated]
    • Infrastructure & Messaging
    • STU
    • Get Current Context
    • 2.10
    • Hide

      The spec intentionally used different Bundle types between DxReport-update and GetCurrentContext. Kamal reports that they are, in prod, using transaction Bundles in GetCurrentContext, however. Also Bas requested in-person and hasn't been given a chance to object to reverting this vote, so we'll Defer to allow additional discussion / surveying of the implementation community. 

      Show
      The spec intentionally used different Bundle types between DxReport-update and GetCurrentContext. Kamal reports that they are, in prod, using transaction Bundles in GetCurrentContext, however. Also Bas requested in-person and hasn't been given a chance to object to reverting this vote, so we'll Defer to allow additional discussion / surveying of the implementation community. 
    • Alex Z Liu / Eric Martin: 5-0-0

    Description

      If a Hub supports content sharing, the Hub returns the current content in a content key and the content version in a version key. Bundle entries SHALL not contain a request attribute. The enclosed Bundle resource SHALL have a type of collection. The Bundle SHALL contain no entries if there is no content associated with the current context.

      Should be replaced with text referring to the transaction bundle specification

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: