2015May core #1255 - Transaction Integrity Guidelines in Read and Search

XMLWordPrintableJSON

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

      Add a section about handling errors with searches that clarifies this.

      Show
      Add a section about handling errors with searches that clarifies this.
    • James Agnew / Grahame Grieve: 4-0-0
    • Enhancement
    • Compatible, substantive
    • Yes
    • DSTU1 [deprecated]

      Comment:

      We suggest that we make more specific guidelines for how to handle resource integrity and lifecycle management. We suggest that we give clear guidelines for at minimum read and other resource level interactions on merged content, and search behavior when resource identifiers are used as parameters. For the former case, we suggest performing content redirection where possible, or if not possible, to provide specific OperationOutcomes to indicate content modification caused the HTTP error. For the latter, we request guidance on specific search outcomes when resource identifiers used in the search parameters have been merged, deleted, or otherwise modified, and suggest additional OperationOutcomes specifying these particular conditions

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

              Created:
              Updated:
              Resolved: