DeviceRequest fails to allow reason for not requesting

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Orders & Observations
    • STU
    • DeviceRequest (was DeviceUseRequest)
    • Hide

      currently exists as an extension and currently no need to be part of core resource.

      Show
      currently exists as an extension and currently no need to be part of core resource.
    • Eric Haas/Dan Rutz: 9-0-1
    • Enhancement

      DeviceRequest needs to accommodate the workflow to allow for indications why a device is not recommended (i.e., .intent = plan) or not ordered (i.e., .intent = order). Clinical decision support artifacts address placing orders or recommmending activities to patients, including use of devices (some implantable, some used directly on the body without implantation). The CDS artifacts may indicate rationale to avoid following the recommendations such that the provider (or patient) can select a valid reason and save that rationale for failing to comply in the record. Such a .notDoneReason metadata element can then inform the CDS event-condition-action rule to avoid re-alerting the provider in the future (or to "snooze" the alert to a later time).

            Assignee:
            Unassigned
            Reporter:
            Floyd Eisenberg
            Floyd Eisenberg
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: