Stream: implementers
Topic: ImmunizationRecommendation-target disease, no vaccine code
Dusica Bojicic (Dec 20 2016 at 01:28):
We are looking into representing immunisation registry records with FHIR, in particular representing the next immunisation due information, consisting of the “next immunisation due” and the due date. The content of “next immunisation due” is the target disease. The actual vaccine is not available.
We looked at ImmunizationRecommendation resource, which seems a good fit conceptually except that it is based upon the vaccineCode.
Any thoughts on which resource to use.
Lloyd McKenzie (Dec 20 2016 at 02:06):
I think the intention is that you'd use ImmunizationRecommendation. I suggest you raise your requirement as a change request using the "propose a change" link in the spec and/or by raising the question on their list server.
Igor Sirkovich (Dec 20 2016 at 02:41):
We are using ImmunizationRecommendation in Ontario. We bind vaccineCode to a VaccinePreventableDiseaseCode valueset, which our business team defined based on SNOMED CT disease codes.
Dusica Bojicic (Dec 20 2016 at 02:51):
We need to record the vaccine and target disease in the record of completed vaccinations, but only the target disease in the list of planned vaccinations.
Brett Esler (Dec 20 2016 at 03:29):
Suggest extension to ImmunizationRecommendation.protocol with element equivalent to http://build.fhir.org/immunization-definitions.html#Immunization.vaccinationProtocol.targetDisease perhaps 0..*
Dusica Bojicic (Dec 20 2016 at 03:40):
ImmunizationRecommendation is still based on vaccineCode which we don't have. I will add a change request but in case it is not resolved on time for us what are the other options? Using some generic resource like Task?
Brett Esler (Dec 20 2016 at 03:53):
maybe CarePlan ?
Richard Townley-O'Neill (Dec 20 2016 at 23:58):
GForge issue raised http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12484
Stephen Chu (Dec 21 2016 at 00:19):
Consider this use case: an immunization record that contains (1) a record of vaccination given, plus (2) information about the next due (date of) vaccination and the targeted infectious disease. The immunizationRecommendation supports (2). That leaves (1) that needs the use of immunization resource. This makes implementation overly cumbersome. Would it be more simple to include a Backbone element in the immunisation resource to support (2)? Or the immunization resource contains a reference to the immunizationRecommendation resource?
Last updated: Apr 12 2022 at 19:14 UTC
