2022-02-01 PIE WG Meeting Agenda/Minutes

HL7  Anti-Trust 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 stated in s05.01 of the Governance and Operations Manual (GOM)

Just a reminder that the ONC Annual Jan meeting will be holding virtual session on Feb 2 – 3 this week.

Topics/sessions include:

• What Health Care Providers Need to Know About Information Sharing & the Information Blocking Regulation
• TEFCA – QHIN Technical Framework Overview
• Public Health and Health IT Coordination
• FHIR Endpoint Discovery – Lantern Update
• Ask Us About Information Sharing and Learn About the New e-Prior Authorization RFI
• TEFCA – A Closer Look at the Common Agreement
• USCDI Expansion – Updates from Versions 2 and 3

Here is the link if you would like to attend any of these sessions:

healthit.gov/news/events/2022-onc-virtual-annual-meeting

PSS 1940 - FHIR IG & CDA Supplemental Guide for Medical Record Review requesting a new project in Da Vinci.  PIE comment - Would like to have understanding of what is being asked/delivered via this proposal.  Multiple workgroups are involved with medical records delivery and review occurs at payers.  Can we have you join our next PIE WG call to review and ask questions in detail.  FM will also attend.  Need clarification around intent.

FHIR-35157 - Hold until Cille or Paul on the call.

Block vote 2:

FHIR-35742 - Table of Contents should be in menu bar   

FHIR-35734 - "gropu" is misspelled in Physical Insurance Card Data Elements table            

FHIR-35185 - what other purposes?        

FHIR-35184 - what will it look like?          

FHIR-35182 - how does provider capture the information?                           

FHIR-34723 - processing missing data requirements        

FHIR-34713 - cross-page use of actor terminology in guidance and use cases        

FHIR-34712 - hyperlinks in background page references

FHIR-34682 - Definition of Beneficiary    

FHIR-34680 - Typo in data element description  

FHIR-34678 - Clarify relationship between Coverage.period and Card Issue Date 

FHIR-34676 - Coverage.type seems to be fixed to HIP      

FHIR-34674 - "Dependent code" may be confusing           

FHIR-34668 - Please define C4DIC            

Mark made a motion to vote on block 2, Mary Kay seconded the motion.  Andrea and Alix abstained.  VOTE:  14-0-2 

Bock Vote 3 to vote on next meeting after review: 

FHIR-34777 - More documentation on Patient Consent and Trust

FHIR-34776 - Clarify using Profiles outside of FHIR RESTful interactions.

FHIR-34775 - Describe a minimal required FHIR RESTful transaction

FHIR-34772 - Clarify if both XML or JSON are supported

FHIR-34769 - Remove requirement for Coverage.meta.profile:supportedProfile

FHIR-34766 - Change label "C4DIC" to something human readable

FHIR-34677 - costToBeneficiary type bound differently in profile and extension

FHIR-34673 - Data Element terminology is different than use case definitions