Open recipe-ruben opened 1 week ago
Do we need those attributes then? The dispenseRequest is for the logistics of the dispense. We should not redefine it for clinicals aspects "duration of treatment" . We can discuss what is the intent but we should only constrain the meaning of the elements.
On Sun, Sep 8, 2024 at 8:24 PM recipe-ruben @.***> wrote:
Currently, in the prescription model, we can find the following properties:
- dispenseRequest 0..1 Class "Dispense Request or authorization for the prescribed medication"
- dispenseInterval 0..1 Duration "Minimum period of time between dispenses"
- quantityPerDispense 0..1 SimpleQuantity "Amount of medication to supply per dispense"
Currently it is only possible to prescribe one product per electronic prescription. Therefore, multiple dispenses for a single prescription are not allowed. As long as the legislation doesn't change, it seems best to adjust this to:
- dispenseRequest 0..1 Class "Dispense Request or authorization for the prescribed medication"
- dispenseDuration 0..1 Duration "Duration of the treatment"
- quantityForDispense 0..1 SimpleQuantity "Amount of medication to supply for this dispense"
— Reply to this email directly, view it on GitHub https://github.com/hl7-be/medication/issues/215, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3HUUEA7GQB4GSQBJLGGSDZVSI4RAVCNFSM6AAAAABN3GOMT6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTENJRGI2DGMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Currently, in the prescription model, we can find the following properties:
Currently it is only possible to prescribe one product per electronic prescription. Therefore, multiple dispenses for a single prescription are not allowed. As long as the legislation doesn't change, it seems best to adjust this to: