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

FHIR Messaging description seems to be missing a significant flow

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci HRex (FHIR)
    • 0.2.0
    • Clinical Interoperability Council
    • Approaches to Exchanging FHIR Data
      Exchanging with messaging
    • Hide

      We will break "messaging" down into a choice of two workflow options - a pull-based approach (which is what we're primarily talking about now) and a 'push' based notification approach.  We'll also adjust the decision tree so that references to 'messaging' are specific about whether they're to pull-based messaging, push-based messaging or both.

      Show
      We will break "messaging" down into a choice of two workflow options - a pull-based approach (which is what we're primarily talking about now) and a 'push' based notification approach.  We'll also adjust the decision tree so that references to 'messaging' are specific about whether they're to pull-based messaging, push-based messaging or both.
    • Marti Velezis / Jimmy Tcheng : 6-0-1
    • Enhancement
    • Non-substantive

    Description

      The FHIR messaging descriptions in the Approaches page (and the Exchanging with Messaging page) doesn't include what many consider to be an important messaging use case which is for the initiating system to be pushing data of interest to the recipient. Much of the Public Health infrastructure being development in FHIR uses this model but it doesn't seem to be represented. In this flow, the initial message isn't a request for data but rather a set of data the recipient is expected to be interested in. The system labels used in this sort of flow are opposite of what is there now (in this case the message initiator is more of the "Data Source" while the recipient is the "Data Consumer"). If this is a valid use of the FHIR messaging workflow, it should be represented in these pages.

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Craig Newman
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: