Questions for the community

Good Day All

Today we had a great engaging discussion on the Community Call. The major point of discussion was on the OHIE Mythbusters slides:
https://docs.google.com/presentation/d/19HBjChP4ZUxnIsf-hEbFkKW_uC1W7iAibRTi7e0D3uo/edit#slide=id.p24

These represent some of the “common” assumptions and questions that we’ve seen raised about OpenHIE. We’d love to get your input on these slides and also have we missed any “myths” that we need to prove or “bust” :wink:

There are a range of questions and conversations points that we looked at that can be found in the minutes here:
https://wiki.ohie.org/display/resources/2017-04-24+Community+Call

We would value the broader communities thoughts on helping us answer them. A topic we pushed to next month’s call is “When is it OpenHIE and When is it not”? Reall looking at times when we may need to use different standards, workflows etc and what is the line when we stop calling it OpenHIE. Would be great to get community members to share ideas and examples of this.

···

Regards
Carl Fourie

Senior Program Manager | Digital Health Division

Jembi Health Systems | SOUTH AFRICA
Mobile: +27 71 540 4477 | Office: +27 21 701 0939 | Skype: carl.fourie17
E-mail: carl.fourie@jembi.org

Physical Address: Unit 3B, 5A-C, Tokai on Main, 382 Main Road, Tokai, Cape Town, South Africa (Map Link)

Email Disclaimer:

This e-mail contains proprietary and confidential information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then deleting same. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail. Jembi Health Systems NPO, its subsidiaries and associated companies is not liable for the security of information sent by e-mail and accepts no liability of whatsoever nature for any loss, damage or expense resulting, directly or indirectly, from the access of this e-mail or any attachments hereto.