OpenHIE DevOps Call - Monday, February 6 at 10 a.m. ET

We are having our
OpenHIE DevOps
call this Monday, February 6 at 10:00 a.m. Eastern Time.


  1. What documentation does the dev/ops community need to provide to support the OpenHiE implementer’s meeting?


  • A. Create a list of documentation and/ or links the dev-ops team needs to gather or create for the implementer’s meeting

Probably things like:


  • Demo


  • Overview of the demo


  • how to run the demo


  • how to install the demo


  • Installation and configuration of tools

-Updated links to OHIE components and directions for installing components?


  • directions for configuring / examples of configurations for specific workflows?


  • what else?

  • B. determine who owns the items and action plan to begin getting this documentation in place


  • How does this fit in with the toolkit?
  1. Work stream updates
  • A. (Ryan C.) Communicate and Demonstrate OHIE Concepts


  • Demo update

  • B. (Carl F.) Support Implementer Use of OHIE


  • Any updates on implementer meeting

  • C. (Paul Brown) Verify OpenHIE integration / Conformance


  • what do we need to do to start getting a strategy in place


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


1101 West Tenth Street

Indianapolis, IN 46202

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

Skype ID: miclcox | |

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.