Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-26285

Provide guidance for error handling

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Published (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive
    • Specification:
      US Da Vinci Alerts (FHIR)
    • Raised in Version:
      0.2.0
    • Work Group:
      Infrastructure & Messaging
    • Related Page(s):
      Framework
    • Grouping:
    • Resolution Description:
      Hide

      Resolution Description 1) Promote the note to Balloters comments into the guidance for error conditions and reference the existing $porcess-message guidance in the FHIR specification.
      2) Add guidance that parties should consider impact of failure to send and decide what additional steps to undertake.

      Show
      Resolution Description 1) Promote the note to Balloters comments into the guidance for error conditions and reference the existing $porcess-message guidance in the FHIR specification. 2) Add guidance that parties should consider impact of failure to send and decide what additional steps to undertake.
    • Resolution Vote:
      Craig Newman/Paul Knapp: 3-0-1
    • Change Category:
      Enhancement
    • Change Impact:
      Non-substantive

      Description

      What happens if $process-message responds with an error? Is there any guidance you can provide on whether the system should retry sending? Or how the error should be handled? What does that mean for the workflow as a whole if the message fails to be retrieved? I stumbled onto this: "We are actively seeking input on whether additional guidance should be documented in this guide on FHIR-related errors (in addition to normal HTTP errors related to security, header and content type negotiation issues)." I do think it is important to provide guidance for handling errors\.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              seanmcilvenna Sean McIlvenna
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: