2015May core #1075 - Need to capture reason request not performed

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • Communication
    • Hide

      To the Event pattern:

      • Will add "notDone" boolean 0..1 modifier
      • Will add "reasonNotDone". (Will add a design note that this is a separate element because of the need for distinct vocabulary binding)

      Will add usage notes indicating that the "not done" is for situations where there's a need for a specific statement in the record about something not being done, not just for workflow purposes.

      Show
      To the Event pattern: Will add "notDone" boolean 0..1 modifier Will add "reasonNotDone". (Will add a design note that this is a separate element because of the need for distinct vocabulary binding) Will add usage notes indicating that the "not done" is for situations where there's a need for a specific statement in the record about something not being done, not just for workflow purposes.
    • Hans Buitendijk/Jose Costa Teixeira: 9-0-0
    • Enhancement
    • Compatible, substantive
    • DSTU1 [deprecated]

      Existing Wording: reasonNotPerformed/reasonRejected

      Proposed Wording: Yes

      Comment:

      We probably need a standard extension on *Request to support capture of reasons for which the request was not performed. See communication.reasonNotPerformed in QUICK profile.

            Assignee:
            Unassigned
            Reporter:
            Keith W. Boone
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: