Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-31202

Task.owner should be mustSupport

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • US SDOH Clinical Care (FHIR)
    • 0.1.0 [deprecated]
    • Patient Care
    • Withdrawn
    • SDOHCC Task Base 1 [deprecated]
    • Hide

      make task.owner mustsupport to facilitate the ability to determine who owns the task.  Explain why we are leaving it as optional (to allow a task to be created without an owner and then have the ability for one of a potential group of performers elect to "own" the task)

      Show
      make task.owner mustsupport to facilitate the ability to determine who owns the task.  Explain why we are leaving it as optional (to allow a task to be created without an owner and then have the ability for one of a potential group of performers elect to "own" the task)
    • Bob Dieterle / Jay Lyle : 9-0-2
    • Enhancement
    • Compatible, substantive

    Description

      Task.owner is who you're asking to fulfill the ServiceRequest. It's alwo how fillers find Tasks that are assigned to them. (Can't assume that the Task.owner is the same as the ServiceRequest.performer - and ServiceRequest.performer is optional.) You might not want to make this mandatory if you want to support a use-case where an 'open' reqeust for fulfillment is set an anyone capable of filling the order can claim it and then execute. If that's not something you want to support, then feel free to make it mandatory

      (Comment 135 - imported by: Robert Dieterle)

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: