2015May core #470 - More explanation on client-assigned ids

XMLWordPrintableJSON

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

      Add Grahame's uses cases and a clarifying statement that servers can state if supplied IDs are supported

      Show
      Add Grahame's uses cases and a clarifying statement that servers can state if supplied IDs are supported
    • Grahame Grieve / Andy Stechishin 4-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: If the client wishes to have control over the id of a newly submitted resource, it should use the update interaction instead.

      Comment:

      It is not clear as to what is meant here. More explanation should be provided. Given that all of the data resides on the server, which is managing all of the data directly, it is not clear why the client should ever have control over the meta id for a resource.

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

              Created:
              Updated:
              Resolved: