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

Consider Updating Dosage to Allow Multiple PRN Reasons

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive
    • Medium
    • FHIR Core (FHIR)
    • R4
    • Pharmacy
    • MedicationDispense
      MedicationRequest
      MedicationStatement
    • Dosage
    • 11.10.0.1
    • Hide

      Reverted previous resolution: Persuasive made 2022-01-18 00:00:00.0 with vote Daniel Zhang / Margaret Weiker: 10-0-0//(Impact: Compatible, substantive; Category: Enhancement; Version: null)//Agree - will change the AsNeeded choice and provide 2 separate elements

      Invariant - AsNeededFor can only be set if AsNeeded is empty or true

       

      This change will be made for R5 only as we can not open R4 for changes

      Show
      Reverted previous resolution: Persuasive made 2022-01-18 00:00:00.0 with vote Daniel Zhang / Margaret Weiker: 10-0-0//(Impact: Compatible, substantive; Category: Enhancement; Version: null)//Agree - will change the AsNeeded choice and provide 2 separate elements AsNeeded - 0..1 - DataType = Boolean AsNeededFor - 0..* - DataType=CodeableConcept -example binding to  http://build.fhir.org/valueset-medication-as-needed-reason.html Invariant - AsNeededFor can only be set if AsNeeded is empty or true   This change will be made for R5 only as we can not open R4 for changes
    • Daniel Zhang / Margaret Weiker: 10-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      Providers can specify multiple PRN reasons/indications on medication orders in our system (e.g. take as needed for nausea and vomiting). Currently, there's not a great way to represent multiple PRN reasons in the Dosage datatype/in MedicationRequest.dosageInstruction (and equivalents). While the dosage.asNeededBoolean can convey some detail, the reasons themselves are hard to transmit clearly.

       

      We've looked at multiple options:

      1) Multiple dosageInstruction repetitions, each with an asNeededCodeableConcept representing one of the reasons - this may cause confusion as it's unclear what dose + timing specified in each Dosage element is for/needs agreement on what dose + timing specified in each Dosage element is for (i.e. is it every 6 hours as needed for nausea and also every 6 hours as needed for vomiting (two doses allowed every 6 hours), or every 6 hours as needed for nausea or vomiting (one dose allowed every 6 hours)).

       

      2) Multiple MedicationRequest resources, each representing a PRN reason - similar confusion about what the dose + timing is for.

       

      3) New 0..* codeableConcept element representing PRN reasons (either in place of or in addition to asNeededBoolean) - this seems like the most straightforward option (and easiest for backporting to previous versions as extensions).

      Attachments

        Activity

          People

            Unassigned Unassigned
            weiyuzh Weiyu Zhang
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: