Stream: Medication
Topic: Dosage.doseAndRate multiplicity
Olivier Boux (Oct 05 2021 at 09:03):
Are there use cases where the multiplicity of .doseAndRate makes sense?
If there are two or more, which one to apply as they have the same .timing ?
Lloyd McKenzie (Oct 05 2021 at 14:09):
@Melva Peters
Christof Gessner (Oct 06 2021 at 06:27):
original discussion on the topic: https://jira.hl7.org/browse/FHIR-14212
Olivier Boux (Oct 06 2021 at 18:10):
Thank you very much.
From this initial discussion, I note that multiplicity SHALL be considered as an alternative description of the same dose.
I had misinterpreted the "calculated" value of the value set associated with the type element. It should be understood in the sense of "theoretical value" from which the "real value", type "ordered", is calculated and then rounded and finaly ordered by the prescriber. Am I right ?
I could not rely on the 40 examples because none of them illustrates this use case, even though prescription 0309 would have been suitable. Update it ? Or add an example ?
Melva Peters (Oct 06 2021 at 22:13):
@Olivier Boux good idea to add an example. Can you add a Jira Issue so that we can add that? Thanks
François Macary (Oct 14 2021 at 07:49):
Christof Gessner said:
original discussion on the topic: https://jira.hl7.org/browse/FHIR-14212
This ticket (on STU3) concluded with this statement "the value set and binding" need to be determined. As of today, in R5 the ValueSet DoseAndRateType has only two values "calculated" and "ordered". However, the binding is "example", which seems a bit strange to me, for a ValueSet which is part of the base standard, used to provide the meaning of a type of dose and rate. Does this mean that the value set is not really determined yet? OR should we change the binding to "required"?
François Macary (Oct 14 2021 at 08:19):
Melva Peters said:
Olivier Boux good idea to add an example. Can you add a Jira Issue so that we can add that? Thanks
Done: 34129
Lloyd McKenzie (Oct 14 2021 at 12:24):
@Melva Peters
Jean Duteau (Oct 14 2021 at 15:08):
It will never be required because we don't have a value set that completely covers the space of this element and that is accepted internationally. We did create an example binding and the value set has two values in it to indicate the kinds of code. If you have additional codes you'd like added to the value set to give further guidance of the kinds of codes that could be used here, we can certainly add more.
Last updated: Apr 12 2022 at 19:14 UTC
