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

Allow workflow-reason extension on Questionnaire

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R6
    • FHIR Infrastructure
    • Questionnaire
    • Hide

      Will define a 'standard' extension in the extensions list called "statusReason" 0..* with an initial context of "DomainResource" with a note that says "may only be used on resources with a 'status' element that do not already have a statusReason."  Will define an example binding on a new value set drawing from v3 ActReason containing these codes: HLEGAL, PATSFTY, EIE, RR.

      Requirements: Specifically introduced to support a reason for retiring a Questionnaire, but can be used much more broadly.  E.g. "Why is this encounter on hold?"  "Why is this specimen not available?"

      Show
      Will define a 'standard' extension in the extensions list called "statusReason" 0..* with an initial context of "DomainResource" with a note that says "may only be used on resources with a 'status' element that do not already have a statusReason."  Will define an example binding on a new value set drawing from v3 ActReason containing these codes: HLEGAL, PATSFTY, EIE, RR. Requirements: Specifically introduced to support a reason for retiring a Questionnaire, but can be used much more broadly.  E.g. "Why is this encounter on hold?"  "Why is this specimen not available?"
    • Brian Postlethwaite/Paul Lynch: 3-0-0
    • Enhancement
    • Compatible, substantive

    Description

      Knowledge artifacts such as Questionnaire sometimes need to be retired (.status = retired) and it is necessary to record the reason for the retirement. Similar to FHIR-41240, the workflow-reason extension seems like a good fit here but its scope of use does not include Questionnaire - would be great if the scope was expanded.

      Attachments

        Activity

          People

            Unassigned Unassigned
            vadim_peretokin Vadim Peretokin
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: