2015May core #1248 - Remove support for conditional creates.

XMLWordPrintableJSON

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

      Motion: add language to the specification explaining that transactions and conditional operations are complex and it is not expected that every server will implement them.

      (We think the same resolution should apply to 7926 and 7927.)

      Show
      Motion: add language to the specification explaining that transactions and conditional operations are complex and it is not expected that every server will implement them. (We think the same resolution should apply to 7926 and 7927.)
    • Michael Donnelly / Grahame Grieve: 12-0-0
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: The conditional create operation allows a client to create a new resource only if some equivalent resource does not already exist on the server. The client defines what equivalence means in this case by supplying a FHIR search query in an If-None-Existheader as shown:

      Proposed Wording: Remove

      Comment:

      The standard should not include support for conditional creates This action between a server and client should occur as a Search + Creates, as it gives clients the opportunity to validate the resource they are looking to create prior to modifying content within the server

            Assignee:
            Unassigned
            Reporter:
            seanmoore
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: