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

Why Messaging?

    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)
    • Hide

      Add guidance surrounding the ramifications of messaging and clarify that this guide is specifying a simple more FHIR RESTful operation based approach using $process-message and messaging structure which is compatible with a full FHIR Messaging. Implementation may choose to develop a more integrated and complete FHIR messaging solution. Clarify our approach and options and ramificiations of each approach.

      Show
      Add guidance surrounding the ramifications of messaging and clarify that this guide is specifying a simple more FHIR RESTful operation based approach using $process-message and messaging structure which is compatible with a full FHIR Messaging. Implementation may choose to develop a more integrated and complete FHIR messaging solution. Clarify our approach and options and ramificiations of each approach.
    • Craig Newman/Paul Knapp: 3-0-1
    • Clarification
    • Non-substantive

    Description

      Rather than re-invent messaging, it makes more sense to use the new subscription Framework coming up in R5. ADT-style messaging is covered pretty well with HL7v2 messages, and using HL7-over-HTTP, requires a much smaller effort that creating a FHIR Messaging infrastructure

      Attachments

        Activity

          People

            Unassigned Unassigned
            vassil Vassil Peytchev
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: