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

clarify intermediary role(s)2

    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)
    • Framework (2.1.4)
    • Hide

      Clarify that the Intermediary needs satisfy functional requirements of Sender and Receiver

      see also FHIR-26143 and FHIR-26177

      Show
      Clarify that the Intermediary needs satisfy functional requirements of Sender and Receiver see also FHIR-26143 and FHIR-26177
    • Ulrike Merrick/Nick Radov: 3-0-1
    • Clarification
    • Non-substantive

    Description

      If an intermediary is allowed to process the message and potentially transform the content (to v2 or some other format) before passing it along to another recipient, is it really an intermediary or is it the endpoint that then just happens to do something else with the data. I suggest defining the intermediary as a pass through (perhaps with minimal unpacking of the bundle to all them to route it propoerly) but then indicate that the recipient may fullfill it's business use cases which may include forwarding data on to other recipients.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: