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

Reliable Delivery - Unreachable Scenarios

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive with Modification
    • Specification:
      US Da Vinci Alerts (FHIR)
    • Raised in Version:
      0.2.0
    • Work Group:
      Infrastructure & Messaging
    • Related Page(s):
      Framework
    • Related Section(s):
      2.1.5
    • Resolution Description:
      Hide

      re additional area to consider is when the Sender cannot reach the Recipient (e.g., network down, certificates expired, DNS issues, etc.).

      These are 400 or 500 http errors and there is existing guidance from the FHIR specification that we will point to in the section as well as providing specific guidance by moving the following note to balloters commenters into the guidance.

      "
      200,202,204+/- OperationOutcome all ok for successful transactions
      Issue : what does widely use Java client want?
      401,404+/- OperationOutcome no point in retry
      429 +/- OperationOutcome retry but slow down traffic
      500+ +/- OperationOutcome - server issues may retry a few times
      "

      Show
      re additional area to consider is when the Sender cannot reach the Recipient (e.g., network down, certificates expired, DNS issues, etc.). These are 400 or 500 http errors and there is existing guidance from the FHIR specification that we will point to in the section as well as providing specific guidance by moving the following note to balloters commenters into the guidance. " 200,202,204+/- OperationOutcome all ok for successful transactions Issue : what does widely use Java client want? 401,404+/- OperationOutcome no point in retry 429 +/- OperationOutcome retry but slow down traffic 500+ +/- OperationOutcome - server issues may retry a few times "
    • Resolution Vote:
      Riki Merrick / Sandy Stuart: 3-0-1
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      In considering reliable delivery, an additional area to consider is when the Sender cannot reach the Recipient (e.g., network down, certificates expired, DNS issues, etc.).

      Existing Wording:

      Note to Balloters…

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              ginocanessa Gino Canessa
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: