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

Reconsider messaging aspects [added]

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Specialty Rx (FHIR)
    • 0.1.0 [deprecated]
    • Pharmacy
    • Message Structures
    • Hide

      We agree that the FHIR documentation is unclear about where Parameters can and cannot be used.

      The resolutions of Jiras submitted in 2020 by Josh Manel (FHIR-26368) and Vassil Pytchev, the commenter (FHIR-26390) clarify that Parameters may be used as a message focus. Both issues were resolved as non-substantive clarifications, which we understand as indicating that this does not represent a new use, but instead a clarification to documentation.

      To the numbered suggestions in the comment:

      1 and 2. An important goal of the IG is to enable all parties involved in specialty medication fulfillment to participate in the exchanges. As a result, the guide includes a REST-only implementation option as well as a messaging-based option for a large portion of pharmacies that today rely on network intermediaries. The messaging approach supports network routing, which is why we chose that approach over use of operations.

      3. We believe the messaging structures in the guide include the resources needed to accomplish the intent of each exchange.

      Show
      We agree that the FHIR documentation is unclear about where Parameters can and cannot be used. The resolutions of Jiras submitted in 2020 by Josh Manel ( FHIR-26368 ) and Vassil Pytchev, the commenter ( FHIR-26390 ) clarify that Parameters may be used as a message focus. Both issues were resolved as non-substantive clarifications, which we understand as indicating that this does not represent a new use, but instead a clarification to documentation. To the numbered suggestions in the comment: 1 and 2. An important goal of the IG is to enable all parties involved in specialty medication fulfillment to participate in the exchanges. As a result, the guide includes a REST-only implementation option as well as a messaging-based option for a large portion of pharmacies that today rely on network intermediaries. The messaging approach supports network routing, which is why we chose that approach over use of operations. 3. We believe the messaging structures in the guide include the resources needed to accomplish the intent of each exchange.
    • Frank McKinney / Tim McNeil : 11-0-3

    Description

      The paradigm of a message wrapping prameters is not a common one. In fact, before R5 having a Parameters resource be referenced in MessageHeader.focus was prohibited by the definition of the resource. FHIR Messaging in general is less mature as an exchange method compared to the RESTful formats. One of the following should be done to address this:
      1. Focus the initial version of the specification on the RESTful exchange.
      2. Use operations instead of messaging - the parameters for the operations are already defined
      3. Use a simpler messaging structure

      Existing Wording:

      a Parameters resource as the focus

      (Comment 18 - imported by: Jean Duteau)

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: