2015May core #1254 - Remove SHOULD stipulation for Server Content Manipulation

XMLWordPrintableJSON

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

      Change the phrase to: "For this reason, servers SHOULD change the resource as little as possible,?given the constraints of the system exposing the FHIR resource.?However due to the variability that exists within healthcare, this specification allows that servers MAY alter the resource on create/update."

      ?

      ?

      Show
      Change the phrase to: "For this reason, servers SHOULD change the resource as little as possible,?given the constraints of the system exposing the FHIR resource.?However due to the variability that exists within healthcare, this specification allows that servers MAY alter the resource on create/update." ? ?
    • Michael Donnelly / Josh Mandel: 16-0-4
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: For this reason, servers SHOULD change the resource as little as possible. However due to the variability that exists within healthcare, this specification allows that servers MAY alter the resource on create/update.

      Proposed Wording: This specification allows that servers MAY alter the resource on create/update.

      Comment:

      FHIR servers will be implemented within EMRs and other HIT applications, where application actions outside of the API may constitue a large majority of the interaction with FHIR resources. We should therefore remove the SHOULD stipulation of this

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

              Created:
              Updated:
              Resolved: