Three followups on this one, @lloyd.
Medication Administration has two properties for reasons… reasonCode and reasonReference. We’re trying to figure out where we should capture the nuance of whether something is a symptom (coughing, wheezing, etc.) or a trigger (allergies, smoking, etc.). If we try to use just reasonCode with a custom codeset, CodeableConcept really doesn’t allow for that nuance unless we hack it into the text (e.g. “symptom- coughing”). If we use reasonReference, it seems to be a better fit as the “type” on the reference would imply a symptom (Condition) or trigger (Observation). @lloyd, which way were you thinking?
Second, regarding dosage. Am I correct that dosage.dose would specify the number of doses/units taken, not the quantity of medication taken? The example on the site for Alprazolam 0.25mg Oral Tablet seems to indicate this (dosage.dose indicates 1 tablet administered, not 0.25mg). In this case, we would be recording the # of puffs from the inhaler, and the medication reference or dosage.text would be where the amount of medication per puff would be indicated.
Finally, asthma medications can either a rescue medication or a controller medication. While I assume this could be implied by the medication involved, it’s currently being explicitly provided to us as an attribute. Assuming we need to capture this explicitly, where would you map it? reasonCode doesn’t make as much sense to me, since this is really an attribute of the medication not an attribute of the situation. A custom use of “category” might work, or we could put something in “notes” to reflect it. Thoughts?
Thanks for your help.