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

New IG for messaging fundamentals

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • (many)
    • 2.1.5
    • Hide

      Future guidance on reliable delivery for Message-based Notifications  will be documented in base FHIR and the HRex IG (which already addresses this paradigm here:  http://hl7.org/fhir/us/davinci-hrex/exchanging-messaging.html#message-based-notifications.)

      Also, see FHIR-38033, which addressed this comment and when to move guidance to HRex.

      Show
      Future guidance on reliable delivery for Message-based Notifications  will be documented in base FHIR and the HRex IG (which already addresses this paradigm here:   http://hl7.org/fhir/us/davinci-hrex/exchanging-messaging.html#message-based-notifications.) Also, see FHIR-38033 , which addressed this comment and when to move guidance to HRex.

    Description

      I don't think we should do that in this IG. Instead define a new IG for foundational Da Vinci messaging guidelines and put it there. We will likely using the messaging paradigm in additional future IGs beyond just Alerts so we won't want to repeat ourselves.

      Existing Wording:

      Note To Balloters
      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). For example, whether to define a minimum set of error response code, such as those listed here. Additionally, what additional guidance to specify how the Sender can provide a more reliable delivery of notifications to the intended recipient(s). For example, defining what actions the Sender must take when it receives a particular error response code.

      Attachments

        Activity

          People

            Unassigned Unassigned
            nradov Nick Radov
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: