Stream: implementers
Topic: Immunization.date
Dusica Bojicic (Sep 12 2017 at 21:38):
I have a query about the intent of Immunization.date. The definition suggests it is the date of administration or the date of intended administration.
We have a need to record “date cancelled”, which is the date on which the intended administration was cancelled and may or may not be the same as the date of intended administration.
Mapping into CDA suggests that Immunization.date is the “date administered” if notGiven=false and “date cancelled” if notGiven=true. Is this the real intent of the Immunization.date? Or do we need to create an extension to cater for the “date cancelled”?
Brett Esler (Sep 13 2017 at 04:33):
A question about cancelled date - implies a cancellation action at a point in time; is this the meaning needed? or is this really just a date that an Immunisation was not given. i.e can cancellation date and intended vaccination date be different values
Brett Esler (Sep 13 2017 at 04:36):
seems Immunisation is a record of either a vaccination that occurred or a vaccination that did not occur on a date; so there is no planning of a future Immunisation here so can't cancel a planned event only not give on a date that it may have been given...
Brett Esler (Sep 13 2017 at 04:37):
to me this means cancelled date is really a not given date so should be Immunisation.date no extension..
Richard Townley-O'Neill (Sep 13 2017 at 04:59):
Maybe the definition of Immunisation.date needs improvement. It is
Date vaccine administered or was to be administered.
maybe change it to something like
Date vaccine was administered or administration was cancelled.
Brett Esler (Sep 13 2017 at 05:00):
It is a semantics question on 'cancelled' - to me 'cancelled' implies intent which is not recorded here.
Brett Esler (Sep 13 2017 at 05:01):
However some intent is implied i.e. event did not occur on date i expected it to
Brett Esler (Sep 13 2017 at 05:02):
but do not record intended to vaccinate on a date and cancelled it on another date - i.e this is a record of past occurence
Brett Esler (Sep 13 2017 at 05:03):
any of the resource authors able to comment?
Jose Costa Teixeira (Sep 13 2017 at 07:56):
Hi. I am not an author of this but I recall some discussions and this text: If systems need to use a MedicationAdministration resource to capture vaccinations for workflow or other reasons, they SHOULD also expose an equivalent Immunization instance.
Jose Costa Teixeira (Sep 13 2017 at 08:00):
IMO, if you need to capture workflow stuff like canceled, not given, you are better off doing so with clear events or requests.
Is the information you require in immunizationRecommendation?
Jose Costa Teixeira (Sep 13 2017 at 08:00):
in medication that is what would happen - request says when it should be given, administration says when it was given (or not)
Ewout Kramer (Sep 14 2017 at 21:44):
@Joginder Madra or @Eric Larson might be able to help out?
Joginder Madra (Sep 14 2017 at 21:50):
The use cases we looked at were fairly basic - the date the vaccine was administered or the date the vaccine was refused - i.e. was not given.
Abbie Watson (Oct 10 2017 at 21:38):
Seems like there's a need to harmonize the date, assertedDate, onsetDate, effectiveDate, performedDate, and adminsiteredDate fields across all the FHIR resources. Would be really great if FHIR could define an Interface pattern, where any of those fields are legitimate across any resource. Maybe refactor them onto BaseResource or DomainResource?
Grahame Grieve (Oct 11 2017 at 15:48):
we won't refactor them to a base resource, but we do have this: http://hl7.org/fhir/w5.html, and I intend to make this a formal interface pattern for R4
Eric Haas (Oct 11 2017 at 16:43):
we mapped them to the event pattern as well
Abbie Watson (Oct 11 2017 at 16:58):
we won't refactor them to a base resource, but we do have this: http://hl7.org/fhir/w5.html, and I intend to make this a formal interface pattern for R4
Nice! Meteor on FHIR will happily use these as a base for our Resource objects, and code these up as an interface. Will be super useful for timelines and other visualizations. Thank you much!
Last updated: Apr 12 2022 at 19:14 UTC
