To try to foster/illicit more discussion on this topic, I’m cross-posting this note from the leads community to the sandbox community. 
···
On Wednesday, May 18, 2016 at 9:58:44 AM UTC-4, derek.ritz wrote:
Thanks, Jamie (and Shaun).
My sense is that the network of
interoperability labs can and should play two key roles for OpenHIE:
- Inform our designs and specifications and
help them be more evidence-based (an applied research role);- Provide an important and useful way for
OpenHIE to be “brought to market” (a channel management role).
The OpenHIE community of communities
supports and articulates our initiative’s mission and vision. It develops and
documents the enterprise architecture (the blueprint) including: the use cases,
the design patterns, and the interoperability profiles that realize these
workflows. Crucially, it also provides the structure the helps us manage and
govern our communities’ interactions with each other, with our donor supporters,
and with other interested parties.
What should we do differently? I think the
thing we should do differently is to more clearly draw a line between OpenHIE
as a blueprint and OpenHIE as a product stack. I think the labs afford us
an elegant way to do this.
Presently, the OpenHIE communities include
a number of software development shops. This served us well over our design and
engineering phases. The focus of these first phases was reflected in our early governance
design; we largely organized ourselves around technology products. In some
communities, there is only one technology product represented; in others there
is more than one. In my view, we should leverage our labs to give us a way to
separate the definition of what OpenHIE is
(our blueprint) from examples of an OpenHIE-conformant product (e.g. OpenEMPI & MEDIC CR as conformant client registries
or Resource Map & DHIS2 as conformant facility directories).
Guarding against channel conflict is
important. My sense is that for OpenHIE to thrive during its new
implementation-focused phase, it will need to become clearer to “the market” that
OpenHIE is not a closed club of software
products. Even the unintentional illusion
of this creates the potential for channel conflict (as an example, try to find
information about MEDIC CR on our client registry wiki page: https://wiki.ohie.org/display/SUB/Client+Registry+Community).
In my view, our OpenHIE communities should
leverage the interoperability labs as a way to de-couple ourselves from
specific software and focus on our core product: the blueprint and its
governance.
I hope this idea can enjoy an active
discussion on this thread. J
Warmest regards,
Derek.
On Tuesday, May 17, 2016 at 7:25:17 AM UTC-4, Jamie Thomas wrote:
Derek,
On yesterday’s call you talked about a lab concept note. Shaun had a question but we ran out of time so as a follow up from the discussion here’s a brief summary of the question:
In the context of these regional learning labs, what would we do differently using the HEAL lab as an example? Conversations/relationships currently exist with members of the HEAL lab, so what would we be doing differently?
There is obvious value in the concept regional labs, so how would we do this well?
Let’s continue the discussion here.
**Jamie Thomas **|****Health Information Project Manager/Communications
Center for Biomedical Informatics
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: jt...@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI
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: “ohie-le...@googlegroups.com” ohie-le...@googlegroups.com on behalf of "mic...@regenstrief.org "
mic...@regenstrief.orgReply-To: “ohie-le...@googlegroups.com” ohie-le...@googlegroups.com
Date: Monday, May 16, 2016 at 4:03 PM
To: “ohie-le...@googlegroups.com” ohie-le...@googlegroups.com
Subject: OpenHIE Leadership Call - Monday, May 16th
If you could not join us for the OpenHIE Leadership call today, you can read the minutes or listen to the recording on
2016-05-16 Leadership Call wiki page.
The next OpenHIE Leadership call will be at 10:00 a.m. EDT on Monday, June 20th.
Thank you!
**Michelle Cox ** |****Program Assistant, Global Health Informatics
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 | Regenstrief Institute, Inc. | Indianapolis IN
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 Leadership” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-leadersh...@googlegroups.com.For more options, visit https://groups.google.com/d/optout.