Skip to main content

Emerging Standards

FHIR Open Tickets

Reviews and coordinates open FHIR specification issues related to immunization workflows and implementation guidance.

StageDraft PathWorking on Now Topic typeCapability Followers19

Stage and Path

Stage

Draft

Draft topics are early-stage ideas gathering initial interest and problem framing.

Path

Working on Now

The next meaningful work is understood, owned, and moving forward without a material constraint.

Overview

Review of open tickets in JIRA for FHIR relating to immunizations.

Coming soon

Support for source material, diagrams, and supporting notes is coming in a future update.

Recent Outcomes

Open Issue Want a clarification between manifestation and reaction Immunization Focus Group Aug 28, 2026 View in Agenda
Working Consensus Best option? Probably not Immunization Immunization Focus Group Aug 28, 2026 View in Agenda

Meetings

MeetingAgendaPresenter(s)
Oct 23, 2026 (Upcoming)
No presenters listed
Oct 9, 2026
Review 17 FHIR tickets organized as follows:

- Previously reviewed by an IFG subset—confirm direction with the full IFG
- What is being recommended or evaluated: https://jira.hl7.org/browse/FHIR-58655, https://jira.hl7.org/browse/FHIR-58952
- Series and season representation: https://jira.hl7.org/browse/FHIR-59485, https://jira.hl7.org/browse/FHIR-59486, https://jira.hl7.org/browse/FHIR-59487, https://jira.hl7.org/browse/FHIR-59488, https://jira.hl7.org/browse/FHIR-59489
- Recommendation authority: https://jira.hl7.org/browse/FHIR-56990, https://jira.hl7.org/browse/FHIR-57247
- Tickets needing initial full-IFG review
- Evaluation authority: https://jira.hl7.org/browse/FHIR-56989
- Dose-number and series-dose datatypes: https://jira.hl7.org/browse/FHIR-54327, https://jira.hl7.org/browse/FHIR-58387, https://jira.hl7.org/browse/FHIR-58388
- Immunization reactions: https://jira.hl7.org/browse/FHIR-58403, https://jira.hl7.org/browse/FHIR-58404
- AI and Device participation: https://jira.hl7.org/browse/FHIR-59304
- Status confirmation
- Resolved editorial correction: https://jira.hl7.org/browse/FHIR-51700
Notes
  • FHIR-58655
    • Comment so far - Only need vaccine, not vaccine group
    • Similar to preferable vaccines in V2
    • Target disease is functionally equivalent to vaccine group
  • FHIR-58952
    • Only one target disease but consider expanding to allow multiple target diseases
  • FHIR-59485
    • Make it codable concept but still can do a string
    • no concerns raised by the group for this direction
  • FHIR-59486
    • Same as evaluation - no concerns
  • FHIR-59487
    • For evaluation
    • adding a season
    • no concerns raised with this direction
  • FHIR-59488
    • For recommendation
    • adding a season
  • FHIR-59489
    • On recommendation
    • can now say which does number you are on but no way of saying how many doses remain
    • can move forward as proposed
Nathan Bunker
Oct 1, 2026
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
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
Sep 25, 2026
ImmunizationRecommendation VaccineCode has a conflated definition

FHIR-57247
ImmunizationRecommendation.authority needs to be moved under recommendation backbone element

FHIR-56990
ImmunizationRecommendation.authority cardinality expansion

FHIR-56989
ImmunizationEvaluation.authority cardinality expansion
Notes
  • FHIR R6 went through ballot and resulted in some tickets
  • Zulip chat to how reactions are documented - https://chat.fhir.org/#narrow/channel/294552-Patient-Care-WG/topic/Reaction.20vs.20Manifestation/with/626177674
  • Comparing to allergy and intolerance
  • Last chance to get it right before Immunization becomes normative
  • Reaction and manifestation discussion - concerns about reducing from 0..* to 0..1 - breaking change
  • Immunization does not allow for AI to be an information source
  • Series Dose and Dose Number - provider indicates intent 2nd of 3 dose series for example - https://ginoc.io/jira-ticket-site/discussion/index.html#/ticket/FHIR-58387?wgKey=value%3APublic+Health
Craig Newman

See All Meetings

Immunization Focus Group (IFG)related toOpen

Included In

Topic ID: 96
capability planning Public Read-only view