Stream: implementers
Topic: Medication Date
Grahame Grieve (Nov 14 2016 at 01:32):
GF#12148 - requests common search parameters across resources. One of the requests is for date across medication resources - but the medication resources do not have any common date related search parameters. I would suggest that there should be a 'date' on each of them.
- MedicationRequest datewritten rename to date
- MedicationAdministration effective-time - add date with same definition
- MedicationDispense - whenhandedover rename to date
- MedicationStatement - add date = MedicationStatement.dateAsserted
@Melva Peters @Michelle (Moseman) Miller @John Hatem @Scott Robertson
Richard Townley-O'Neill (Nov 14 2016 at 02:19):
Some ideas:
1 - I would have thought that when comparing MedicationStatements with MedicationAdministrations and other medication resources, the date of interest was the the 'date of medication use', not the 'date of assertion'. So MedicationStatement's search date should be based on effective.
2 - This would be an opportunity to align the names of MedicationAdministration.effectiveTime[x] and MedicationStatement.effective[x].
3 - The information that can be held by the combined data elements effectiveDateTime and effectivePeriod can also be held by two different data elements date and duration. That design would give a common date data element for searching without adding an extra data element just for searching.
Grahame Grieve (Nov 14 2016 at 02:20):
I'm not proposing new elements, just new search parameters
Richard Townley-O'Neill (Nov 14 2016 at 02:25):
That stops 3. How about 1?
2 still bugs me.
Grahame Grieve (Nov 14 2016 at 02:30):
you're probably right about 1 and I'm not sure about 2
Lloyd McKenzie (Nov 14 2016 at 19:58):
+1 for changing effectiveTime[x] to effective[x]
Michelle (Moseman) Miller (Nov 15 2016 at 14:28):
FYI - In an offline (email) discussion with Pharmacy co-chairs, I think there is informal agreement to make these consistent by renaming effectiveTime to effective. (For historical context, this was discussed previously in Pharmacy as part of GF#10036, which was initially resolved to make them consistent using effectiveTime[x], but that resolution was later challenged due to the ugliness of having effectiveTimeDateTime as a choice of types. Using effective[x] as the name is ideal.)
Mikael Rinnetmäki (Apr 02 2019 at 12:53):
Just noticed that the search parameter for MedicationAdministration is called effective-time, whereas 17 other resources use the parameter date (https://www.hl7.org/fhir/searchparameter-registry.html#clinical-date). I tried to search for the reasoning here in Zulip and this was the only thread I was able to find close to the subject. I still didn't get why the MedicationAdministration resource should be different from the others in this regard.
John Silva (Apr 02 2019 at 13:30):
@Mikael Rinnetmäki -- good question. I'd add one more to this (maybe it's already been discussed in the Pharmacy committee): What does 'effective-time' mean (no matter what it's called) when you have an infusion with both a start and end time (effectivePeriod) for the administration? Do MedAdmin's need a different query parameter or an additional one to handle this? [I don't see a search parameter for effectivePeriod]
Mikael Rinnetmäki (Apr 02 2019 at 14:17):
@John Silva at least Observation clarifies the search parameter date to cover both effective[x] alternatives
dateObtained date/time. If the obtained element is a period, a date that falls in the period
John Silva (Apr 02 2019 at 17:23):
@Mikael Rinnetmäki -- Sounds like there should be a 'date' search for MedAdmin then too. Do we need to enter a GForge for this to be considered?
Mikael Rinnetmäki (Apr 03 2019 at 04:57):
Added 20649.
Mikael Rinnetmäki (Apr 30 2019 at 06:19):
... which seems to now have a resolution:
Agree that we will change the name of the parameter to "date"
Last updated: Apr 12 2022 at 19:14 UTC
