Hi All,
Here are some Next Steps from yesterday’s OHIE – TS call today.
·
TS Implementation Guide – Jack will interview writer for the guide but will also look to expand the outline before our next call. All members should take a look at the current
OHIE - Facilities Registry Guide for other ideas. <Jamie can you provide the link?>.
·
HIE Terminology Use Cases - We are looking for all community members to provide 4-5 use cases for TS interactions that they believe to be relevant for OpenHIE. An example might me “Fetch LOINC map for a local laboratory
term”. Send your list of use cases to
terminology-services@googlegroups.com then Jack will organize a list of these use-cases for the community to discuss and place relevance on the next call. (ACTION ITEM FOR ALL)
·
Use Cases – Jon, Andy and Larry will continue to work on case studies; Jon – Rwanda, Andy - MoTECH/IMO, Larry - VA Model
Couldn’t join the Terminology Services community call today? Or maybe you did but want to refresh your memory about what happened?
Listen to a recording and read the minutes posted on the OpenHIE Wiki.
Next Call – July 3rd
·
Review Rwanda Use Case w/ Jon
·
(TOPICS??)
Jamie Thomas |Health Informatics Project Coordinator
Regenstrief Institute, Inc. |ph: 317.423.5670 | 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.