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

New IG for messaging fundamentals

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Deferred (View Workflow)
    • Priority: Highest
    • Resolution: Considered for Future Use
    • Specification:
      US Da Vinci Alerts (FHIR)
    • Raised in Version:
      0.2.0
    • Work Group:
      Infrastructure & Messaging
    • Related Page(s):
      (many)
    • Related Section(s):
      2.1.5
    • Resolution Description:
      Hide

      IN this IG we are specifying a simple more FHIR RESTful operation based approach see FHIR-26098.

      This constrained form of messaging is currently supported only by this IG. Agree that after publication and general vetting of the approach the exchange pattern content should should be merged into the Da Vinci hrex IG and referenced from it in a future version of this IG.

      Show
      IN this IG we are specifying a simple more FHIR RESTful operation based approach see FHIR-26098 . This constrained form of messaging is currently supported only by this IG. Agree that after publication and general vetting of the approach the exchange pattern content should should be merged into the Da Vinci hrex IG and referenced from it in a future version of this IG.
    • Resolution Vote:
      Craig Newman/Paul Knapp: 3-0-1

      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

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              nradov Nick Radov
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: