Request (Solicited Communication) unclear

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • Patient Care
    • STU
    • Profile overview [deprecated]
    • Hide

      We will add a section at the beginning of the Request page explaining why it might be used instead of the simpler 'Pull' (i.e. query) mechanism.  Specifics include - the data source doesn't/can't/won't support query for regulatory or technical reasons; the data being retrieved will need to be assembled, reviewed, filtered or otherwise manipulated in an asynchronous manner that prevents a synchronous query from being used.

      Show
      We will add a section at the beginning of the Request page explaining why it might be used instead of the simpler 'Pull' (i.e. query) mechanism.  Specifics include - the data source doesn't/can't/won't support query for regulatory or technical reasons; the data being retrieved will need to be assembled, reviewed, filtered or otherwise manipulated in an asynchronous manner that prevents a synchronous query from being used.
    • Richard Esmond / Marti Velezis : 10-0-0
    • Enhancement
    • Non-substantive

      Request (Solicited Communication)

      It isn't clear why Request is an alternative to Pull, especially since the actor interaction diagrams are using Post (Get).

      Pull just states that the Sender "supports" the query. Request states that the Sender receives, processes, completes, and sends the communication to the requestor - which to me is the definition of "supports".

      Please add a discussion to explain why Request is an alternative, including what makes Request different from Pull.

            Assignee:
            Unassigned
            Reporter:
            Patricia Craig
            Patricia Craig
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: