MedicationRequest requires notDoneReason

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Pharmacy
    • STU
    • MedicationRequest
    • Hide

      Changes to MedicationRequest" to align to Request logical model

      1. doNotPerform - add as modifier flag

      2. update reasonCode and reasonReference - to specify reason for prescribing or not prescribing

      Show
      Changes to MedicationRequest" to align to Request logical model 1. doNotPerform - add as modifier flag 2. update reasonCode and reasonReference - to specify reason for prescribing or not prescribing
    • Floyd Eisenberg/Jose Costa Teixeira: 14-0-0
    • Enhancement
    • Compatible, substantive
    • STU3

      MedicationRequest needs to accommodate the workflow to allow for indications why a medication 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 medications. 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: