2015May core #471 - Don't let client make decisions for the server

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Implementable Technology Specifications
    • REST (http)
    • 2.1.0.13.1 Condition
    • Hide

      The text in the specification mentions the possibility for the server to return a 422 (2.1.0.13) if it chooses to enforce avoiding duplicate data based on its own business rules.

      So the server is allowed to determine itself what would be considered a duplicative entry.

      Show
      The text in the specification mentions the possibility for the server to return a 422 (2.1.0.13) if it chooses to enforce avoiding duplicate data based on its own business rules. So the server is allowed to determine itself what would be considered a duplicative entry.
    • Bill de Beaubien / Josh Mandel: 16-0-3
    • Correction

      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.

      Comment:

      Allowing a client to make the decisions for the server is problematic as the client may not be aware of all of the conditions and requirements of the server. The server should also be allowed to determine itself what would be considered a duplicative entry regardless of whether the client uses a conditional create or not (If this is allowed by the specification, it should be explicetely stated.

            Assignee:
            Unassigned
            Reporter:
            corey_spears#1
            corey_spears#1
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: