Relationship between Tasks and orders (particularly .basedOn)

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • US Post Acute Orders (FHIR)
    • 0.3.0 [deprecated]
    • Orders & Observations
    • (profiles)
    • Hide

      will give example of situation where order includes both a DeviceRequest and a MedicationRequest (e.g. infusion pump and pain killer) that should be  tracked as two parts of one order (e.g. it is not appropriate to fill only one part of the order if placed with a supplier that fill both.

      Show
      will give example of situation where order includes both a DeviceRequest and a MedicationRequest (e.g. infusion pump and pain killer) that should be  tracked as two parts of one order (e.g. it is not appropriate to fill only one part of the order if placed with a supplier that fill both.
    • Bob Dieterle / Marti Velezis : 11-0-6
    • Clarification
    • Non-substantive

      The PAO-Task profile allows .basedOn to repeat. What is the use case where this would happen? Given that each Task, can only "focus" on a single request resource, would .basedOn ever repeat? I'm assuming that there should be a Task for each order being sent (even if multiple are sent in a single message bundle). Please clarify the relationship between Tasks and Request resources.

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: