ImmDS + HALO - Agenda

Meeting

ImmDS + HALO

Date

Thursday, September 17, 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
Immunization CDS (ImmDS + HALO) Current topic 44 following · 4 here today 3:05 PM–3:55 PM 50 min	Project Updates & Next Steps * PSS Status: Review current progress and upcoming milestones * Discussion with CDS Work Group at HL7 meeting * Update on Step Into CDSi Follow-Up on Open Issues * Schedule Authority Placement & Cardinality: FHIR-56989; FHIR-56990; FHIR-57247 * Vaccine Groups / Target Disease: FHIR-58655 New Discussion Topics * Outputs handled via extensions: * Season selection (evaluation and recommendation) * Series selection (evaluation and recommendation) * Number of doses remaining (recommendation) * Contextual Condition Code Hosting & Registration: Status update on registering, publishing, and hosting CDSi observation codes with IVCI Notes Went to Patient Care and they were in support of what we were doing Asked about PSS, we don't need to do this. Public Health was not concerned about scope change and PSS is already universal. There was concern about going to FHIR r6. We want to clean up extensions on r4. Feeling like we need to push back and advocate for r6. The people who are going to use this that this r4 or r6 isn't going to be barrier. This is leading edge. The target for implementers is more limited, not to every system. Daryl will be at the HL7 WGM next week. Discussion will be held Wednesday Q2 at CDS and also at Tuesday Q3 for the Immunization Roundtable. Eric and Nathan will also be attending. Nathan showed progress on Step Into CDSi. Question about where the tickets are to be logged and taken care of. This will be talked about IFG next Friday. Vaccine Groups / Target Disease: A question about whether this on the immunization resource too. The background is that we don't want to use a vaccine group (like NOS CVX) when we can convey with Target Disease. Looked at it and it is not on immunization is it is on immunizationRecommendation. So this is part of the incubator. Using targetDisease generally, and vaccineCode only if there is a specific vaccine. The definitional part of the vaccineCode that needs to be changed. TargetDisease is always valued. Would recommend changing the cardinality to 1..*. Could be multiple, but usually one. That should be valued. There is no concept of "vaccine group", it's not a defined concept. We might lose a battle with FHIR experts, but we can do that in our IG. Discussed if Codeable concept can be repeated inside. And yes it can but the concepts inside CodeableConcept need to be the same. MMR would be sent as multiple targetDiseases, not one CodeableConcept with three codes inside. Eric will revise that ticket based on this conversation. Let's get rid of VaccineGroup so that vaccineCode is just the vaccine. We don't need the vaccineGroup. Next ICE release will split out the diseases into a list of codeable concepts. Season selection: (What season the vaccinated was evaluated in, and what season it is forecasted for.) HLN has this in extensions right now. Series selection: Which series was selected. Helps with traceability for both evaluation and forecast. Knowing what is driving this is very helpful. There are string fields for series, but they want codedable concept. Number of doses remaining: A user requested this. Makes sense that we would add a new field. How should we deal with seasonal? Will be convening season. That can help resolve issue with knowing what the values apply to. There are different tiers of information. We will be working to standardized codeable values for forecastStatus, a tier 1 concept, but probably not for doseNumber, series, season, which will need to be published. Also returning the URL that gets you back to the rules. Might be a security issue for some systems. Not an issue for the guide. The Backbone element, which recommendation is, can't support documentation. It has very little inheritance. The idea was that we change the type of element then we get more properties. Not tied to this solution. We will need to do some research on this to see what this is. Propose we put in some kind of field to support URL. Could be more information, meta information. What about markdown? There is a description field already. That gives you the clinical information. Might want to be able to embed content. There is information for clinical user, but what we are missing is what the rule implementation did. Implementation specific details. Erin is going to try and make more tickets.
Wrap Up Current topic 3:55 PM–4:00 PM 5 min	Next steps Next topics