Stream: implementers
Topic: current-medications
René Spronk (Jul 16 2018 at 09:38):
Why was $current-medications not modeled as an operation on Medication* resources, but as an operation on List ? Has the design rationale behind this been documented anywhere ?
(In our FHIR training courses something like $current-medication is a good example for an operation on the Med* resources)
Grahame Grieve (Jul 16 2018 at 12:23):
where is it an operation on list?
René Spronk (Jul 16 2018 at 12:57):
http://build.fhir.org/list-operation-find.html
Grahame Grieve (Jul 16 2018 at 13:00):
ok so finding the list is an operation.
Grahame Grieve (Jul 16 2018 at 13:00):
but the list itself is actually a List resource - that makes things explicit as opposed to implicit (as it would be in an operation)
René Spronk (Jul 16 2018 at 13:01):
So to rephrase: why a List/$find with $current-medications as a name parameter, instead of a $current-medications operation on a Med* resource ? The latter could also return a List resource
René Spronk (Jul 17 2018 at 06:43):
@Lloyd McKenzie ? I'm looking to understand the rationale for dealing with this one way or the other. Currently I see no real benefit in specifying some special mechanism which only applies to certain 'current' Lists. I guess there must be added value above and beyond a simple operation (which returns a list) on a Med* resource. What is that benefit ?
Jose Costa Teixeira (Jul 17 2018 at 09:04):
very short and possibly out of context: I think "current" is a distracting word, other than that i think it makes sense to have this on List.
Jose Costa Teixeira (Jul 17 2018 at 09:05):
you can ask for a "this person's medication prescriptions" on the medrequest resource, but you would typically not ask for a list of dispenses on that resource, right? for a list of dispenses, you would have a list of dispenses.
Jose Costa Teixeira (Jul 17 2018 at 09:06):
since we do not know if a list will contain requests, dispenses, etc then "a patient's medication list" seems more part of a list,
even if the other resources can have an operation to get a list.
Jose Costa Teixeira (Jul 17 2018 at 09:06):
the definition of "current" is local, context-sensitive.
Jose Costa Teixeira (Jul 17 2018 at 09:07):
ie different implemetnations will define "current meds" differently - one will bring prescriptions that the end date is in the future.
Another implementation will bring prescriptions and dispenses plus medStatements for the last 6 months.
and another will bring the dispenses for the last year
Jose Costa Teixeira (Jul 17 2018 at 09:11):
so it seems to make sense to have this in List
Lloyd McKenzie (Jul 17 2018 at 13:38):
A given system might have numerous List instances of medications - admtting meds and discharge meds from numerous encounters, including data forwarded from other systems, different med lists for tracking meds of interest in different situations. The "$current" operation is intended to be the means to find what the EMR considers to be the "authoritative" med list - the presumption being that the EMR has such a thing and knows how to find it.
John Moehrke (Jul 17 2018 at 13:50):
so given this discussion about current lists http://build.fhir.org/lifecycle.html#current
Last updated: Apr 12 2022 at 19:14 UTC
