Clarification on OperationOutcome - 2018-May Core Norm Infrastructure #212

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Bundle
    • Hide

      batch : no, errors come in entry.resource, not entry.response.outcome.

      transaction: no error must be a whole group thing.

      Clarify this in the documentation

      Show
      batch : no, errors come in entry.resource, not entry.response.outcome. transaction: no error must be a whole group thing. Clarify this in the documentation
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Non-substantive
    • STU3

      Existing Wording: OperationOutcome with hints and warnings (for batch/transaction)

      Comment:

      For batch, wouldn't errors come back here too? And for transactions, would it be wrong to provide an entry-by-entry list of errors rather than reporting them all as a group if the transaction fails?

      Summary:

      Clarification on OperationOutcome

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: