2022-07-06 CDex/HRex Meeting

CMS HL7 Virtual Connectathon - July 2022

Date: July 19-21, 2022    

Registration:  https://www.surveymonkey.com/r/56MXVRF (Ended June 30)

Location:  Virtual

Follow the CMS 2022 - 07 FHIR Connectathon 3 - FHIR - Confluence for Track Information and Logistics.

Calling all Implementers!  Opportunity to demonstrate your investment in FHIR and show the success of interoperability!  Sign Up here: Planning Demos Schedule- CMS HL7 Virtual Connectathon - July 2022

HealthLX Update: Jason/Joel will share an update on what to expect from the RI, specifically sharing the request and response: 

• Structure of the payload to send to the operation's end point
• Resources stored at the operation end point
• Share diagram of how it will work

The CMS Virtual Connectathon is fast approaching and we are nearing the final stages of planning. 

Jason (HealthLX) provided an update on the HealthLX reference implementation for attachments. 

• The endpoint is on a server that would need to be deployed. Could stand up the HealthLX server or bypass real endpoint and go directly into the logic. Would not be noticeable via the interface but is you want to see the raw endpoints, would have to deploy the server.
• Would also limit the ability to use Touchstone because there wouldn't be anything to hit. 
• Jason noted that standing up the HealthLX server is not a lot of work. The group decided that standing up the server would be best so that Touchstone can be used.

September Connectathon - 2022 - 09 Connectathon 31

Date: September 17-18, 2022

Location: Baltimore, MD (Live and In-Person)

Proposals are Due July 12th

1. FHIR-36985: Clarify Figure 4 and associated text in 2.6.2 (hbuitendijk) Persuasive with Modification
2. FHIR-36997: Alignment with other ePA guides (hbuitendijk)
3. FHIR-36845: Need clarification on who is signing for whom (sutley) Persuasive with Modification
4. FHIR-37253: Please flesh sentence (celine_lefebvre) Persuasive with Modification
5. FHIR-37243: concerned about liability implications of digital signatures (celine_lefebvre) Persuasive with Modification
6. FHIR-37563: Add Request Attachments" content as Draft (ehaas) info pre-apply in flight, need clarification on requirements. see below
7. FHIR-35151: Better standardize Task.reasonReference by formalizing (but not limiting) the current scenarios (Isaac.Vetter)  Not Persuasive with Modification
8. FHIR-30824: Recommendation for exchanging purpose of use. (Isaac.Vetter) Persuasive with Mod

FHIR-35151 - Getting issue details... STATUS Eric noted that this ticket was addressed offline and Isaac removed the in-person resolution requirement. He briefly summarized the resolution and the ticket was changed to ready for vote.

FHIR-36997 - Getting issue details... STATUS This ticket relates to the conversation during the Burden Reduction call this morning. There is interaction between PAS and CDex that needs clarification. Eric intends to add a section with flow diagrams. Hans agreed that would be helpful but the additional clarity around the when, what and where needs to also be included. Hans is ok with the proposed resolution but emphasized the need to update PAS and CDR. 

FHIR-36845 - Getting issue details... STATUS Need to add clarity around synchronous and asynchronous signatures. Eric will add a summary section in the Signatures pages to summarize the different scenarios.

The last block vote will be made available via Zulip and the listserv for review. The block vote will take place in the Patient Care workgroup meeting this coming Monday, July 11th.

13:17:26 From  Crystal Kallem (POCP / Da Vinci PMO)  to  Everyone:

https://jira.hl7.org/browse/FHIR-30824

13:32:07 From  Christol -Elevance Health  to  Everyone:

sorry I'm late, on call now

13:36:09 From  Isaac Vetter (Epic)  to  Everyone:

Although current state of healthcare data exchange is typically limited to a single, well-known and pre-established purpose-of-use, this IG intends to define a potential and aspirational path forward such that at some time in the future, data exchange between two actors will enable distinct and dynamically defined purposes of use.

13:40:05 From  ehaas  to  Everyone:

we need to wrap this upe

13:40:15 From  Hans Buitendijk (Cerner)  to  Everyone:

Note that there is a survey going around Da Vinci and others to determine whether we can define common data sets (inclusive of POU as that is critical) that can be requested.  It would be a starter set that parties can adjust locally, but could get us on the path towards more dynamic requests.  But dynamic requests are indeed not short term.

13:49:57 From  Crystal Kallem (POCP / Da Vinci PMO)  to  Everyone:

https://jira.hl7.org/browse/FHIR-36845

13:57:31 From  Isaac Vetter (Epic)  to  Everyone:

Why would it make sense to always return a system-level signature?

13:59:16 From  Isaac Vetter (Epic)  to  Everyone:

Should the direct-query page repeat this sentence from the task page: "Pre-negotiate whether electronic or digital signatures are used"

13:59:40 From  Hans Buitendijk (Cerner)  to  Everyone:

For both sync and async?

Adjourned at 3:06 PM ET