FHIR Chat · MedicationRequest.dosageInstruction.asNeededCodeableConcept · implementers

Stream: implementers

Topic: MedicationRequest.dosageInstruction.asNeededCodeableConcept


view this post on Zulip Weiyu Zhang (Nov 16 2021 at 04:07):

Hi all,
I've been looking at the best way to map our internal medication model to MedicationRequest, and had a quick question for the group on the best way to represent a single med order with multiple PRN reasons (e.g. take as needed for nausea and vomiting). Our current solution is to model this as a single MedicationRequest resource with multiple dosageInstruction repetitions (each with an asNeededCodeableConcept representing one of the PRN reasons) due to the 0..1 cardinality constraint on Dosage.asNeededCodeableConcept, but we're worried that may cause some confusion about the total number of prescribed doses. Do you have any recommendations/suggestions on how to represent such a MedRequest?
Thanks!

view this post on Zulip Lloyd McKenzie (Nov 16 2021 at 04:48):

@Melva Peters

view this post on Zulip Isaac Vetter (Nov 16 2021 at 14:43):

And further, is there a specific reason why the med resources have specifically limited Dosage to a single PRN reason?

view this post on Zulip Melva Peters (Nov 16 2021 at 16:14):

I can't think of a reason why the cardinality is 0..1. I would suggest you add a Jira Issue and request a change with your specific use case.

view this post on Zulip Weiyu Zhang (Nov 17 2021 at 01:27):

Sounds good, thanks! Submitted as https://jira.hl7.org/browse/FHIR-34325

view this post on Zulip Arianne van de Wetering (Nov 30 2021 at 11:14):

Having more than one as needed concept does raise the question: may the medication be taken when at least one criterium is true or may it only be taken when all are true?

view this post on Zulip Marijke van Geijn (Nov 30 2021 at 12:11):

I noticed the valueset 'Medication as needed reason' contains combinations like this: 2919008 Nausea, vomiting and diarrhea. This captures it in a single PRN reason.


Last updated: Apr 12 2022 at 19:14 UTC