Thanks Jamie,
The only feedback I have is inline with previous comments around consistency in naming: The different LMIS / Logistics Management Info System labelling above and below the line is a little confusing. I’d recommend using just LMIS or spelling
the entire thing out as Logistics Management Information System - both have good domain recognition in the places OpenHIE is at in my experience.
Other than that minor point I think the diagram works well for what I think its intended level of communication is.
One possible suggestion, if it hasn’t been mentioned already, for the problem of stacking the HIE components & registries boxes is to stack the icons in each box respectively. Visually that’d be choose a maximum number of icons wide either components
or registries can span, then stack registries within the registry box and components within the component box up to that maximum, overflowing to new rows, but don’t stack the registries over the components or the other way round. As more of either of those
are added the diagram won’t forever grow horizontally. For how I plan to leverage the diagram to be expanded to show the intersection between HIE and the supply chain, this stacking would work just fine. Just a thought.
Best,
Josh
···
On Jun 17, 2019, at 4:09 PM, Jack Bowie jack.bowie@gmail.com wrote:
I’d like to second Ron’s comments on use of PoC (use your favorite expansion) rather than External Systems and Registry Linking Service (spelled out).
Jack
On Mon, Jun 17, 2019 at 9:05 AM Thomas, Jamie jt48@regenstrief.org wrote:
Thanks everyone for the second round feedback. It doesn’t look like we’ve had anyone vote to accept the diagram as it was sent out so this may require further conversation. We will review the feedback provided and determine the best way
to proceed.
If anyone has yet to give feedback to “agree” or “disagree” please feel free to as we decide how to proceed.
Jamie Thomas |* Community
Manager*
Center for Biomedical Informatics
<image001.png>
1101 West Tenth Street
Indianapolis, IN 46202
Tel 317-274-9218 | Fax 317-274-9305
Email: jt48@regenstrief.org | Skype: jamie.thomas5670
Twitter: @Regenstrief
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: **“Ron G. Parker” rgparker57@eastlink.ca
**Date: **Friday, June 14, 2019 at 11:43 AM
**To: **Carl Leitner litlfred@gmail.com
**Cc: **“Thomas, Jamie” jt48@regenstrief.org, “‘Fourie, Carl’” <cfourie@path.org >,
“jennifer.e.shivers@gmail.com” jennifer.e.shivers@gmail.com, Derek Ritz <derek.ritz@ecgroupinc.com >,
‘Daniel Futerman’ daniel.futerman@jembi.org, ‘Ryan Crichton’ ryan.crichton@jembi.org, Jack Bowie <jack.bowie@gmail.com >,
“ohie-architecture@googlegroups.com” ohie-architecture@googlegroups.com
**Subject: **RE: (REVIEW & VOTE) 2019 Architecture Diagram
Thanks Carl, this is helpful.
Ron G Parker | mail: rgparker57@eastlink.ca |
mobile: +1-902-222-7716 | skype: rongparker | timezone: ADT (UTC -3)
From: ohie-architecture@googlegroups.com ohie-architecture@googlegroups.com ** On
Behalf Of **Carl Leitner
Sent: June 14, 2019 11:39
To: Ron G. Parker rgparker57@eastlink.ca
Cc: Thomas, Jamie jt48@regenstrief.org; Fourie, Carl <cfourie@path.org >;
Jennifer E Shivers jennifer.e.shivers@gmail.com; Derek Ritz (ecGroup) <derek.ritz@ecgroupinc.com >; Daniel Futerman
daniel.futerman@jembi.org; Ryan Crichton ryan.crichton@jembi.org; Jack Bowie <jack.bowie@gmail.com >;
OHIE Architecture list ohie-architecture@googlegroups.com
Subject: Re: (REVIEW & VOTE) 2019 Architecture Diagram
Resending for visibility w/ my correct email (hopefully).
Cheers,
-carl
On Jun 14, 2019, at 10:33 AM, Carl Leitner litlfred@ibiblio.org wrote:
Hi Ron,
In regards to your second bullet, the are two different uses of eRegistry which may be causing some confusion. To be a bit more precise, by an eRegister/eRegistry I did not
mean something like a National Cancer Registry, rather something like how OpenSRP or DHIS2 Tracker is commonly used. So we have two uses of the term eRegistry. The first, I would describe as something like :
- A system used for reporting all cases of a specific disease/health condition within a jurisdiction for programmatic monitoring purposes at the central level
The second, which is where WHO has started using ‘digital client record’ to help disambiguate, is something like
- A system used by providers during the provision of care for the management of client information related to a specific disease or health condition within a care plan at the
facility or community level
Certainly information from the second type of system could be used to feed the first type of system, though I would expect that the information requirements in the first is
significantly less than the second.
I am not exactly sure what you mean by 'operational components’ and if that would apply to both of the definitions above.
Cheers,
-carl
On Jun 14, 2019, at 8:38 AM, Ron G. Parker <rgparker57@eastlink.ca > > > > > wrote:
My vote is this is not quite ready yet (sorry, it seems things jump out at you when it is time to commit… funny how that works)
I (mostly) agree with Carl here.
- Solid lines rather than dotted.
- I don’t believe that registries or other operational components should be lumped in with the “Digital Client Record”. It is very important to differentiate between the SHR (client / patient-centric data) and other data that is used to make health service delivery
possible.- My preference is “Place of Service” rather than “External Systems”. Bottom row is not meant to be entirely comprehensive but rather representative (deserves a footnote?)
I would also add that having InterLinked Registries as a cog wheel and then showing the registries above could be a bit confusing. The concept of InterLinked Registries is a combination of the registries in the architecture and access
mechanisms (service) that correlate registries to meet business needs. Can we re-label the cog wheel to be “Registry Linking Service”?
Ron G Parker | mail: rgparker57@eastlink.ca |
mobile: +1-902-222-7716 | skype: rongparker | timezone: ADT (UTC -3)
From: ohie-architecture@googlegroups.com ohie-architecture@googlegroups.com ** On
Behalf Of **Carl Leitner
Sent: June 14, 2019 09:18
To: Thomas, Jamie jt48@regenstrief.org
Cc: Fourie, Carl cfourie@path.org; Jennifer E Shivers jennifer.e.shivers@gmail.com; litlfred@ibiblio.org ;
Derek Ritz derek.ritz@ecgroupinc.com; Daniel Futerman <daniel.futerman@jembi.org >;
Ryan Crichton ryan.crichton@jembi.org; Jack Bowie <jack.bowie@gmail.com >;
OHIE Architecture list ohie-architecture@googlegroups.com
Subject: Re: (REVIEW & VOTE) 2019 Architecture Diagram
This is looking great from my perspective. A few minor comments:
- Metadata and Business should be aligned vertically
- For those trying to modify the diagram, dotted lines can present a problem - can we switch to a solid line?
- I am not sure that I can accurately explain the distinction between mobile system and EMR, and that this distinction is significant enough to call out in the diagram. Maybe we can combine them? Also, see attached icon that I have been
using Noting that the WHO is using the language ‘Digiital Client Record’ to include both EMRs and what have been called eRegisters and eRegistries. This really goes back to the discussion as to what
exactly goes in the bottom row - are they type of systems by business domain, are they places of service. Looking at the rest of the row it seems more about the type.of system.
- On all our assets under ohie.net and wiki.ohie.net we
jump back and forth between External System and PoService where P is either Point of Place. It would be great to settle on one term and update these pages. Not withstanding the unfortunate acronym, I have to admit a preference for PoS. External System could
create confusion in particular as we interface with other back end systems. For example if we utilize an eGovernment system such as mobile payment gateway or SMS flow engine as part of our infrastructure, it would be external to the HIE, but would not in
my mind be “below the line.”
Cheers,
-carl
On Fri, Jun 14, 2019, 07:21 Thomas, Jamie jt48@regenstrief.org wrote:
In case anyone was having trouble opening the file sent before here is a PDF version.
Jamie Thomas |* Community
Manager*
Center for Biomedical Informatics
1101 West Tenth Street
Indianapolis, IN 46202
Tel 317-274-9218 | Fax 317-274-9305
Email: jt48@regenstrief.org | Skype: jamie.thomas5670
Twitter: @Regenstrief
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: **“Thomas, Jamie” jt48@regenstrief.org
**Date: **Thursday, June 13, 2019 at 12:44 PM
**To: **“Fourie, Carl” cfourie@path.org, "jennifer.e.shivers@gmail.com "
jennifer.e.shivers@gmail.com, "litlfred@ibiblio.org "
litlfred@ibiblio.org
**Cc: **Derek Ritz <derek.ritz@ecgroupinc.com >, Daniel Futerman
daniel.futerman@jembi.org, Ryan Crichton <ryan.crichton@jembi.org >,
Jack Bowie jack.bowie@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com
**Subject: **Re: (REVIEW & VOTE) 2019 Architecture Diagram
Thank you all for your input on the OHIE architecture diagram over the last few days. We have taken your feedback and made minor changes to the diagram, see attached. Please take a look at the revised diagram and remember (as Shaun put
it), “consider whether this diagram achieves the goal of providing an overarching sense of the OpenHIE architecture, with the expectation that there is much more detail underneath to be unpacked through exploration of the particular real-world needs.”
Couple other things to think about. One, the UHC community had a call today and discussed their roadmap for the next 12 months. They plan to take a look at how the UHC could be represented in the diagram in the future (fall 2019). Two,
we recognize that the diagram will need to be flexible to support unique implementer needs and we are working on a way in which the community can create customizable diagrams using movable icons.
ACTION ITEM: Process to gain consensus will be the same as before. We ask that members
of the Architecture Review Board take a look at this latest version and simply reply to this email as to whether they ‘Agree’ or ‘Disagree’
with the diagram. If anyone disagrees with what they see or do not see please provide some reasoning around why.
Please respond by EOD Friday, June 14
Jamie Thomas |* Community
Manager*
Center for Biomedical Informatics
1101 West Tenth Street
Indianapolis, IN 46202
Tel 317-274-9218 | Fax 317-274-9305
Email: jt48@regenstrief.org | Skype: jamie.thomas5670
Twitter: @Regenstrief
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-architecture@googlegroups.com "
ohie-architecture@googlegroups.com on behalf of “Fourie, Carl” cfourie@path.org
**Date: **Wednesday, June 12, 2019 at 3:21 AM
**To: **“jennifer.e.shivers@gmail.com” <jennifer.e.shivers@gmail.com >,
“litlfred@ibiblio.org” litlfred@ibiblio.org
**Cc: **Derek Ritz <derek.ritz@ecgroupinc.com >, Daniel Futerman
daniel.futerman@jembi.org, Ryan Crichton <ryan.crichton@jembi.org >,
Jack Bowie jack.bowie@gmail.com, "ohie-architecture@googlegroups.com "
ohie-architecture@googlegroups.com
**Subject: **Re: (REVIEW & VOTE) 2019 Architecture Diagram
HI Jennifer,
We are bringing this to light (all be it a little slowly) so I heed the comments here and I think we will need to know where things are going to plug in – but in short I don’t think we have a “diagram” that we “just haven’t sent in for
approval yet” and we still need to build it. We are working on roadmap tomorrow and will add this to the conversation – I don’t think we need to hold on us for now. Once we have the “pattern” for OpenHIE we can easily do an interim update would be my option.
Cheers
Carl Fourie
Senior Technical Advisor Cape Town | South Africa
tel / whatsapp: +27.71.540.4477
skype: carl.fourie17
**stay connected: @DigitalSQR ****| **digitalsquare.org
- The information in this message, including any attachments, is intended only for the designated recipient(s), and may be privileged,
confidential, or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, alteration, dissemination, retention, distribution, or use in any way of this message, its contents, and any attachments,
is strictly prohibited. If you have received this message in error, please notify the sender immediately by reply e-mail and delete this message.*
**From: **OHIE list <ohie-architecture@googlegroups.com >
on behalf of Jennifer Shivers jennifer.e.shivers@gmail.com
**Date: **Tuesday, 11 June 2019 at 20:53
**To: **Frederick Leitner litlfred@ibiblio.org
**Cc: **Derek Ritz <derek.ritz@ecgroupinc.com >, Daniel Futerman
daniel.futerman@jembi.org, Ryan Crichton <ryan.crichton@jembi.org >,
Jack Bowie jack.bowie@gmail.com, OHIE list ohie-architecture@googlegroups.com
**Subject: **Re: (REVIEW & VOTE) 2019 Architecture Diagram
Carl,
Is the insurance team working on what they need from an architecture perspective?
Jennifer
On Jun 11, 2019, at 2:48 PM, Carl Leitner litlfred@gmail.com wrote:
Hi all,
I must admit to be slightly confused as to the “doing one at a time” vs “all at once.” In the first diagram, we have an SHR, an HMIS and an LMIS in the set of components, and then have things like a PR in the metadata registries. Are
we saying that health financing will be added into the main diagram or we will generate a new diagram for it specifically?
Also noting that the HMIS may also need some other components that are not reflected here such as an indicator registry (flagging for @James K) or a perhaps more broadly a knowledge repository:
https://www.hl7.org/fhir/capabilitystatement-knowledge-repository.html
Knowing that decisions on what’s needed for each community may yet need to be done, I had thought we were first creating the framework for the diagrams for each business domain.
Cheers,
-carl
On Tue, Jun 11, 2019, 12:21 Derek Ritz derek.ritz@ecgroupinc.com wrote:
Thanks, Jennifer. Yes, I remember those calls. I also know that there is a huge overlap with the insurance registries and repositories and our existing care-focused HIE assets (please see below).
I didn’t realize our strategy was to do each one as a separate iteration. Thanks for clarifying that.
I still favour some diagrammatic approach that will illustrate the “loose-coupling” of separate domains to our HIE. I’m sorry to have missed yesterday’s call. Did that idea come up, at all? It certainly has been an aspect of discussion
during our SCM community calls.
Warmest regards,
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: Jennifer Shivers jennifer.e.shivers@gmail.com
Sent: June 11, 2019 11:17 AM
To: Derek Ritz derek.ritz@ecgroupinc.com
Cc: Daniel Futerman <daniel.futerman@jembi.org >; Ryan
Crichton ryan.crichton@jembi.org; Jack Bowie <jack.bowie@gmail.com >;
OpenHIE Architecture ohie-architecture@googlegroups.com
Subject: Re: (REVIEW & VOTE) 2019 Architecture Diagram
Derek,
We spent at least one or two calls adding the supply chain icons to the diagram. The insurance community has not yet discussed architecture diagram changes. We will add theirs when they are ready.
Jennifer
On Jun 11, 2019, at 11:08 AM, Derek Ritz derek.ritz@ecgroupinc.com wrote:
I agree that we should be clear about what the boxes/groupings represent and consistent in the labeling. I also am surprised to see logistics explicitly referenced but health financing notably missing. Regarding this point, I would very
much like to see some indication in our diagram that there are complementary domains
that are “loosely coupled” to an HIE rather than appearing to indicate that these domains are “part of” an HIE. I’m not sure how we illustrate this… but I do think it is, conceptually, a very important message for us to clearly convey.
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 ohie-architecture@googlegroups.com ** On
Behalf Of **Daniel Futerman
Sent: June 11, 2019 6:06 AM
To: Ryan Crichton ryan.crichton@jembi.org
Cc: Jack Bowie <jack.bowie@gmail.com >;
OpenHIE Architecture ohie-architecture@googlegroups.com
Subject: Re: (REVIEW & VOTE) 2019 Architecture Diagram
In previous discussions, those two boxed sections were labelled as ‘Metadata Services’ and ‘Business Domain Services’ (see here )
- I think it’s worth labelling them in the diagram for clarity.
Has there been consensus on how to scale out the Component Layer systems? It seems we’re promoting a single row, rather than stacking these vertically into several rows (presumably to avoid misperceptions of hierarchy). I don’t see an issue
with this in the current diagram, but wonder if it’s practical as new systems are added to the diagram (e.g. health financing).
There was also discussion on decoupling labels and icons, to allow for a choice on whether to use acronyms/abbreviations. We may still need a ‘default’ diagram though - my vote is for the default to avoid acronyms and spell things out (and
to be consistent e.g. the diagram uses HEALTH MGMT INFO SYSTEMat the top but then HMIS System at
the bottom).
Otherwise I think the diagram does a great job of incorporating the changes discussed in the ARB meetings - I provisionally ‘Agree’ but would like to resolve/clarify these points.
Regards,
Daniel.
Daniel Futerman** **
Technical Program Manager
Cell: +27 83 603 5424
Skype: daniel.futerman
[Jembi Health Systems | Johannesburg
- This e-mail contains proprietary and confidential information some or all of which may be legally privileged. It is for the
intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then deleting same. If you are not the intended recipient you must not use, disclose, distribute, copy, print
or rely on this e-mail. Jembi Health Systems NPO, its subsidiaries and associated companies is not liable for the security of information sent by e-mail and accepts no liability of whatsoever nature for any loss, damage or expense resulting, directly or indirectly,
from the access of this e-mail or any attachments hereto.*
On Tue, Jun 11, 2019 at 10:55 AM Ryan Crichton ryan.crichton@jembi.org wrote:
Hi,
Before I can agree or disagree, I see that the components are split up into two boxed sections. It’s not clear why this is the case. We may need some more commentary around that.
Cheers,
Ryan
On Tue, Jun 11, 2019 at 2:53 AM Jack Bowie jack.bowie@gmail.com wrote:
Looks good, but ‘ILR’ does stick out as the only primary element described with an acronym in the diagram.
Jack
On Monday, June 10, 2019 at 12:49:00 PM UTC-4, Jamie Thomas wrote:
Hi All,
As a follow up from this morning’s OHIE architecture call I’ve attached the finalized draft 2019 OHIE architecture diagram. I would ask members
of the Architecture Review Board take a look at this version and simply reply to this email as to whether they ‘Agree’ or ‘Disagree’ with
the diagram. If anyone disagrees with what they see or do not see please provide some reasoning around why.
Please provide **your response by EOD Wednesday ** at
which time I will tally responses.
Jamie Thomas |* Community
Manager*
Center for Biomedical Informatics
1101 West Tenth Street
Indianapolis, IN 46202
Tel 317-274-9218 | Fax 317-274-9305
Email: jt48@regenstrief.org |
Skype: jamie.thomas5670 | Twitter: @Regenstrief
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/8e152648-4af0-426b-bd57-221ad5300805%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
[–
You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/CABh-%2BTJ_WtLYT0kKXuQ6-Mh-XVOgb8UtLmrybXLq%3DmPTcTN6qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.](http://www.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/CAPfiHehcE1sysSNJQmgPvtr0O_gfM9N6eimSd6Mh2OHFOqPmxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.](http://www.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/8a4ccb2ade642e688d119919685f787a%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.](http://www.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/83d0b80c9fca03ac6b2db64f3cea0103%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.](http://www.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/1EA77A45-5D33-45EF-9B59-48C02EE2CB80%40gmail.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/134CE914-35BB-488C-AA09-7880992D0BB6%40path.org.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/C163C7D0-C9C4-4DD1-812A-541771E5098E%40regenstrief.org.
For more options, visit https://groups.google.com/d/optout.](http://www.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/CAKLjotnW2UbQ_yL2JTZQML3fEJUCpRuf5PGX7J%3Dn2ZSKu%3D81fQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.](http://www.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/005401d522ae%241893c910%2449bb5b30%24%40eastlink.ca.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/C9274594-AC32-411B-8129-609664C76933%40gmail.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.To
view this discussion on the web visit https://groups.google.com/d/msgid/ohie-architecture/CAGCCHRrxtU-R%2B2dcrfzsU_9fCVHfKBbMbsiO%3DoYsM7dFNBk86A%40mail.gmail.com.For
more options, visit https://groups.google.com/d/optout.