Please add your topics here within this section, instead of using comments; the comments may not be seen.
Time & Constraints
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
Oracle reviewed: Allergies, Problems(cond and dx), ReqMeds, Procedures, and Immunizations. Ready for Jay's final review.
Taskforce meeting series, John is presenting
C-CDA <> FHIR mapping will share “reconciled” examples with the CDA examples task force for review and feedback.
Examples to be discussed include (see specific content here: https://github.com/chunli866/CCDAtoFHIRSamples/tree/main/Rec_Output_Draft):
|Focus on content publishing.|
Structural and vocabulary mapping group (PAMPI+) status
Allergy gaps review with Russ.
Jay- "immunizations "1/2 done.
Mapping-reviewed PAMPI value-sets
"Task Force'-first meeting went well.
Chun's team- working on the prep work for the upcoming connecthaton.
Medication request resource discussion:
Option 1: Using "order" seems indefensibly specific. Using "plan" may also seem indefensibly specific, but for US Core guidance.
US Core requires all meds to be reported in MedicationRequest, including those more accurately reported as MedicationStatements. In those cases, US Core stipulates using intent = "plan" as a default value.
CF map: https://docs.google.com/spreadsheets/d/1JTXVrmdWya4by2x0jJiFE8MHMPFx2-ihTQIZNwnZvuI/edit#gid=0
The FC map just says “not supported.”
Option 2: Cerner/Oracle.
This resource covers all types of orders for medications for a patient. Our implementation is based on "order" representing a request or a demand for authorization for action and is more in tune with an order being placed.
Option 3. Dan -use both
Ballot discussion in FMG on November 2
|Ballot as a new IG or with the previous IG - reference the FMG discussion on November 2 initiated by Structured Documents co-chairs. Jean Duteau, CGP chair, was also present.|
FMG Discussion 2022-11-02 FMG Agenda/Minutes (Summarized by John D'Amore)
Github repository https://github.com/HL7/ccda-on-fhir
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
Deloitte team ( Taima Gomez, Steve Powell, Nahom Endashaw)
|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.|
HL7 SD and FHIR Connectathons
Connectathon information January 2023
|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.
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 AIemail@example.com|
@ Ken Lord
|@ John D'Amore||Moreinformaticsfirstname.lastname@example.org|
|@ Lisa R. Nelson||MaxMDemail@example.com|
|@ Jay Lyle||JPSystemsfirstname.lastname@example.org|
Joseph Quinn (Joe)
|Smile Digital Healthemail@example.com|
|@ Sara Armsonfirstname.lastname@example.org|
|@ Scott Robertson||Kaiser Permanenteemail@example.com|
|@ Christopher Vitale ||DiameterHealthfirstname.lastname@example.org|
|@ Angie Benoit||DiameterHealthemail@example.com|
|@ Hans Buitendijk||Oracle Health AI|
|@ John Donnellyfirstname.lastname@example.org|
|@ 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||Sequoiaemail@example.com|
|@ Gay Dolin|
|@ Serafina Versaggi|
|@ Michelle Barry|
@ Diego Kaminker
|@Jean Duteau||Duteau Design Incfirstname.lastname@example.org|
|@ Floyd Eisenberg||iParsimonyemail@example.com|
|Smile Digital Health|
|@Eleanor Claire Cundiff|