OpenHIE Health Financing Toward UHC Call - Thursday, September 10 at 10 a.m. EDT

Just a reminder that we will be having the OpenHIE Health Financing Toward UHC call Thursday, September 10 at 10:00 a.m. EDT.


  1. Creating a roadmap to draft HF workflows into the OHIE Architectural Spec

  2. AOB

We will be using Zoom:

Please note that Regenstrief—generated Zoom links will require the use of passcodes beginning September 2020. For those accessing the call via the revised link below , there should be no noticeable change since the passcode is embedded into the link. For those dialing in via phone, you will be required to enter a passcode. Please use “1” since that is the standard passcode assigned to OpenHIE-related calls.

If you encounter problems accessing this Zoom link at the time of your call, please contact Michelle Cox via Slack or email ( ) and mark your message “URGENT – ZOOM”.

Join from PC, Mac, Linux, iOS or Android :

Or Telephone : Dial: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)

Meeting ID: 154 938 887 Passcode: 1

International numbers available :

If you could not join us for the OpenHIE Health Financing Toward UHC call yesterday, you can read the minutes or listen to the recording on 2020-09-10 Health Financing Toward UHC Call wiki page.

The next OpenHIE Health Financing Toward UHC call is scheduled for 10:00 a.m. EDT on Thursday, October 8th.

Hi all – I had a chance to review the minutes of the UHC meeting (sorry I couldn’t attend it… the topics and discussion were very interesting!). There was a line of discussion around the similarities between the CR and the beneficiary database (in OpenIMIS).

This is a topic that relates to work done by the JLN a few years ago to map a common digital health infrastructure that could be used to serve healthcare and UHC workflows (and the analytics needed to manage each of these). It was published in 2014 by PATH, but (except that it predates FHIR) the concepts are all still very applicable. The book can be found, here: There is a 1:1 mapping that can be made between CR and beneficiary DB, between FR and empaneled providers, between HWR and empaneled practitioners, between healthcare terminologies and billing codes, and between SHR and insured service transactions. See Fig. 10 here for an example:

I hope this is helpful and I’d be happy to discuss this work with anyone interested in exploring how our new FHIR-based profiles can operationalize the approaches described in the chapter on “enterprise architecture”. :slight_smile:

Warmest regards,