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

Why priority on both ServiceRequest and Task?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive with Modification
    • Specification:
      US SDOH Clinical Care (FHIR)
    • Raised in Version:
      0.1.0
    • Work Group:
      Patient Care
    • Related Artifact(s):
      SDOHCC Task Base 1
    • Grouping:
    • Resolution Description:
      Hide

      Provide guidance on the use of the task.priority to distinguish urgent tasks (e.g. need shelter immediately) from routine tasks.  No change needed to element (stays mustSupport)

      Show
      Provide guidance on the use of the task.priority to distinguish urgent tasks (e.g. need shelter immediately) from routine tasks.  No change needed to element (stays mustSupport)
    • Resolution Vote:
      Bob Dieterle / Jay Lyle : 9-0-2
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      Do you need it in both places? What does it mean if they differ? Suggest that it belongs on the ServiceRequest, not the Task

      (Comment 133 - imported by: Robert Dieterle)

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: