Clarify the justification for requiring a "transaction" in history bundle entries

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • Bundle
    • Hide

      Clarify that it allows receiving systems to differentiate between create and update, and that it would allow a history to be treated as a transaction (though note limitations with this around transaction boundaries)

      Show
      Clarify that it allows receiving systems to differentiate between create and update, and that it would allow a history to be treated as a transaction (though note limitations with this around transaction boundaries)
    • Grahame Grieve / Ewout Kramer : 7-0-1
    • Non-substantive
    • DSTU1 [deprecated]

      http://hl7-fhir.github.io/http.html#history says

      Each entry SHALL contain a transaction, and, if the entry.transaction.method is a PUT or a POST, a resource.

      It would be helpful to provide the rationale for this behavior (something like "This ensures that a history response from one server can be 'fed into' another server's transaction endpoint, forming the basis for a primitive one-way data synchronization protocol.")

            Assignee:
            Unassigned
            Reporter:
            Josh Mandel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: