2015May core #1242 - Server Representation of Content should be returned on Create and Update

XMLWordPrintableJSON

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

      The idea is that it is likely that data will be transformed, and by not returning you stimulate client behaviour to not verify the data.

      We believe that clients who choose not to validate the data will ignore the data even if the server returns it, so this argument is not persuasive. Seeing the clear benefits in the mobile/low bandwidth space, we choose to keep the current behaviour.

      Show
      The idea is that it is likely that data will be transformed, and by not returning you stimulate client behaviour to not verify the data. We believe that clients who choose not to validate the data will ignore the data even if the server returns it, so this argument is not persuasive. Seeing the clear benefits in the mobile/low bandwidth space, we choose to keep the current behaviour.
    • Josh Mandel / David Hay: 17-0-2
    • Enhancement

      Existing Wording: The client can indicate whether the entire resource is returned using the HTTP return preference:

      Proposed Wording: Servers SHALL return the entire resource content as it is represented in their system.

      Comment:

      Servers may transform content received from the client and that server-native representation of content should be conveyed to clients

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

              Created:
              Updated:
              Resolved: