2015May core #1256 - Guidelines for Resource Integrity Management within Conformance

XMLWordPrintableJSON

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

      The basic needs are now covered, since the R4 spec now says:

      "Both client and server systems SHOULD clearly document how transaction integrity is handled, in the documentation in the CapabilityStatement."

      instead.

      We propose to keep the current text, until a more specific request comes up to change it.

      Show
      The basic needs are now covered, since the R4 spec now says: "Both client and server systems SHOULD clearly document how transaction integrity is handled, in the documentation in the CapabilityStatement ." instead. We propose to keep the current text, until a more specific request comes up to change it.
    • Michael Donnelly/Richard Ettema: 5-0-0
    • Enhancement

      Existing Wording: Both client and server systems SHOULD clearly document how transaction integrity is handled. DSTU TODO: how?

      Proposed Wording: Both client and server systems SHALL clearly document how transaction integrity is handled through one of two ways. (1) If servers manage and track resource transaction integrity, servers indicate that they will redirect to target resources of merged content on resource-level interactions, and (2) if servers do not manage and track, they should indicate this through operationoutcome

      Comment:

      We should give clear guidelines for how to support transactional integrity by servers. We've defined two general strategies, but will likely need to update the conformance resource to support the tracking of this information

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

              Created:
              Updated:
              Resolved: