A couple of questions (OHIE Guidebook)

Legacy ohie-implementers
1

Hey everyone,

I’ve been wanting to ask for a while now about what you think the current OpenHIE Framework does not do that you wish it did? Is there a specific article missing? Would a 1-2-3 type of implementation steps be welcomed to help implementers in understanding a sequence of steps to establishing an HIE?

In documenting the initial OHIE Guidebook table of contents these questions come up again and again, maybe you have other thoughts that you can share?

Thanks,

Brian

Regards

Brian Armstrong
Digital Health Systems Architect

Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong

E-mail: brian.armstrong@jembi.org

Web: www.jembi.org

2

Hi all.

This PPT deck is from a few years ago; it was presented at the 2nd AeHIN conference in Manila in September, 2013. As you can tell from the last slide of the deck, this presentation immediately preceded an “intro to OpenHIE” prezo that Shaun gave. The deck’s content is informed, in part, by PEPFAR-funded work that was planned to be released as a WHO Guideline. Sadly, that project was never taken through to completion by WHO.

The theme of a re-usable workflow pattern is one that underpins the entirety of OpenHIE’s architectural approach. Brian, I would hope that we could leverage some of this early thinking – update/refresh it – and use it as a way to frame how OpenHIE’s “Lego blocks” map to guideline-based care delivery workflows.

Warmest regards,

Derek.

PS: sorry for the large number of slides… but as is true for most of my PPT decks, the slides are intended to be run in quick succession in PPT show mode (like an animation). It is probably best viewed that way….

PPS: There is a related a deck on our OpenHIE wiki (found here: https://wiki.ohie.org/download/attachments/13926693/14-02-03%20arch%20diagrams.pptx?api=v2) that provided some forward-looking ideas about how we could employ a workflow engine to bake care guidelines into our HIE infrastructure. The “integrated care pathway” (ICP) project never did find support within our OpenHIE community – but the idea of a top-10 list of workflows (see slide 53) is one which still might be worth pursuing. Just a thought…

Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality.

13-09-23 AeHIN partner prezo (ecGroup).pptx (1.94 MB)

···

From: ohie-implementers@googlegroups.com [mailto:ohie-implementers@googlegroups.com] On Behalf Of brian.armstrong@jembi.org
Sent: Friday, August 26, 2016 5:16 PM
To: OpenHIE Implementers Network (OHIN)
Subject: [ohie-implementers] A couple of questions (OHIE Guidebook)

Hey everyone,

I’ve been wanting to ask for a while now about what you think the current OpenHIE Framework does not do that you wish it did? Is there a specific article missing? Would a 1-2-3 type of implementation steps be welcomed to help implementers in understanding a sequence of steps to establishing an HIE?

In documenting the initial OHIE Guidebook table of contents these questions come up again and again, maybe you have other thoughts that you can share?

Thanks,

Brian

Regards*

Brian Armstrong*

Digital Health Systems Architect

Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong

E-mail: brian.armstrong@jembi.org

Web: www.jembi.org

–
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/c33c1394-5abf-40e8-98a4-c08ae5e94db1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

Hi Derek,

···

Thank you for this. I will review on the weekend and come back to the list.

Have a great weekend.

Regards
Brian Armstrong
Digital Health Systems Architect

Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong

E-mail: brian.armstrong@jembi.org

Web: www.jembi.org

On Aug 26, 2016, at 17:41, Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi all.

This PPT deck is from a few years ago; it was presented at the 2nd AeHIN conference in Manila in September, 2013. As you can tell from the last slide of the deck, this presentation immediately preceded an “intro to OpenHIE” prezo that Shaun gave. The deck’s content is informed, in part, by PEPFAR-funded work that was planned to be released as a WHO Guideline. Sadly, that project was never taken through to completion by WHO.

The theme of a re-usable workflow pattern is one that underpins the entirety of OpenHIE’s architectural approach. Brian, I would hope that we could leverage some of this early thinking – update/refresh it – and use it as a way to frame how OpenHIE’s “Lego blocks” map to guideline-based care delivery workflows.

Warmest regards,

Derek.

PS: sorry for the large number of slides… but as is true for most of my PPT decks, the slides are intended to be run in quick succession in PPT show mode (like an animation). It is probably best viewed that way….

PPS: There is a related a deck on our OpenHIE wiki (found here: https://wiki.ohie.org/download/attachments/13926693/14-02-03%20arch%20diagrams.pptx?api=v2) that provided some forward-looking ideas about how we could employ a workflow engine to bake care guidelines into our HIE infrastructure. The “integrated care pathway” (ICP) project never did find support within our OpenHIE community – but the idea of a top-10 list of workflows (see slide 53) is one which still might be worth pursuing. Just a thought…

Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality.

From: ohie-implementers@googlegroups.com [mailto:ohie-implementers@googlegroups.com] On Behalf Of brian.armstrong@jembi.org
Sent: Friday, August 26, 2016 5:16 PM
To: OpenHIE Implementers Network (OHIN)
Subject: [ohie-implementers] A couple of questions (OHIE Guidebook)

Hey everyone,

I’ve been wanting to ask for a while now about what you think the current OpenHIE Framework does not do that you wish it did? Is there a specific article missing? Would a 1-2-3 type of implementation steps be welcomed to help implementers in understanding a sequence of steps to establishing an HIE?

In documenting the initial OHIE Guidebook table of contents these questions come up again and again, maybe you have other thoughts that you can share?

Thanks,

Brian

Regards*

Brian Armstrong*

Digital Health Systems Architect

Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong

E-mail: brian.armstrong@jembi.org

Web: www.jembi.org

–
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/c33c1394-5abf-40e8-98a4-c08ae5e94db1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

<13-09-23 AeHIN partner prezo (ecGroup).pptx>

4

HI Brian,

Thanks for the question. I think Derek raised a thread where there were a few comments on what would be great to see, maybe lets add that to the list?

Regards

···

On Fri, Aug 26, 2016 at 11:15 PM, brian.armstrong@jembi.org wrote:

Hey everyone,

I’ve been wanting to ask for a while now about what you think the current OpenHIE Framework does not do that you wish it did? Is there a specific article missing? Would a 1-2-3 type of implementation steps be welcomed to help implementers in understanding a sequence of steps to establishing an HIE?

In documenting the initial OHIE Guidebook table of contents these questions come up again and again, maybe you have other thoughts that you can share?

Thanks,

Brian

Regards

Brian Armstrong
Digital Health Systems Architect

Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong

E-mail: brian.armstrong@jembi.org

Web: www.jembi.org

–

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/c33c1394-5abf-40e8-98a4-c08ae5e94db1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

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.

5

Hi Carl,

That sounds great, I will do that. I’m digesting the information Derek sent, and seen several points that could be included. I will send further thoughts later this afternoon (Canada EST).

Thanks!

Brian

···

On Mon, Aug 29, 2016 at 5:38 AM, Carl Fourie carl@jembi.org wrote:

HI Brian,

Thanks for the question. I think Derek raised a thread where there were a few comments on what would be great to see, maybe lets add that to the list?

Regards

Regards
Brian Armstrong
Digital Health Systems Architect

Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong

E-mail: brian.armstrong@jembi.org

Web: www.jembi.org

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 Fri, Aug 26, 2016 at 11:15 PM, brian.armstrong@jembi.org wrote:

Hey everyone,

I’ve been wanting to ask for a while now about what you think the current OpenHIE Framework does not do that you wish it did? Is there a specific article missing? Would a 1-2-3 type of implementation steps be welcomed to help implementers in understanding a sequence of steps to establishing an HIE?

In documenting the initial OHIE Guidebook table of contents these questions come up again and again, maybe you have other thoughts that you can share?

Thanks,

Brian

Regards

Brian Armstrong
Digital Health Systems Architect

Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong

E-mail: brian.armstrong@jembi.org

Web: www.jembi.org

–

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/c33c1394-5abf-40e8-98a4-c08ae5e94db1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.