Possible synch conflics when updating the task.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • US Post Acute Orders (FHIR)
    • 0.3.0 [deprecated]
    • Orders & Observations
    • (NA)
    • Both Flow Diagrams
    • Hide

      Clarify the situations that may exist when updates occur to the Task and/or Orders (e.g. ServiceRequest, MedicationRequest, DeviceRequest) need to use the business status (need to clarify / define the exact values) and reason for change to indicate what needs to be done (such as retrieve orders and determine the specific updates that have been requested).

      Indicate which task statuses prohibit further updates. (cancel, completed)

      Show
      Clarify the situations that may exist when updates occur to the Task and/or Orders (e.g. ServiceRequest, MedicationRequest, DeviceRequest) need to use the business status (need to clarify / define the exact values) and reason for change to indicate what needs to be done (such as retrieve orders and determine the specific updates that have been requested). Indicate which task statuses prohibit further updates. (cancel, completed)
    • Bob Dieterle / Marti Velezis : 4-0-8
    • Clarification
    • Compatible, substantive

      Possible synch conflics when "Ordering Provider System" updates the task.

      The Rendering provider can update the task while the Ordering provider is sending the updated task.

      I suggest the ordering provider sending a new task to cancel, or update the task. See more info at https://www.hl7.org/fhir/workflow-ad-hoc.html item 12.7.6.4

      Existing Wording:

      In both diagrams. In the first one is in "Get Task (to make sure we are acting on the most current information)".

            Assignee:
            Unassigned
            Reporter:
            Ricardo Quintano
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: