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

The decision points tree does not seem to follow a natural approach

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive with Modification
    • Specification:
      US Da Vinci HRex (FHIR)
    • Raised in Version:
      current
    • Work Group:
      Clinical Interoperability Council
    • Related Page(s):
      Approaches to Exchanging FHIR Data
    • Related Section(s):
      Decision Points
    • Resolution Description:
      Hide

      We will:

      • In "Direct connection?" section, will call out the fact that there is work-in-progress to allow routing over REST and that once this in place, if it fits within the constraints of the environment, messaging would no longer be necessary.
      • Rename "Human Intervention?" to "Allow Human Intervention?"
      • Revamp "Formal Authorization Required" to:
        • make clear we're talking about authorization for information exchange
        • make clear that Task can be in play even if there's a CommunicationRequest
        • will consider renaming and adjusting diagram so interplay between CommunicationRequest and Task is clearer
        • will reflect that authorization for information exchange sometimes stems from a 'higher level' request (e.g. ServiceRequest, MedicationRequest, etc.)
          *
      Show
      We will: In "Direct connection?" section, will call out the fact that there is work-in-progress to allow routing over REST and that once this in place, if it fits within the constraints of the environment, messaging would no longer be necessary. Rename "Human Intervention?" to "Allow Human Intervention?" Revamp "Formal Authorization Required" to: make clear we're talking about authorization for information exchange make clear that Task can be in play even if there's a CommunicationRequest will consider renaming and adjusting diagram so interplay between CommunicationRequest and Task is clearer will reflect that authorization for information exchange sometimes stems from a 'higher level' request (e.g. ServiceRequest, MedicationRequest, etc.) *

      Description

      The decision points tree does not seem to follow a natural approach on determining the appropriate exchange pattern."Direct connection", "Consumer initates" are secondary to the actual purpose of exchange. There are fundamental prinicples of exchange that must be followed, but beyond that the decisions should be made per the requirements of the use case.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              vassil Vassil Peytchev
              Request in-person:
              Vassil Peytchev
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: