Jan 2015 Ballot Comment #319

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Financial Mgmt
    • STU
    • ProcessRequest [deprecated]
    • Hide

      Many things could be accomplished using as the trigger: Task, resource creation or changes, Operations, other endpoints, bundles, Transactions and other communication mechanisms - those offered only in FHIR and those provided over other exchanges, eg. web services, email, Direct, MLLP, etc.
      Yes, operations could be defined and used to obtain the processing status of transactions.
      Should this be the only means to obtain that information, no as not all implementers will implement Operations.

      Show
      Many things could be accomplished using as the trigger: Task, resource creation or changes, Operations, other endpoints, bundles, Transactions and other communication mechanisms - those offered only in FHIR and those provided over other exchanges, eg. web services, email, Direct, MLLP, etc. Yes, operations could be defined and used to obtain the processing status of transactions. Should this be the only means to obtain that information, no as not all implementers will implement Operations.
    • Benoit Schoeffler/Mary Kay McDaniel: 6-0-0
    • Clarification

      Comments
      Why can't this be done as a Query using Operation or as a function using Order/OrderResponse?

      Grahame's Comments
      I don't have a clue what this resource is trying to do. What does 'not support a get operation' mean?

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Lloyd McKenzie, Melva Peters
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: