Chair:  Durwin Day Christol Green 

interim co-chair: peter gunter,  chris johnson

Scribe: Robin Isgett  


Antitrust Statement

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 stated in §05.01 of 
the Governance and Operations Manual (GOM).

NOTE: This attendance applies if you are present at the related meeting/call, regardless if you have signed a different attendance for your WG. 

Attendees


Minutes Approved as Presented 


This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."


Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Decision Link(if not child)
HL7

Antitrust Statement

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 stated in §05.01 of 
the Governance and Operations Manual (GOM).

Christol read Antitrust Statement.
Management

 Minutes Approval 10/4/2022

Approved minutes by consensus.

Management

New Proposals and PSS for review - PIE comments or interest

No new proposals or PSSs.
ALL

Jan 2023 Connectathon in Henderson NV Jan 14-15

Jan 2023 WGM in Henderson NV - meeting dates and quarters (Jan 16-20)

PIE WGM Jan 16-19, 2023 Agenda/Minutes

Reviewed draft agenda.  Corrected Tues Q1 to Thru Q1for FHIR meeting with FM.  Added Gender Harmony and R&E to Tues Q3.  Need to add LOINC overview Wed Q2.  Added Wed Q1, CCDA on FHIR with Rick G.  Asked the workgroup to think about topics for the agenda.


ALL 

CDex - Ballot reconciliation underway - PIE WG Tickets to be review on CDex call tomorrow

CDex Survey results

CDex mapping exercise

Review next agenda.
LenelRace and Ethnicity codes - continued

Ballot closes Friday at midnight for Gender Harmony and R&E.  May have guidance on using CDA to collect this data.  Lenel sent an E-mail with the tickets for consideration.

Thanks to Matt at MaxMD for compiling this list of comments for consideration by PIE.


Jira ticket: OTHER-2464 

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony

Related Section(s): 2.1 Gender Identify GH

Summary: IG should provide an example of how to use in a containing structure witch supports multiple cardinality. Statement alone is not sufficient guidance

Description:

Current text:

"This template represents one code value, with associated context and metadata. It is expected to be composed into containing structures with multiple cardinality to support cases that require multiple values."

While the text supports multiple cardinality, there needs to be more guidance provided.


Jira ticket: OTHER-2465

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony

Related Section(s): 2.1 Gender Identify GH

Summary: Constraints should be added to provide explicit guidance on how to record the provenance of this information. 

Description:

Constraints should be added to provide explicit guidance on how to record the provenance of this information.

  • Who was the author?
  • Who was the informant?
  • Also what method was used to collect this information? 


Jira ticket: OTHER-2466

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony

Related Section(s): 2.1 Gender Identify GH

Summary: Need to include an example that shows use of NullFlavor OTH and how to document a write-in value


Description:


Jira ticket: OTHER-2467

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony

Related Section(s): 2.2 Individual Pronouns 

Summary: Constraints should be added to provide explicit guidance on how to record the provenance of this information. 

Description:

Constraints should be added to provide explicit guidance on how to record the provenance of this information.

  • Who was the author?
  • Who was the informant?
  • Also what method was used to collect this information? 


Jira ticket: OTHER-2468

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony

Related Section(s): 2.2 Individual Pronouns 

Summary: Need to include an example that shows use of NullFlavor OTH and how to document a write-in value

Description:

Need to include an example that shows use of NullFlavor OTH and how to document a write-in value



Jira ticket: OTHER-2469

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony

Related Section(s): 2.3 Recorded Sex or Gender 

Summary: Provide additional guidance for the use of “<” code

Description:

The “<” code seems like it would need to be handled specially in xml documents. Recommend added an example demonstrating how to represent this code in the xml document.


Jira ticket: OTHER-2470

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony

Related Section(s): 2.4 Sex for Clinical Use

Summary: Clarification of entryRelationship

Description:

It seems like the design should go the other way or maybe the inversionInd attribute should be true.  The semantics needs to the other procedure (or what ever act) that is being referenced is supported by this observation. Shouldn't that require inversion of the SPRT semantics?




Jira ticket: OTHER-2471

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/cdagenderharmony.html

Related Page(s): CDA Gender Harmony: Figure 4: Sex for Clinical Use

Related Section(s): 

Summary: Modification to example

Description:

This example is not complete enough to be illustrative.  What is the "other" act that is being referenced?  Please clarify


Jira ticket: OTHER-2472

Specification: Cross-Paradigm Gender Harmony (OTHER)

Raised in Version: 1.0.0-ballot

Related URL: http://hl7.org/xprod/ig/uv/gender-harmony/2022Sep/index.html#questions-to-balloters

Related Page(s): FHIR Gender Harmony

Related Section(s): 1.1.2 Questions to Balloters

Summary: Use of both Patient and Observation Resource to capture "Personal Characteristic" for Gender Identity, Recorded Sex or Gender, Pronouns etc.

Description:

While initially there where thoughts that a single Resource should be used to collect details of ones Gender Identity, Recorded Sex or Gender, and Pronouns, there are reasons/use cases that would support the use of both the Patient Resource and Observation Resource. 


The use of the Observation Resource would support providing the source and method for the collection of personal characteristics (i.e. Gender Identity, Recorded Sex or Gender, Pronouns) over multiple encounters that may change over time.  While the need for an institution to have a single instance to identify Gender Identity, Recorded Sex or Gender, and Pronouns would support the use of the Patient Resource to contain the data.

For these reasons, I recommend both the use of the Social Determinants of Health IG proposed Personal Characteristic Observation as well as the Patient Resource.






ALLProducts review on PIE WG main page - what is out dated etc...ACP document can be updated only when the regulation comes out.  Ask Lisa Nelson if VBC Health Story can be removed or if changes needed.  CDA attachments are still valid.  Check with Dental regarding Dental R1 and periodontal.  No change to OID.  Carin and CDex are updated under key references for implementing attachments.  Clinical Documents for payers no longer needed.  Can probably get rid of last 4 bullets.  Review more for next meeting.
Adjourned at
Adjourned at 3:07 PM EST.

Supporting Documents

Outline Reference

Supporting Document

Minute Approval


Tasks

  •