Why are options focused on fulfillment, not status changes? - 2016-09 core #591

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • Workflow
    • 12.1.2
    • Hide

      Will revamp wording to reflect that status changes are possible too.

      Show
      Will revamp wording to reflect that status changes are possible too.
    • Grahame Grieve/Josh Mandel: 8-0-3
    • Clarification
    • Non-substantive
    • DSTU2

      Comment:

      Why do so many Options indicate that you can only perform fulfillment not status changes when the Task or ProcessRequest resource could be the resource which is POSTed or otherwise sent to convey the action to be performed (assuming that it is not possible to use more than one verb (POST) and thereby do an UPDATE or PATCH).

      Summary:

      Why are options focused on fulfillment, not status changes?

            Assignee:
            Unassigned
            Reporter:
            Paul Knapp
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: