User-Submitted Topics

Please add your topics here within this section, instead of using comments; the comments may not be seen.

Name

Topic

Time & Constraints


Ballot approval steps and preparation 

Postpone the meetings until comments are received.



HL7 Antitrust Policy

Professional Associations, such as HL7, which bring together competing entities 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 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as state in 05.01 of the Governance and Operations Manual (GOM).

Agenda Topics 


Agenda Outline

Agenda Item

Discussion

Decisions/Updates

1

Review Project Planning 


Public health report out.





Report out to Public Health has been discussed and reviewed (Craig Newman).


Medication 



2Subgroups Roundup

Structural and vocabulary mapping group (PAMPI+) status



(02/13/23 Terminology "Routes" team review request.

Allergy gaps review with Russ.

http://hl7.org/fhir/uv/v2mappings/2020Sep/index.html



https://docs.google.com/spreadsheets/d/1wsWF03DFq7TkRPhl5AjFjki00KfCRXmvJJ4BAkC8uEg/edit#gid=712927881


CF map: https://docs.google.com/spreadsheets/d/1JTXVrmdWya4by2x0jJiFE8MHMPFx2-ihTQIZNwnZvuI/edit#gid=0

Negation Allergy examples were discussed in the context of the paths for the value(s) transformation.

Terminology discussion planned for the Tuesday working group meeting discussion.

(https://jira.hl7.org/browse/FHIR-39625)


02/27/23-Timelines: (sign up) 03/14-21; structure docs-03/16, CGP-03/16  ; FHIR management -03/22.

02/27/23-Outstanding work 2-3 weeks:

  1. CCDA-FHIR:
    1. Additional examples (med doses)More complete C-CDA example
  2. 03/09 FHIR-CCDA:
    1. Ken- documentation; Oracle-examples; 
  3. 03/10 Maps review is finalized. 
  4. IG content, identify gaps 



Not discussed 
3

May 2023 Ballot discussion





https://www.hl7.org/special/committees/tsc/ballotmanagement/pi_index_nibs.cfm?ProjectNumber=1122

Considerations:

C-CDA or FHR FMG can be considered the same project the ballot artifacts are the same - TBD

Content restraining suggestion has been made for an upcoming cycle. 

What is the Ballot artifact project to use? TBD 

FMG Discussion 2022-11-02 FMG Agenda/Minutes (Summarized by John D'Amore)

Github repository https://github.com/HL7/ccda-on-fhir

Cross-group team approves the NIB (02/09/2023).

Considerations:

The CDA to FHIR mapping has been validated through connectathon validation, focusing on mapping C-CDA to FHIR.

Only - Oracle and MDIX were working on the bi-directional implementation.


4

Ontology 

Not discussed 

Links 

https://confluence.hl7.org/display/CGP/Cross-Group+Projects+Home
https://confluence.hl7.org/display/CGP/Provenance+Domain

Model selection topics: Provenance and Allergy.

Floyd will reach out to Gay and the team. Explore ONC funding. Considering canonical concepts for the model. No updates (01/30)


5

Provenance Domain Definitions 

Definition of Author

Narrative 

Not discussed 


6

Qualitative and Quantitative scoring

Analytics

Not discussed 

Artifacts sources review. Gaps classification, minimum elements, and clinical validations. (DSS driver )The team has shared resources and thoughts. The initial scope has been identified - provenance and Allergies. 

Deloitte team ( Taima Gomez, Steve Powell, Nahom Endashaw)

Another avenue has been proposed:




7

HL7 SD and FHIR Connectathons 

Not discussed

Connectathon information 2023 - 01 Connectathon 32

track report out:


8HL7 Working Group

Not discussed


Not discussed 


9Balloting Preparation


The decision process for using ConceptMap

Antler (condition syntax tool for running languages) vs fhirpath - why both. 

https://build.fhir.org/ig/HL7/v2-to-fhir/mapping_guidelines.html

Stating spec (e.g., cardinality) in map vs. linking – reader convenience?  cardinality is included in the maps when you have required on one side 

[IG Shorthand links broken but in git]

Relations between fsh, json, & html

> Map pages have two sections; is one from csv & one from ConceptMap?

> FSH has fewer entries than the table (which has blank rows).

Who is using this and for what purpose? Any feedback? 


An antler style has been preferred. Concept maps play an important role in the V2-FHIR project as they help to address similarities and differences between FHIR 5 and FHIR 4 concepts i.e., role codes or participation codes, or other attributes. Also, specs like cardinality and optionality fields are important to include on both sides of the map as they are maybe different for FHIR and V2.  

https://build.fhir.org/ig/HL7/v2-to-fhir/

The most updated maps:

FMG. building maps is still a challenge 

Potential CDC collaboration. 

All necessary approvals were received from 3 teams:

2023-04-13 Cross-Group Project Workgroup Call



Parking Lot topics for the future:

  • update from previous minutes

Topics on Deck:

    1. Updates from AMIA: ONC, department of health, FDA.
    2. New participants' orientation Q&A orientation TBD.
    3. Valuation of the  v2- CDA value-set maps.
    4. Lisa Nelson: SDWG call on Wednesday Russ Ott asked if we could write up a general principle for two different things.  The General Principle would get reviewed by SDWG and would be approved, once all agree on the documented approach.  The mapping team and the value set update team could then use these two principles to help guide their work.

      1.  How to handle the use of null flavors when mapping between C-CDA and FHIR US Core.
      2. How to handle value set alignment and where aligned value sets should live


    5. C-CDA to US Core value set alignment

Open Action Items:

  • update from previous minutes


Adjourn: xxxx pm  


Attendance:

Present

Name

Affiliation 

Contact Information

  • yes
@ Natalee AgassiOracle Health AInatalee.agassi@oracle.com
  • yes 

@ Ken Lord

MDIXklord@mdixinc.com
  •  yes 
@Chun LiDiameterHealthcli@diameterhealth.com
  • yes
@ John D'AmoreMoreinformaticsjohnd@moreinformatics.com
  •  yes
@ Lisa R. Nelson MaxMDlnelson@max.md
  •  yes
@ Jay LyleJPSystems jay.lyle@jpsys.com
  • yes 
Smile Digital Healthjoseph.quinn@smilecdr.com
  •  yes
@ Sara Armson
sarmson@rti.org
  •  yes
@ Scott RobertsonKaiser Permanentescott.m.robertson@kp.org
  •  yes
@ Christopher Vitale 

DiameterHealthcvtale@diameterhealth.com
  •  yes
@ Angie Benoit DiameterHealthabenoit@diameterhealth.com
  •  yes
@Tara SwelstadDiameterHealthtswelstad@diameterhealth.com
  •  yes
@ Hans BuitendijkOracle Health AI
  •  yes
 John Donnelly 
jtdonnelly@intepro.biz
  •  yes
@ Ayala AnmerHHSAnmer.Ayala@hhs.gov
  •  yes
@ Natasha KreisleMaxMD
  •  yes
@ Emma JonesAllscripts 
  •  yes
@ Gargi GajjarMDIX
  •  yes
@ Peter MuirPJM Consulting 
  •  yes
@ Sajjad HussainGoogle
  •  yes
@ Paulo Pinho

  •  yes 
@ Didi DavisSequoiaddavis@sequoiaproject.org
  •  yes
@ Gay Dolin

  •  yes
@ Serafina Versaggi

  •  yes
@ Michelle Barry

  •  yes

@ Diego Kaminker

HL7Diego@hl7.org
  •  yes
@Jean DuteauDuteau Design Incjean@duteaudesign.com
  •  yes
@Eden Hankins

  •  yes
@ Floyd EisenbergiParsimonyfeisenberg@iparsimony.com  
  •  
@Dean AtchleyOptumdean.atchley@optum.com
  •  
@Jackie Hemenway UPMChemenwayj@upmc.edu
  • yes


  • yes
Uniteddaniel.venton@optum.com
  • yes
@Ryan Wheihler

  • yes
Smile Digital Health
  •    yes
@Eleanor  Claire Cundiff

  • No labels