We’re working on a feature to display medication side effects to clinicians (in the Order Form) and dispensers (in the Dispense Prescription panel) during the pharmacy workflow.
Before we start building, I wanted to check if anyone has done something similar or knows of existing modules/approaches we could leverage.
What we need:
Display side effects for medications in the patient order form and dispensing details.
Classify side effects as “common” or “severe/unusual.”
A way for admins to manage/update this side effect list (as it will grow/change over time).
A configuration setting to toggle the visibility of these side effects specifically for the dispenser view.
Questions:
Does MRS have any built-in support for drug metadata/attributes like this?
Are there existing modules (or work-in-progress) that handle drug information/side effects?
For the data model, would you recommend extending the Drug entity, using Concept mappings, or creating a dedicated module?
Thanks @ibacher for the feedback. To wrap up the architectural design, I have two more technical questions:
Should we link the side effects to the Drug entity (the specific product) or to the Concept (the active ingredient)? What’s the recommended approach here?
Since we gonna build a new module, does it make sense to map this data to FHIR ClinicalUseDefinition resource? Or is there anything else you would recommend for clinical metadata?
I think that requires the opinion of a pharmacist or practitioner and that it may depend on whatever data source is being used to populate the side-effect information and how it structures data. My guess is that concept-level is ok as long as combined medications are represented via a separate concept, but that’s just a guess.
That would be the right resource to use. It probably makes sense to implement in FHIR, but heavily depends on how you’re intending to query it.