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

Provide guidance for error handling

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • Framework
    • 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.
    • Craig Newman/Paul Knapp: 3-0-1
    • Enhancement
    • 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

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: