3) The reason codes (http://hl7.org/fhir/R4/valueset-immunization-evaluation-dose-status-reason.html) are: adverse storage condition, cold chain break, expired lot, administered outside schedule, product recall. All of these (except administered outside schedule) aren't things that a CDS engine would return to the caller; it's something the caller would pass up to the CDS engine. So having this as a part of ImmunizationEvaluation does not make sense.
Suggestion #3: For things like storage conditions and recall, that information will typically be supplied by the caller as part of Immunization.subpotentReason. Expired or Outside of Scheduled can be determined by the CDS engine based on the patient history and other data. CDS engines may want to be more specific about the schedule issues (eg. given too soon, patient too young) which may be a problem if we provide a generic "out of schedule" code in an extensible value set. On 10/31/2019, the Public Health WG reviewed the value sets for Immunization.subpotentReason and ImmunizationEvaluation.doseStatusReason. We will come up with an extended set of values for the value set, drawing on experience from CDS engines and CDSi. We think we'll want to expand the "out of schedule" to be more specific.
http://jira.hl7.org/browse/fhir-24961
3) The reason codes (http://hl7.org/fhir/R4/valueset-immunization-evaluation-dose-status-reason.html) are: adverse storage condition, cold chain break, expired lot, administered outside schedule, product recall. All of these (except administered outside schedule) aren't things that a CDS engine would return to the caller; it's something the caller would pass up to the CDS engine. So having this as a part of ImmunizationEvaluation does not make sense.
Suggestion #3: For things like storage conditions and recall, that information will typically be supplied by the caller as part of Immunization.subpotentReason. Expired or Outside of Scheduled can be determined by the CDS engine based on the patient history and other data. CDS engines may want to be more specific about the schedule issues (eg. given too soon, patient too young) which may be a problem if we provide a generic "out of schedule" code in an extensible value set. On 10/31/2019, the Public Health WG reviewed the value sets for Immunization.subpotentReason and ImmunizationEvaluation.doseStatusReason. We will come up with an extended set of values for the value set, drawing on experience from CDS engines and CDSi. We think we'll want to expand the "out of schedule" to be more specific.
Overall: Persuasive with Mod