Should statusReason be mustSupport?

XMLWordPrintableJSON

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

      Make Task.statusReason mustSupport (cardinality remains 0..1) and Task.statusReason.text is required (cardinality 1..1) and include usage notes to define when the task.statusreason mustsupport should apply.

      Show
      Make Task.statusReason mustSupport (cardinality remains 0..1) and Task.statusReason.text is required (cardinality 1..1) and include usage notes to define when the task.statusreason mustsupport should apply.
    • Bob Dieterle / Jay Lyle : 9-0-2
    • Enhancement
    • Compatible, substantive

      If your purpose is to track the solicitation for fulfillment and managing that, don't you want to require support for capturing the reason why the Task is rejected or failed (or, less likely, put on hold)?

      (Comment 131 - imported by: Robert Dieterle)

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

              Created:
              Updated:
              Resolved: