Re-launch of IOL/SHR Community Call

All,

The
Interoperability and Shared Health Record Community calls
have been combined into one and will relaunch on Tuesday, May 16 at 4:00 p.m. GMT +2. Calls will take place every third Tuesday.

The May 16th call will be looking at the following agenda points:

·
Introducing the OpenHIE Interoperabiltiy Layer Functional Specification Document (https://wiki.ohie.org/display/SUB/OpenHIE+IOL+Functional+Specifications)

o
This document is a living version of the OpenHIE Interoperability Layer Functional Specification Documentation. The purpose of this document is to synthesize the definitions, functionality and expectations of an interoperability
layer that is supportive of the OpenHIE architecture and community views.

·
Discussion of the use of FHIR and the FHIR based SHR tool emerging from implementation needs.

·
AOB

We encourage you to participate in these calls. Feel free to bring your questions, comments, and ideas. Dial in information as well as a notes page can be located on the

wiki
.

Thank you!

**Michelle Cox ** |****Program Coordinator, Global Health Informatics

image001.png

1101 West Tenth Street

Indianapolis, IN 46202

Tel 317-274-9324 | Fax 317-274-9305

Skype ID: miclcox | Facebook.com/regenstriefinstitute |
www.regenstrief.org

My normal work hours are Monday – Friday, 7:15 a.m. – 4:00 p.m. Eastern Time

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.