OHIE-TS: Join OHIE-SHR for validation role discussion

On our last
OHIE-TS community call on March 11th
we briefly discussed what the validation role for TS could look like. This discussion was a result of feedback we received from the OHIE-Shared Health Record community (OHIE-SHR) around existing use cases
where the TS is not being used for validation of terminology.

The TS is about serving its users so our community would like to better understand what validation looks like for OpenHIE implementations and how we can better assist the SHR component. In the
spirit of collaboration the OHIE-SHR community has invited TS community members to join their next call on
Tuesday, March 24th @10am EDT to discuss what the potential validation role for TS might look like?

Jamie Thomas | Global Health Communications Specialist

Regenstrief Institute, Inc. |
ph: 317.274.9218 | Skype: jamie.thomas5670 | jt48@regenstrief.org

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.

Reminder we will be talking about
what validation looks like for OpenHIE implementations and how we can better assist the SHR component on the next
OHIE-SHR call on Tuesday, March 24th @10am EDT, read more below.

ยทยทยท

Thank you,

Jamie Thomas

From: Thomas, Jamie
Sent: Thursday, March 12, 2015 9:42 AM
To: terminology-services@googlegroups.com
Subject: OHIE-TS: Join OHIE-SHR for validation role discussion

On our last
OHIE-TS community call on March 11th
we briefly discussed what the validation role for TS could look like. This discussion was a result of feedback we received from the OHIE-Shared Health Record community (OHIE-SHR) around existing use cases
where the TS is not being used for validation of terminology.

The TS is about serving its users so our community would like to better understand what validation looks like for OpenHIE implementations and how we can better assist the SHR component. In the
spirit of collaboration the OHIE-SHR community has invited TS community members to join their next call on
Tuesday, March 24th @10am EDT to discuss what the potential validation role for TS might look like?

Jamie Thomas | Global Health Communications Specialist

Regenstrief Institute, Inc. |
ph: 317.274.9218 | Skype: jamie.thomas5670 | jt48@regenstrief.org

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.