Want to be more involved in discussions about OpenHIE architecture?
Back in June 2013 a mailing list around OpenHIE Architecture & Standards was created for members of OpenHIE and its subcommunities (Client Registry, Health Worker Registry, Facility Registry, Terminology Services, Shared Health Record,
HMIS, and Interoperability Layer) to discuss cross-cutting technical issues about how components work with one another and the affect they have on our health information exchange. This mailing list is open to anyone so if you would like to join the group
click here, email is
For the last six months we have been hosting one monthly OpenHIE Architecture & Standards call on the second Monday of the month. These calls have been extremely productive for our group and team members have requested to have more calls
around architecture and cross-cutting issues. In response to this request we will now be hosting
TWO OpenHIE Architecture & Standards calls a month, one on the second Monday of the month and the other on the last Friday of the month. The next call will be held
next week on Friday, March 28th from 10:00-11:00 AM ET. Please join the mailing list for agendas and dial in information or go out to the
OpenHIE Architecture Call page on the wiki.
Jamie Thomas | Health Informatics Project Coordinator
Regenstrief Institute, Inc. |
ph: 317.274.9218 | Skype: jamie.thomas5670 |
Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s).
Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.
If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information
by anyone other than the intended recipient is strictly prohibited.