Thanks for raising these questions Craig,
I’m curious from the team members, what are the current patterns of managing data integrity and access within the OpenHIE implementation or other HIE implementations? If not implemented what patters are we designing around.
I’m curious as to how others are managing the scenario that Craig outlined below?
···
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
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.
On Mon, May 16, 2016 at 6:08 AM, Craig A cappl@grameenfoundation.org wrote:
Hi Carl,
I’ll answer the questions inline
On Thursday, May 12, 2016 at 12:32:06 AM UTC-7, carl wrote:
Hi Craig
Great to have you weighing in here.
I’ve added a heading on the wiki page for the assumptions you list here. I’m wondering what you are thinking around the concept of DATA ACCESS? is this how OpenHIE allows data access or what data is accessible by who, how to configure etc?
Craig: I attended an Interop Layer community call last month where we discussed informed consent. It got me thinking about central government ownership of the HIE and mandated use. It makes sense for all health providers in a given geographic area to be required to interact with the HIE. Let’s say INGO 1 works in the country and is now mandated to push data to the HIE. Are there generalized workflows we can share that would reduce the burden of adoption for this INGO? For example, what happens in OpenHIE implementations when there’s a conflict between the data in the HIE and the data in a Point of Service provider’s system? Who owns that data and how can the POS provider ensure data quality in this scenario? Is it a best practice to create duplicate records? I feel that there is a lot of operational knowledge in OpenHIE deployments that could benefit the community.
On Wed, May 11, 2016 at 7:39 PM, Craig A ca...@grameenfoundation.org wrote:
Hi Carl,
I have a few items for group discussion:
- It would be good to identify key assumptions when implementing OpenHIE. For example, I think we assume that a Point of Service application should be connected to the internet to gain real-time benefit from OpenHIE.
What should we assume about data access, modifying records and recommending workflows when things go wrong?
Sincerely,
Craig
On Tuesday, May 10, 2016 at 11:22:20 PM UTC-7, carl wrote:
Good day all
As our introductions start kicking up it is a good time to start asking some questions of the growing network. The first is:
“What are we missing?” - https://wiki.ohie.org/display/SUB/OHIN+Wiki+content+suggestions
There is a page on the wiki - https://wiki.ohie.org/display/SUB/OHIN+Wiki+content+suggestions with some initial ideas and we would encourage the network to discuss these here on the list and make suggestions.
Looking forward to the feedback (here and wiki)
Senior Program Manager | Digital Health Division
Regards
Carl Fourie
Jembi Health Systems | SOUTH AFRICA
Mobile: +27 71 540 4477 | Office: +27 21 701 0939 | Skype: carl.fourie17
E-mail: carl....@jembi.org
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.
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-implement...@googlegroups.com.
To post to this group, send email to ohie-imp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/7eac3f08-3ead-4303-b6aa-101263cbecc4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-implementers+unsubscribe@googlegroups.com.
To post to this group, send email to ohie-implementers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/a62ed55a-0e2e-4f0f-bfda-58bcaeec208f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.