Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page
OpenHIE Architecture Call
.

**Michelle Cox **|****Program Assistant

image001.png

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

Hi all,
Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,
-carl

2015-General-Architecture-Diagram_ILR.png

···

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page
OpenHIE Architecture Call
.

**Michelle Cox **|****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE
Architecture diagram
. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate
    more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations
    and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

···

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com

Date: Monday, December 14, 2015 at 3:09 PM

To: OpenHIE Architecture ohie-architecture@googlegroups.com

Cc: “Cox, Michelle Louise” miclcox@regenstrief.org

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page
OpenHIE Architecture Call
.

**Michelle Cox **|****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

···

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE
Architecture diagram
. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate
    more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations
    and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com

Date: Monday, December 14, 2015 at 3:09 PM

To: OpenHIE Architecture ohie-architecture@googlegroups.com

Cc: “Cox, Michelle Louise” miclcox@regenstrief.org

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page
OpenHIE Architecture Call
.

**Michelle Cox **|****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

···

From: “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com on behalf of Ryan ryan@jembi.org

Date: Thursday, December 17, 2015 at 1:28 AM

To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe
that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE
Architecture diagram
. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate
    more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations
    and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com

Date: Monday, December 14, 2015 at 3:09 PM

To: OpenHIE Architecture ohie-architecture@googlegroups.com

Cc: “Cox, Michelle Louise” miclcox@regenstrief.org

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page
OpenHIE Architecture Call
.

**Michelle Cox **|****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators) with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to this diagram but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

···

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From: “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com on behalf of Ryan ryan@jembi.org

Date: Thursday, December 17, 2015 at 1:28 AM

To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe
that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE
Architecture diagram
. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate
    more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations
    and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com

Date: Monday, December 14, 2015 at 3:09 PM

To: OpenHIE Architecture ohie-architecture@googlegroups.com

Cc: “Cox, Michelle Louise” miclcox@regenstrief.org

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page
OpenHIE Architecture Call
.

**Michelle Cox **|****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

···

From: Ryan ryan@jembi.org

Date: Friday, December 18, 2015 at 1:23 AM

To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner <litlfred@gmail.com >,
ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators) with indications of which IHE profiles are being spoken and perhaps an indication of transaction
security if possible.

Perhaps this can be similar to
this diagram
but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From: “ohie-architecture@googlegroups.com” <ohie-architecture@googlegroups.com >
on behalf of Ryan ryan@jembi.org

Date: Thursday, December 17, 2015 at 1:28 AM

To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe
that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE
Architecture diagram
. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate
    more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations
    and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com

Date: Monday, December 14, 2015 at 3:09 PM

To: OpenHIE Architecture ohie-architecture@googlegroups.com

Cc: “Cox, Michelle Louise” miclcox@regenstrief.org

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page
OpenHIE Architecture Call
.

**Michelle Cox **|****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

Hi Jamie and Ryan.

Ryan, I used a set/family of slides to try to convey this idea. Here is the deck I used at a recent (October) presentation I did in Manila re: OpenHIE and how it works: https://wiki.ohie.org/download/attachments/13926693/15-08-24%20OpenHIE%27s%20Architecture%20and%20its%20ComponentsDR.pptx?api=v2.

Perhaps the full set of IHE transactions could be overlaid on top of the high-level architecture diagram. Would this give the kind of picture you’re thinking of?

Warmest regards, and Merry Christmas,

Derek

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-architecture@googlegroups.com [mailto:ohie-architecture@googlegroups.com] On Behalf Of Thomas, Jamie
Sent: Friday, December 18, 2015 8:48 AM
To: Ryan Crichton; Grannis, Shaun J; Carl Leitner; ohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

From: Ryan ryan@jembi.org
Date: Friday, December 18, 2015 at 1:23 AM
To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators) with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to this diagram but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From:ohie-architecture@googlegroups.comohie-architecture@googlegroups.com on behalf of Ryan ryan@jembi.org
Date: Thursday, December 17, 2015 at 1:28 AM
To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE Architecture diagram. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.

Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com
Date: Monday, December 14, 2015 at 3:09 PM
To: OpenHIE Architecture ohie-architecture@googlegroups.com
Cc: “Cox, Michelle Louise” miclcox@regenstrief.org
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,
Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,
-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page OpenHIE Architecture Call.

**Michelle Cox ** |****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi Derek,

That is exactly what I think the diagram should convey. Overlaying the transactions is a start but I think there will be additional components like the ILR and the xds.b mediator that may need to be brought out.

Cheers,

Ryan

···

On Fri, Dec 18, 2015 at 10:24 PM Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Jamie and Ryan.

Ryan, I used a set/family of slides to try to convey this idea. Here is the deck I used at a recent (October) presentation I did in Manila re: OpenHIE and how it works: https://wiki.ohie.org/download/attachments/13926693/15-08-24%20OpenHIE%27s%20Architecture%20and%20its%20ComponentsDR.pptx?api=v2.

Perhaps the full set of IHE transactions could be overlaid on top of the high-level architecture diagram. Would this give the kind of picture you’re thinking of?

Warmest regards, and Merry Christmas,

Derek

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-architecture@googlegroups.com [mailto:ohie-architecture@googlegroups.com] On Behalf Of Thomas, Jamie
Sent: Friday, December 18, 2015 8:48 AM
To: Ryan Crichton; Grannis, Shaun J; Carl Leitner; ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

From: Ryan ryan@jembi.org
Date: Friday, December 18, 2015 at 1:23 AM
To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators) with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to this diagram but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From:ohie-architecture@googlegroups.comohie-architecture@googlegroups.com on behalf of Ryan ryan@jembi.org
Date: Thursday, December 17, 2015 at 1:28 AM
To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE Architecture diagram. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com
Date: Monday, December 14, 2015 at 3:09 PM
To: OpenHIE Architecture ohie-architecture@googlegroups.com
Cc: “Cox, Michelle Louise” miclcox@regenstrief.org
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,
Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,
-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page OpenHIE Architecture Call.

**Michelle Cox ** |****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org

Last call for any secondary diagrams around specific implementations people would like to share and discuss on an upcoming OHIE Arch call.

**Jamie Thomas **|****Health Information Project Manager/Communications

Center for Biomedical Informatics

F447BFA7-64CF-416E-9382-5383D9F359EA[15].png

We**’**** ve
moved!**

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9218 | Fax 317-274-9305

Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI

www.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.

···

From: Ryan ryan@jembi.org

Date: Monday, January 4, 2016 at 2:22 AM

To: Derek Ritz derek.ritz@ecgroupinc.com, Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” <sgrannis@regenstrief.org >,
Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Derek,

That is exactly what I think the diagram should convey. Overlaying the transactions is a start but I think there will be additional components like the ILR and the xds.b mediator that may need to be brought out.

Cheers,

Ryan

On Fri, Dec 18, 2015 at 10:24 PM Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Jamie and Ryan.

Ryan, I used a set/family of slides to try to convey this idea. Here is the deck I used at a recent (October) presentation I did in Manila re: OpenHIE
and how it works: https://wiki.ohie.org/download/attachments/13926693/15-08-24%20OpenHIE%27s%20Architecture%20and%20its%20ComponentsDR.pptx?api=v2.

Perhaps the full set of IHE transactions could be overlaid on top of the high-level architecture diagram. Would this give the kind of picture you’re
thinking of?

Warmest regards, and Merry Christmas,

Derek

**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-architecture@googlegroups.com
[mailto:ohie-architecture@googlegroups.com]
On Behalf Of Thomas, Jamie
Sent: Friday, December 18, 2015 8:48 AM
To: Ryan Crichton; Grannis, Shaun J; Carl Leitner;
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

**From:**Ryan ryan@jembi.org
Date: Friday, December 18, 2015 at 1:23 AM
To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner <litlfred@gmail.com >,
ohie-architecture@googlegroups.comohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators)
with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to

this diagram
but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From:ohie-architecture@googlegroups.com” <ohie-architecture@googlegroups.com >
on behalf of Ryan ryan@jembi.org
Date: Thursday, December 17, 2015 at 1:28 AM
To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that
the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany
the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status
and processes for updating the OpenHIE Architecture diagram . This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some
brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current
    diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries
    implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created
    from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases.
    So community members are asked to come up with secondary diagrams around specific implementations and share those with Jamie Thomas (jt48@regenstrief.org ) by Thursday, December 31 so we can have a conversation
    around them on an upcoming architecture call.

Best,

Shaun

From:ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com
Date: Monday, December 14, 2015 at 3:09 PM
To: OpenHIE Architecture ohie-architecture@googlegroups.com
Cc: “Cox, Michelle Louise” miclcox@regenstrief.org
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page

OpenHIE Architecture Call
.

**Michelle Cox ** |****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout
.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

Hi All,

Here are some thoughts & suggestions regarding more detailed architecture images that would capture things like the infoman.

Initially, we believe the Infoman corresponds strongly to this type of entity aggregation pattern (https://msdn.microsoft.com/en-us/library/ff649505.aspx). While the interoperability layer reflects: https://msdn.microsoft.com/en-us/library/ff647328.aspx.

Both of these are utilities that are there to support types integration, and the wiki link in Ryan’s email identifies a number of these types of integration tools or utilities. They are not ‘2nd class’ - they are 1st class but they fall into a different family of concerns - namely, one of systems integration. For more detailed frameworks, we would suggest that we stop showing the middle interoperability layer as a black box and start breaking out its contained services - namely the Interoperability layer, Infoman, and other similar utilities.

This is based on our feeling that the existing categories are still a strong simplifying message that we should keep. e.g.,:

  • ”There’s POC apps & services",
  • “there’s HIE services”, and
  • “there’s HIS integration services/utilities”
    The problem we may could create with the Infoman or other integration services in the HIE grouping, is that we are trying to insert an element out of its natural container, or would create a new container with the ILR using a ‘dotted box’, which we believe would increase confusion as we use dotted boxes for other types of groupings.

Here is a visual of what we are suggesting …

Screen Shot 2016-01-05 at 10.04.19 AM.png

Hope everyone had a good Holiday season. Looking forward to discussing in greater depth.

All the best,

Scott and Ed

F447BFA7-64CF-416E-9382-5383D9F359EA[15].png

···

On Mon, Jan 4, 2016 at 1:56 PM, Thomas, Jamie jt48@regenstrief.org wrote:

Last call for any secondary diagrams around specific implementations people would like to share and discuss on an upcoming OHIE Arch call.

**Jamie Thomas **|****Health Information Project Manager/Communications

Center for Biomedical Informatics

We**’**** ve
moved!**

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9218 | Fax 317-274-9305

Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI

www.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.

From: Ryan ryan@jembi.org

Date: Monday, January 4, 2016 at 2:22 AM

To: Derek Ritz derek.ritz@ecgroupinc.com, Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” <sgrannis@regenstrief.org >,
Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Derek,

That is exactly what I think the diagram should convey. Overlaying the transactions is a start but I think there will be additional components like the ILR and the xds.b mediator that may need to be brought out.

Cheers,

Ryan

On Fri, Dec 18, 2015 at 10:24 PM Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Jamie and Ryan.

Ryan, I used a set/family of slides to try to convey this idea. Here is the deck I used at a recent (October) presentation I did in Manila re: OpenHIE
and how it works: https://wiki.ohie.org/download/attachments/13926693/15-08-24%20OpenHIE%27s%20Architecture%20and%20its%20ComponentsDR.pptx?api=v2.

Perhaps the full set of IHE transactions could be overlaid on top of the high-level architecture diagram. Would this give the kind of picture you’re
thinking of?

Warmest regards, and Merry Christmas,

Derek

**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-architecture@googlegroups.com
[mailto:ohie-architecture@googlegroups.com]
On Behalf Of Thomas, Jamie
Sent: Friday, December 18, 2015 8:48 AM
To: Ryan Crichton; Grannis, Shaun J; Carl Leitner;
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

**From:**Ryan ryan@jembi.org
Date: Friday, December 18, 2015 at 1:23 AM
To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner <litlfred@gmail.com >,
ohie-architecture@googlegroups.comohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators)
with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to

this diagram
but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From:ohie-architecture@googlegroups.com” <ohie-architecture@googlegroups.com >
on behalf of Ryan ryan@jembi.org
Date: Thursday, December 17, 2015 at 1:28 AM
To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that
the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany
the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status
and processes for updating the OpenHIE Architecture diagram . This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some
brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current
    diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries
    implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created
    from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases.
    So community members are asked to come up with secondary diagrams around specific implementations and share those with Jamie Thomas (jt48@regenstrief.org ) by Thursday, December 31 so we can have a conversation
    around them on an upcoming architecture call.

Best,

Shaun

From:ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com
Date: Monday, December 14, 2015 at 3:09 PM
To: OpenHIE Architecture ohie-architecture@googlegroups.com
Cc: “Cox, Michelle Louise” miclcox@regenstrief.org
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page

OpenHIE Architecture Call
.

**Michelle Cox ** |****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout
.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

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

Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

Thanks Scott and Ed. So, what I’m hearing is that you agree with having (in addition) a new more complex diagram but would suggest that we keep items grouped into their logical groups. This would allow the diagram to relate back to the higher level diagram and prevent confusion.

Is this mostly correct?

Cheers,

Ryan

F447BFA7-64CF-416E-9382-5383D9F359EA[15].png

Screen Shot 2016-01-05 at 10.04.19 AM.png

···

On Mon, Jan 4, 2016 at 1:56 PM, Thomas, Jamie jt48@regenstrief.org wrote:

Last call for any secondary diagrams around specific implementations people would like to share and discuss on an upcoming OHIE Arch call.

**Jamie Thomas **|****Health Information Project Manager/Communications

Center for Biomedical Informatics

We**’**** ve
moved!**

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9218 | Fax 317-274-9305

Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI

www.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.

From: Ryan ryan@jembi.org

Date: Monday, January 4, 2016 at 2:22 AM

To: Derek Ritz derek.ritz@ecgroupinc.com, Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” <sgrannis@regenstrief.org >,
Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Derek,

That is exactly what I think the diagram should convey. Overlaying the transactions is a start but I think there will be additional components like the ILR and the xds.b mediator that may need to be brought out.

Cheers,

Ryan

On Fri, Dec 18, 2015 at 10:24 PM Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Jamie and Ryan.

Ryan, I used a set/family of slides to try to convey this idea. Here is the deck I used at a recent (October) presentation I did in Manila re: OpenHIE
and how it works: https://wiki.ohie.org/download/attachments/13926693/15-08-24%20OpenHIE%27s%20Architecture%20and%20its%20ComponentsDR.pptx?api=v2.

Perhaps the full set of IHE transactions could be overlaid on top of the high-level architecture diagram. Would this give the kind of picture you’re
thinking of?

Warmest regards, and Merry Christmas,

Derek

**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-architecture@googlegroups.com
[mailto:ohie-architecture@googlegroups.com]
On Behalf Of Thomas, Jamie
Sent: Friday, December 18, 2015 8:48 AM
To: Ryan Crichton; Grannis, Shaun J; Carl Leitner;
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

**From:**Ryan ryan@jembi.org
Date: Friday, December 18, 2015 at 1:23 AM
To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner <litlfred@gmail.com >,
ohie-architecture@googlegroups.comohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators)
with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to

this diagram
but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From:ohie-architecture@googlegroups.com” <ohie-architecture@googlegroups.com >
on behalf of Ryan ryan@jembi.org
Date: Thursday, December 17, 2015 at 1:28 AM
To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that
the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany
the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status
and processes for updating the OpenHIE Architecture diagram . This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some
brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current
    diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries
    implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created
    from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases.
    So community members are asked to come up with secondary diagrams around specific implementations and share those with Jamie Thomas (jt48@regenstrief.org ) by Thursday, December 31 so we can have a conversation
    around them on an upcoming architecture call.

Best,

Shaun

From:ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com
Date: Monday, December 14, 2015 at 3:09 PM
To: OpenHIE Architecture ohie-architecture@googlegroups.com
Cc: “Cox, Michelle Louise” miclcox@regenstrief.org
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,

-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page

OpenHIE Architecture Call
.

**Michelle Cox ** |****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.

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

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout
.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

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


Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

Oops… hit “reply” instead of “reply all”. Thanks, Ryan, for pointing that out. :slight_smile:

Please see message, below…

image001.png

···

From: Derek Ritz [mailto:derek.ritz@ecgroupinc.com]
Sent: Thursday, January 7, 2016 9:39 AM
To: Ryan Crichton
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all.

Do we want to be able to indicate or graphically suggest the capability to support federated directories of facility and HW info? I think this is an important point and an almost universal requirement; it might be helpful to show it as a feature of OpenHIE (and even show “how” we do it, if we can).

Warmest regards,

Derek.

On Thu, Jan 7, 2016 at 3:02 AM, Ryan Crichton ryan@jembi.org wrote:

Thanks Scott and Ed. So, what I’m hearing is that you agree with having (in addition) a new more complex diagram but would suggest that we keep items grouped into their logical groups. This would allow the diagram to relate back to the higher level diagram and prevent confusion.

Is this mostly correct?

Cheers,

Ryan

On Tue, Jan 5, 2016 at 6:15 PM Scott Teesdale steesdale@instedd.org wrote:

Hi All,

Here are some thoughts & suggestions regarding more detailed architecture images that would capture things like the infoman.

Initially, we believe the Infoman corresponds strongly to this type of entity aggregation pattern (https://msdn.microsoft.com/en-us/library/ff649505.aspx). While the interoperability layer reflects: https://msdn.microsoft.com/en-us/library/ff647328.aspx.

Both of these are utilities that are there to support types integration, and the wiki link in Ryan’s email identifies a number of these types of integration tools or utilities. They are not ‘2nd class’ - they are 1st class but they fall into a different family of concerns - namely, one of systems integration. For more detailed frameworks, we would suggest that we stop showing the middle interoperability layer as a black box and start breaking out its contained services - namely the Interoperability layer, Infoman, and other similar utilities.

This is based on our feeling that the existing categories are still a strong simplifying message that we should keep. e.g.,:

  • ”There’s POC apps & services",
  • “there’s HIE services”, and
  • “there’s HIS integration services/utilities”

The problem we may could create with the Infoman or other integration services in the HIE grouping, is that we are trying to insert an element out of its natural container, or would create a new container with the ILR using a ‘dotted box’, which we believe would increase confusion as we use dotted boxes for other types of groupings.

Here is a visual of what we are suggesting …

Inline image 1

Hope everyone had a good Holiday season. Looking forward to discussing in greater depth.

All the best,

Scott and Ed

On Mon, Jan 4, 2016 at 1:56 PM, Thomas, Jamie jt48@regenstrief.org wrote:

Last call for any secondary diagrams around specific implementations people would like to share and discuss on an upcoming OHIE Arch call.

**Jamie Thomas **|****Health Information Project Manager/Communications

Center for Biomedical Informatics

We**’**ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9218 | Fax 317-274-9305

Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI

www.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.

From: Ryan ryan@jembi.org
Date: Monday, January 4, 2016 at 2:22 AM
To: Derek Ritz derek.ritz@ecgroupinc.com, Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Derek,

That is exactly what I think the diagram should convey. Overlaying the transactions is a start but I think there will be additional components like the ILR and the xds.b mediator that may need to be brought out.

Cheers,

Ryan

On Fri, Dec 18, 2015 at 10:24 PM Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Jamie and Ryan.

Ryan, I used a set/family of slides to try to convey this idea. Here is the deck I used at a recent (October) presentation I did in Manila re: OpenHIE and how it works: https://wiki.ohie.org/download/attachments/13926693/15-08-24%20OpenHIE%27s%20Architecture%20and%20its%20ComponentsDR.pptx?api=v2.

Perhaps the full set of IHE transactions could be overlaid on top of the high-level architecture diagram. Would this give the kind of picture you’re thinking of?

Warmest regards, and Merry Christmas,

Derek

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-architecture@googlegroups.com [mailto:ohie-architecture@googlegroups.com] On Behalf Of Thomas, Jamie
Sent: Friday, December 18, 2015 8:48 AM
To: Ryan Crichton; Grannis, Shaun J; Carl Leitner; ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

From: Ryan ryan@jembi.org
Date: Friday, December 18, 2015 at 1:23 AM
To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators) with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to this diagram but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From:ohie-architecture@googlegroups.comohie-architecture@googlegroups.com on behalf of Ryan ryan@jembi.org
Date: Thursday, December 17, 2015 at 1:28 AM
To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE Architecture diagram. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.

Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com
Date: Monday, December 14, 2015 at 3:09 PM
To: OpenHIE Architecture ohie-architecture@googlegroups.com
Cc: “Cox, Michelle Louise” miclcox@regenstrief.org
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,
Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,
-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page OpenHIE Architecture Call.

**Michelle Cox ** |****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Scott Teesdale

Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.
+1 (905) 515-0045
www.ecgroupinc.com

Hi all, thanks for continuing the thread here… looking forward to moving things forward on our next call. To quickly respond to the comments above.

Ryan: Yes, I believe we are on the same page. A more evolved diagram, where we stick to the same categorizations, would be useful for the techies/architects/standards folks out there. Also, I would be curious to hear from others who are involved with the other types of integration tools/utilities noted in that wiki page, to see what they think too. We have primarily engaged around the infoman.

Derek: Re: federation of a single registry, we have observed the potential for multiple patterns among FRs related to their governance and integration patterns. I think for us to adequately depict federation, we will need to identify a tangible implementation first, and use that as the basis. Then weigh that with the other patterns OHIE has observed and decide what we recognize as appropriate to promote for countries to replicate successful patterns. **Side note, we would be happy to have this discussion on a future FR community call as well, to better depict the requirements and patterns as they intersect with governance / technology patterns. ** All this to say, I know HWRs are often federated … so perhaps it would be totally applicable in their community.

All the best,

Scott

image001.png

···

On Thu, Jan 7, 2016 at 9:33 AM, Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Oops… hit “reply” instead of “reply all”. Thanks, Ryan, for pointing that out. :slight_smile:

Please see message, below…

From: Derek Ritz [mailto:derek.ritz@ecgroupinc.com]
Sent: Thursday, January 7, 2016 9:39 AM
To: Ryan Crichton
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all.

Do we want to be able to indicate or graphically suggest the capability to support federated directories of facility and HW info? I think this is an important point and an almost universal requirement; it might be helpful to show it as a feature of OpenHIE (and even show “how” we do it, if we can).

Warmest regards,

Derek.

On Thu, Jan 7, 2016 at 3:02 AM, Ryan Crichton ryan@jembi.org wrote:

Thanks Scott and Ed. So, what I’m hearing is that you agree with having (in addition) a new more complex diagram but would suggest that we keep items grouped into their logical groups. This would allow the diagram to relate back to the higher level diagram and prevent confusion.

Is this mostly correct?

Cheers,

Ryan

On Tue, Jan 5, 2016 at 6:15 PM Scott Teesdale steesdale@instedd.org wrote:

Hi All,

Here are some thoughts & suggestions regarding more detailed architecture images that would capture things like the infoman.

Initially, we believe the Infoman corresponds strongly to this type of entity aggregation pattern (https://msdn.microsoft.com/en-us/library/ff649505.aspx). While the interoperability layer reflects: https://msdn.microsoft.com/en-us/library/ff647328.aspx.

Both of these are utilities that are there to support types integration, and the wiki link in Ryan’s email identifies a number of these types of integration tools or utilities. They are not ‘2nd class’ - they are 1st class but they fall into a different family of concerns - namely, one of systems integration. For more detailed frameworks, we would suggest that we stop showing the middle interoperability layer as a black box and start breaking out its contained services - namely the Interoperability layer, Infoman, and other similar utilities.

This is based on our feeling that the existing categories are still a strong simplifying message that we should keep. e.g.,:

  • ”There’s POC apps & services",
  • “there’s HIE services”, and
  • “there’s HIS integration services/utilities”
    The problem we may could create with the Infoman or other integration services in the HIE grouping, is that we are trying to insert an element out of its natural container, or would create a new container with the ILR using a ‘dotted box’, which we believe would increase confusion as we use dotted boxes for other types of groupings.

Here is a visual of what we are suggesting …

Hope everyone had a good Holiday season. Looking forward to discussing in greater depth.

All the best,

Scott and Ed

On Mon, Jan 4, 2016 at 1:56 PM, Thomas, Jamie jt48@regenstrief.org wrote:

Last call for any secondary diagrams around specific implementations people would like to share and discuss on an upcoming OHIE Arch call.

**Jamie Thomas **|****Health Information Project Manager/Communications

Center for Biomedical Informatics

We**’**ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

Tel 317-274-9218 | Fax 317-274-9305

Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI

www.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.

From: Ryan ryan@jembi.org
Date: Monday, January 4, 2016 at 2:22 AM
To: Derek Ritz derek.ritz@ecgroupinc.com, Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Derek,

That is exactly what I think the diagram should convey. Overlaying the transactions is a start but I think there will be additional components like the ILR and the xds.b mediator that may need to be brought out.

Cheers,

Ryan

On Fri, Dec 18, 2015 at 10:24 PM Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Jamie and Ryan.

Ryan, I used a set/family of slides to try to convey this idea. Here is the deck I used at a recent (October) presentation I did in Manila re: OpenHIE and how it works: https://wiki.ohie.org/download/attachments/13926693/15-08-24%20OpenHIE%27s%20Architecture%20and%20its%20ComponentsDR.pptx?api=v2.

Perhaps the full set of IHE transactions could be overlaid on top of the high-level architecture diagram. Would this give the kind of picture you’re thinking of?

Warmest regards, and Merry Christmas,

Derek

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-architecture@googlegroups.com [mailto:ohie-architecture@googlegroups.com] On Behalf Of Thomas, Jamie
Sent: Friday, December 18, 2015 8:48 AM
To: Ryan Crichton; Grannis, Shaun J; Carl Leitner; ohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Thanks for clarifying this Ryan. What do people think about this?

-Jamie

From: Ryan ryan@jembi.org
Date: Friday, December 18, 2015 at 1:23 AM
To: Jamie Thomas jt48@regenstrief.org, “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi Jamie,

No I don’t think so. I’m envisaging a single overall architecture diagram which shows each of the components (including the ILR and the various mediators) with indications of which IHE profiles are being spoken and perhaps an indication of transaction security if possible.

Perhaps this can be similar to this diagram but with a more general focus on all the components and a list of IHE profiles used for each arrow. I think this would be useful to link the high level diagram we have now to the workflows more effectively.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 5:24 PM Thomas, Jamie jt48@regenstrief.org wrote:

Thanks for the feedback Ryan. Can you clarify for me if you saying there should be a different diagram for every workflow?

-Jamie

From:ohie-architecture@googlegroups.comohie-architecture@googlegroups.com on behalf of Ryan ryan@jembi.org
Date: Thursday, December 17, 2015 at 1:28 AM
To: “Grannis, Shaun J” sgrannis@regenstrief.org, Carl Leitner litlfred@gmail.com, “ohie-architecture@googlegroups.comohie-architecture@googlegroups.com

Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,

@Carl, that version of the digram looks good to me. It still looks fairly simple for casual viewers in my eyes.

@Shaun, thanks for the summary, I think those points resonate well with what was discussed on the call. However, I do have one point further. I think that the lower level, more detailed diagrams shouldn’t only be for specific implementations. I believe that we as OpenHIE should maintain a general more detailed diagram that describes how OpenHIE fits together using our reference tools. A diagram that would accompany the workflow specifications.

Interested to hear how other feel about this.

Cheers,

Ryan

On Thu, Dec 17, 2015 at 12:36 AM Grannis, Shaun J sgrannis@regenstrief.org wrote:

Thanks for getting this started Carl!

To put Carl’s diagram in context, and for the larger group that hasn’t been able to participate in recent discussions, we’ve been reviewing the current status and processes for updating the OpenHIE Architecture diagram. This topic was discussed on Monday’s OpenHIE Architecture call. As a follow up I wanted to send out some brief points made on the call and what consensus was reached.

  • The current architecture diagram is intended to communicate elements of OpenHIE at a conceptual level, it is intended to be “inspirational”.
  • The current architecture diagram is also intended for people new to OpenHIE and those seeking an overview. Consensus on the call was that the current diagram serves these purposes well, however we acknowledged a subsequent need to be able to communicate more fine-grained, implementation specific details.
  • Community members are encouraged to create artifacts based on this diagram, following the same look and feel presently used, tailored to specific communities/countries implementations.
  • It is not contradictory to use the diagram to explain both the high-level architecture of OpenHIE and our communities, as the communities were created from the architecture.
    Consensus was the diagram serves a purpose and should stay the same. However there is a level missing that goes into more detail around component use cases. So community members are asked to come up with secondary diagrams around specific implementations and share those with Jamie Thomas (jt48@regenstrief.org) by Thursday, December 31 so we can have a conversation around them on an upcoming architecture call.

Best,

Shaun

From: ohie-architecture@googlegroups.com on behalf of Carl Leitner litlfred@gmail.com
Date: Monday, December 14, 2015 at 3:09 PM
To: OpenHIE Architecture ohie-architecture@googlegroups.com
Cc: “Cox, Michelle Louise” miclcox@regenstrief.org
Subject: Re: Reminder: OpenHIE Architecture Call - Monday, December 14th - 10:00 a.m. ET

Hi all,
Per the conversation today, here is a (very rough) attempt at the Fisher Price version of the OpenHIE high-level diagram which incorporates the ILR.

Cheers,
-carl

On Friday, December 11, 2015 at 10:33:53 AM UTC-5, Cox, Michelle Louise wrote:

Just another reminder – there will be an OpenHIE Architecture call this upcoming Monday, December 14th at 10:00 a.m. ET.

You can find details out on the wiki page OpenHIE Architecture Call.

**Michelle Cox ** |****Program Assistant

cid:image001.png@01D11112.EEAD66C0

We’ve moved!

Please update your records and visit us at our new address:

1101 West Tenth Street

Indianapolis, IN 46202

Web and email addresses, and phone numbers will remain the same.

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

Skype ID: miclcox | Facebook.com/regenstriefinstitute

www.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.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Scott Teesdale

Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org


You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.

+1 (905) 515-0045
www.ecgroupinc.com

Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn