Need way to link patient correction tasks

XMLWordPrintableJSON

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

      We will define a new 'workflow event' extension with an initial context of Task (and propose adding it to other event resources)

      name: workflow-followOn
      cardinality: 0..*
      definition: Points to a preceding event within a workflow that was a prerequisite for or provides other justification for the current action.

      rationale: This is distinct from 'reason'.  The reason why the action is necessary is distinct from pointing to prerequisites or preceding workflow steps that allow or necessitate the current action.  The prerequisites could be driven by a formal protocol (e.g. PlanDefinition), but that's not necessary for this to be relevant.

       

      Will continue discussion on a future call

      Show
      We will define a new 'workflow event' extension with an initial context of Task (and propose adding it to other event resources) name: workflow-followOn cardinality: 0..* definition: Points to a preceding event within a workflow that was a prerequisite for or provides other justification for the current action. rationale: This is distinct from 'reason'.  The reason why the action is necessary is distinct from pointing to prerequisites or preceding workflow steps that allow or necessitate the current action.  The prerequisites could be driven by a formal protocol (e.g. PlanDefinition), but that's not necessary for this to be relevant.   Will continue discussion on a future call

      The patient empowerment work group plans to use Task to represent requests for correction to a record as well as requests to log a formal disagreement with respect to a record.  In the workflow, it's possible for a request task to be submitted, then rejected, then have a new correction submitted that addresses the concerns from the previous rejection, (repeat as necessary) followed by a Task to log a formal disagreement.  There's a need to link all these tasks together into a chain so that it's clear they're all part of one "conversation".  It's possible to use 'reason' to link the "logging of disagreement" to the most recent "request for change", but that doesn't work so well for linking the various requests for change to each other.  Should we have a 'replaces' relationship?  Something else?  (Note that there is a standard replaces extension, if that's what we deem to be most appropriate.)

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

              Created:
              Updated:
              Resolved: