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

Should statusReason be mustSupport?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive
    • 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

      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.
    • Resolution Vote:
      Bob Dieterle / Jay Lyle : 9-0-2
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive

      Description

      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)

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: