add doNotPerform to Task (core or standard extension)

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • Task
    • Hide

      At this point, we can't think of any "do not perform" use-cases that wouldn't be better handled by either using one of the more formal 'authorization' requests (MedicaitonRequest, ServiceRequest, etc.) or better be captured as part of a higher level requst/Task describing something to be done.  If someone comes forward with a concrete use-case where doNotPerform on Task is appropriate, we'll happily re-evaluate this decision.

      Show
      At this point, we can't think of any "do not perform" use-cases that wouldn't be better handled by either using one of the more formal 'authorization' requests (MedicaitonRequest, ServiceRequest, etc.) or better be captured as part of a higher level requst/Task describing something to be done.  If someone comes forward with a concrete use-case where doNotPerform on Task is appropriate, we'll happily re-evaluate this decision.
    • John Hatem/Jose Costa Teixeira: 6-0-0

      It is possible to order NOT to perform a specific task

      The standard extension exists and we should either add Task to its scope (or in core) or justify why this is not applicable

      For history, see #26526

            Assignee:
            Unassigned
            Reporter:
            Jose Costa-Teixeira
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: