Need to figure out how to link Tasks in a sequence

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Task
    • Hide

      Will define a standard extension that has a target of ANY (could be a Request or could be an Event) 0..* with a name of "workflow-followOnOf" with a definition "Indicates a preceding action that provides context for the current action"

      requirements "Allows linking a previous action (whether successful or failure) whose existence helps to either justify or demonstrate the appropriateness of the current action.  Possible examples:

      • Pointing to a "first line" drug prescription when ordering a second-line drug. 
      • Lodging a formal disagreement after the rejection of a request for correction.
      • Physio therapy order referencing what therapy(ies) had already been done"
      Show
      Will define a standard extension that has a target of ANY (could be a Request or could be an Event) 0..* with a name of "workflow-followOnOf" with a definition "Indicates a preceding action that provides context for the current action" requirements "Allows linking a previous action (whether successful or failure) whose existence helps to either justify or demonstrate the appropriateness of the current action.  Possible examples: Pointing to a "first line" drug prescription when ordering a second-line drug.  Lodging a formal disagreement after the rejection of a request for correction. Physio therapy order referencing what therapy(ies) had already been done"
    • Jose Costa Teixeira/Chandrakant Bhoslay: 8-0-0
    • Enhancement
    • Non-substantive

      Patient Empowerment is planning to leverage Task to represent both requests for change of a record as well as requests to log an official disagreement with content in a record.  The actual workflow can involve a request for change being submitted, then rejected, then a new task requesting the same change, but with more detail that addresses the initial rejection, possibly being rejected again (repeat until the patient succeeds or has no new info to provide) after which they can submit a task asking for the logging of formal disagreement.  There's a need to link all of these Tasks together.  We've contemplated using 'reason' to link "request for record of disagreement" to "request for correction", but that wouldn't work for tying subsequent requests for correction.  Should we have a 'replaces' relationship?  Something else?

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: