Please add your topics here within this section, instead of using comments; the comments may not be seen.
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).
Review Project Planning
Public health report out.
Structural and vocabulary mapping group (PAMPI+) status
(02/13/23 Terminology "Routes" team review request.
Allergy gaps review with Russ.
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.
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:
May 2023 Ballot discussion
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).
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.
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)
Provenance Domain Definitions
Definition of Author
Qualitative and Quantitative scoring
|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:
HL7 SD and FHIR Connectathons
|Connectathon information 2023 - 01 Connectathon 32|
track report out:
|8||HL7 Working Group|
The decision process for using ConceptMap
Antler (condition syntax tool for running languages) vs fhirpath - why both.
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.
The most updated maps:
FMG. building maps is still a challenge
Potential CDC collaboration.
All necessary approvals were received from 3 teams:
Parking Lot topics for the future:
- update from previous minutes
Topics on Deck:
- Updates from AMIA: ONC, department of health, FDA.
- New participants' orientation Q&A orientation TBD.
- Valuation of the v2- CDA value-set maps.
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
- C-CDA to US Core value set alignment
Open Action Items:
- update from previous minutes
Adjourn: xxxx pm
|@ Natalee Agassi||Oracle Health AIfirstname.lastname@example.org|
@ Ken Lord
|@ John D'Amore||Moreinformaticsemail@example.com|
|@ Lisa R. Nelson||MaxMDfirstname.lastname@example.org|
|@ Jay Lyle||JPSystemsemail@example.com|
Joseph Quinn (Joe)
|Smile Digital Healthfirstname.lastname@example.org|
|@ Sara Armsonemail@example.com|
|@ Scott Robertson||Kaiser Permanentefirstname.lastname@example.org|
|@ Christopher Vitale ||DiameterHealthemail@example.com|
|@ Angie Benoit||DiameterHealthfirstname.lastname@example.org|
|@ Hans Buitendijk||Oracle Health AI|
|@ John Donnellyemail@example.com|
|@ Ayala Anmer||HHS||Anmer.Ayala@hhs.gov|
|@ Natasha Kreisle||MaxMD|
|@ Emma Jones||Allscripts|
|@ Gargi Gajjar||MDIX|
|@ Peter Muir||PJM Consulting|
|@ Sajjad Hussain|
|@ Paulo Pinho|
|@ Didi Davis||Sequoiafirstname.lastname@example.org|
|@ Gay Dolin|
|@ Serafina Versaggi|
|@ Michelle Barry|
@ Diego Kaminker
|@Jean Duteau||Duteau Design Incemail@example.com|
|@ Floyd Eisenberg||iParsimonyfirstname.lastname@example.org|
|Smile Digital Health|
|@Eleanor Claire Cundiff|