Clarify meaning of Task.basedOn - 2016-09 core #178

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • Task
    • Task.basedon
    • Hide

      Update the definition to;

      "BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a DiagnosticRequest, MedicationRequest, ProcedureRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfil. This latter resource is referenced by FocusOn. For example, based on a DiagnosticRequest (= BasedOn), a task is created to fulfil a procedureRequest ( = FocusOn ) to collect a specimen from a patient.

      Show
      Update the definition to; "BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a DiagnosticRequest, MedicationRequest, ProcedureRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfil. This latter resource is referenced by FocusOn. For example, based on a DiagnosticRequest (= BasedOn), a task is created to fulfil a procedureRequest ( = FocusOn ) to collect a specimen from a patient.
    • Eric Haas/Jose Costa-Teixera: 7-0-5
    • Clarification
    • Non-substantive
    • DSTU2

      Existing Wording: Identifies a plan, proposal or order that this task has been created in fulfillment of.

      Comment:

      Unclear what this really means. Is this where the DiagnosticRequest, Prescription, etc. request resource would be referenced? If so, the definition does not make that clear. If not, not sure what this intends to reflect.

      Summary:

      Clarify meaning of Task.basedOn

            Assignee:
            Unassigned
            Reporter:
            Michelle Miller
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: