ImmDS + HALO - Agenda

Meeting

ImmDS + HALO

Date

Thursday, October 1, 2026

Time

3:00 PM America/New_York

Status Closed

Meeting Information

All ImmDS + HALO Meetings

Meeting between AIRA and HLN to support implementation of a new CDS solution that realizes the new ImmDS + HALO standard.

Chair: Nathan Bunker

Attendance

Haven't signed in for this meeting yet?

Topic / Time	Agenda	Presenter(s)
Welcome and Introductions Current topic 3:00 PM–3:05 PM 5 min	Welcome Introductions Notes Discussing before the meeting starts InteropHub. There is a lot of detail, need to have umbrella topics. If a topic gets added, how do I know it gets added. For folks engaged in multiple things spending less time on administration and have having less choices is a good things. Trying to figure out each group is relevant is very hard. Explaining what happens when you pick or don't pick a sub group would be helpful. Looking at the agenda.	Nathan Bunker
Immunization CDS (ImmDS + HALO) Current topic 44 following · 3 here today 3:05 PM–3:20 PM 15 min	Update on progress from HLN and AIRA Review of discussions from HL7 WGM Notes Update on what is going on with software Next release of ICE will have the target disease adjustments in it FHIR-58952 in particular, and others as well. Should HLN should move forward with the current design to remove the extensions? The more stable we can make the API then have to introduce the changes later on. The extensions, and do it a different way, it's a bigger lift. Other strategy was to keep it in extensions and then when it was approved then replicating it. Leaving the extensions in. Would this be an issue if a non-normative message came out then would this a problem for someone with a normative message. Don't know enough about the client side to know what HLN should do. Already facing the problem of being outside the incubator with the first change of 0..1 going to 0..* for disease. Stay conformant with the incubator or fix it? Can this be fast tracked? Anyone implementing this will have to deal with a non-standard interface today. HLN is feeling that getting this as close to what the final is. Didn't want to do a split out just to remain conformant. Maybe we can go faster, then we know that it's going there. Do the incubators just live in build.fhir.org? Do you just use the latest build? Will ask this at the Public Health WG meeting in the next hour. Outcomes Will ask this at the Public Health WG meeting in the next hour.	Nathan Bunker Chris Sorenson
FHIR Open Tickets Current topic 19 following · 2 here today 3:20 PM–3:55 PM 35 min	Structural/definitional FHIR-58952 - MULTIPLE TARGET DISEASES IN IMMUNIZATION EVALUATION FHIR-58655 - ImmunizationRecommendation VaccineCode has a conflated definition FHIR-59485 - ImmunizationEvaluation: Change 'series' from string to CodeableConcept FHIR-59486 - ImmunizationRecommendation: Change 'series' from string to CodeableConcept Handled in ICE FHIR API extensions FHIR-57247 - ImmunizationRecommendation.authority needs to be moved under recommendation backbone element FHIR-56990 - ImmunizationRecommendation.authority cardinality expansion FHIR-56989 - ImmunizationEvaluation.authority cardinality expansion FHIR-59487 - ImmunizationEvaluation: Add season FHIR-59488 - ImmunizationRecommendation: Add season FHIR-59489 - ImmunizationRecommendation: Add seriesDosesRemaining Other open questions *Option for recommendation-related URL: PlanDefinition, Library, Device, and Device Definition JIRA FHIR Tickets Notes Working on FHIR tickets. Comment from participant: The scenario I was considering is that there is a provider. Provider is using Authority A for a recommended influenza vaccine schedule and Authority B for a TB schedule. Patient 1 has received vaccinations for both influenza and TB. How is that represented? (can be addressed offline/different time and place) Another topic: How do we message at the technical level to share how the logic got to the answer. HLN software provides a URL for this. Maybe PlanDefinition, Library, DeviceDefinition. Device seemed to narrow but actually it's more broad. Probably more than a URL, maybe version number and data. PlanDefinition had some references to CDS. Action item is to do more investigation. The term needed is something like "clinical decision support rule that is backing the recommendation for a particular vaccine group". Need this at the recommendation backbone element. URL can be displayed as additional documentation Explains the logic that was used to make the recommendation Discussed 7 tickets that would be useful to move.	Erin Roche
Wrap Up Current topic 3:55 PM–4:00 PM 5 min	Next Steps Question about Call time, can we move earlier to allow for European participation? Notes Agreed to move to 10 am ET. Nathan will setup new call time. Outcomes Agreed to move to 10 am ET. Nathan will setup new call time.