Professional Associations that bring together competing entities, such as HL7, are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 activities, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust policy as stated in §05.01 of the Governance and Operations Manual (GOM).




AbdulMalik Shakir Hi3 Solutions
Austin Kreisler Leidos
Becky Angeles Carradora Health
Cindy Bush CDC/NCHS
Craig Newman Altarum
Danny Wise Allscripts
Forrest White Altarum
Jamie Parker Carradora Health
Jennifer Lockhart Alaska PH
John Loonsk JHU/APHL
Karen Knight NAACCR
Karrie Schwencer HLN Consulting LLC
Kasey Diebold CDC
Kishore Bashyam Drajer LLC
Laura Rappleye Altarum
Maria Michaels CDC
Mike Yaskanin Altarum
Ravi Kafle WA-DOH
Ruby Nash Lantana Consulting Group
Sarah Gaunt Lantana Consulting Group
Shirley Burton CDC/NIOSH/RHD/SB
Tony Winters PHII

Chair: Laura Rappleye 

Scribe: Danny Wise 

Discussion items





5 min.Welcome, agenda review, meeting minute approval Laura Rappleye
  • last week's minutes approved as posted; no concerns or corrections raised
5 min.

MedMorph Reference Architecture IG - Vote to reopen, propose new resolution, and re-vote on FHIR-30205 - Getting issue details... STATUS

Becky Angeles
  • IG initially adopted US Core v. 3.1.1
  • Comment was to use US Core v, 3.2 instead (latest version at the time)  – initially disposed as persuasive in March 2021
  • Project team decided to stick with 3.1.1, however, since that version is used in regulation for the 21st Century Cures Act
  • WG approved re-opening comment 21-0-0 (motion: Becky, second: Craig) 
  • WG approved new “not persuasive” disposition (motion: Becky, second: AMS) 23-0-1
5 min. MedMorph Reference Architecture Ballot Reconciliation package discussionBecky Angeles
  • Ballot recon is nearly complete, question about next steps
  • Only one remaining comment that's being worked through – does it need to be 100% resolved before sending out recon package for review?
  • Austin asked if that comment was a negative – BALLOT-14997 - Getting issue details... STATUS is an affirmative vote
  • To keep from delaying things further (since this IG is now impacting our WG Health Metrics as an “idle ballot”), WG agreed it’s OK to move on to sending out recon package for WG review with the caveat there is one last comment that should be resolved in the near future
10 min.

Longitudinal Maternal Health Research IG - Questions on 9 Jira tickets like this FHIR-37144 - Getting issue details... STATUS and others in BV1 - Ruby Nash (15 min)

Ruby Nash
  • 9 tickets were submitted related to terminology (one for each of 9 different value sets in the IG) suggesting to use (THO) URLs vs, URLs
  • To do so, a value set needs to go through the UTG process to be properly registered
  • There has been some indication that an IG with FMM-3 maturity will be required to have all value sets in THO
  • WG recommends that since this is a brand new IG, dispose tickets as “Considered for future use”
  • Will be included approval in WG approval in upcoming block vote
15 min.

FHIR eCR and US Core Gender Identity extension (

    1. extension is different to C-CDA Companion Guide Gender Identity template - does not allow for multiples with date ranges
    2. propose re-opening and re-disposing this Jira issue: FHIR-37437 - Getting issue details... STATUS
    3. propose creating a new Gender Identity extension with the ability to capture date range instead of using US Core Gender Identity profile
    4. (have raised an issue against the US Core Gender Identity Extension here: FHIR-37509 - Getting issue details... STATUS )
Sarah Gaunt
  • New Gender Identity template in C-CDA V3 supports multiple gender identities with date ranges (since a person's gender identity could change over time)
  • However, US Core only supports one gender identity for FHIR with no date range
  • FHIR-37509 - Getting issue details... STATUS logged to address this in US Core, but this wouldn’t get updated until a future version of US Core; prefer to keep IG aligned with US Core 3.1.1 because that’s what’s included in regulation text (similar to earlier MedMorph discussion)
  • Request to re-open previous eCR FHIR IG ticket FHIR-37437 - Getting issue details... STATUS so it can be redispositioned to use a different, new extension that supports multiple gender identities
  • Will model new extension after R5 gender identity extension (, will use ”preferred” value set appropriate for US Realm
  • Will create separate Jira ticket to work with Cross-Group Projects to discuss issue and come to agreement on variance from US Core
  • WG approved re-open FHIR-37437 - Getting issue details... STATUS 25-0-0 (motion: Sarah, second: Craig) 
  • WG approved new “persuasive with mod” disposition and will create new extension 25-0-0 (motion: Sarah, second: Craig)