CSD Workflow Diagram

Hi All
As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:
    https://wiki.ohie.org/display/documents/CSD+Query+for+services
related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,
-carl

Hey Carl,

I don’t have any comments, this matches up with my expectations. A minor point: perhaps it would be useful to fill out the endpoint column with with something like “http:////careServicesRequest” or similar for the other transactions. Just for added information?

Cheers,

Ryan

···

On Mon, Feb 17, 2014 at 10:19 PM, Carl Leitner litlfred@gmail.com wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

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

Hi Carl,

Thanks for sending this around. Are our communities co-owners of this workflow? CC’ed martin here to comment when he has a second as well, I know he may have some recommendations.

Best,

Scott

···

On Monday, February 17, 2014 3:19:08 PM UTC-5, Carl Leitner wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

It would be great if you were :slight_smile:
Cheers,
-carl

···

On Feb 20, 2014, at 12:37 PM, Scott Teesdale steesdale@instedd.org wrote:

Hi Carl,

Thanks for sending this around. Are our communities co-owners of this workflow? CC’ed martin here to comment when he has a second as well, I know he may have some recommendations.

Best,

Scott

On Monday, February 17, 2014 3:19:08 PM UTC-5, Carl Leitner wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

Hi Carl,

Great, sounds good to me too. Let me coordinate between the community on who should be the POC / co-sponsor, but I think it makes sense for both communities to help advise the workflow. We have some other related discussion we should continue too, regarding potentially joining IHE to vote and also how we want to continue the change request process as well. Perhaps, in a couple weeks we could plan to sync on how we all want to move forward in terms of process and strategy on this.

Best,

Scott

···

On Thu, Feb 20, 2014 at 12:38 PM, Carl Leitner litlfred@gmail.com wrote:

It would be great if you were :slight_smile:
Cheers,
-carl

On Feb 20, 2014, at 12:37 PM, Scott Teesdale steesdale@instedd.org wrote:

Hi Carl,

Thanks for sending this around. Are our communities co-owners of this workflow? CC’ed martin here to comment when he has a second as well, I know he may have some recommendations.

Best,

Scott

On Monday, February 17, 2014 3:19:08 PM UTC-5, Carl Leitner wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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


Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

Will do (unless someone from the FR community gets to it first).
Cheers,

-carl

···

On Mon, Feb 17, 2014 at 10:19 PM, Carl Leitner
litlfred@gmail.com wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[

https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH
AFRICA

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

E-mail: ryan@jembi.org

Great start to this process. The CSD workflow is an excellent example of a workflow requiring coordination among multiple components, and so the communities for each of these components will likely provide input into that process.

It seems to me that either designating a single sponsor, or perhaps a co-sponsor from key component communities will likely be the most effective path forward.

Shaun

···

Shaun J. Grannis, MD MS FACMI FAAFP
Biomedical Research Scientist, The Regenstrief Institute
Associate Professor, I.U. School of Medicine

410 West 10th Street, Suite 2000
Indianapolis, IN 46202
(317) 274-9092 (Office)
(317) 274-9305 (Fax)

On Fri, Feb 21, 2014 at 11:10 AM, Carl Leitner cleitner@capacityplus.org wrote:

Will do (unless someone from the FR community gets to it first).
Cheers,

-carl

On Feb 19, 2014, at 1:47 AM, Ryan Crichton ryan@jembi.org wrote:

Hey Carl,

I don’t have any comments, this matches up with my expectations. A minor point: perhaps it would be useful to fill out the endpoint column with with something like “http:////careServicesRequest” or similar for the other transactions. Just
for added information?

Cheers,

Ryan

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

On Mon, Feb 17, 2014 at 10:19 PM, Carl Leitner
litlfred@gmail.com wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[

https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH
AFRICA

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

E-mail: ryan@jembi.org

Hi Carl, thanks for sharing! Just a couple of doubts:

  1. Step 2:

Validation is defined according to country specific
data governance policies in accessing the InfoMan

So this step answers the question: is this PoS allowed to execute the query identified by the given UUID?

Am I getting it right?

  1. Given it’s a query for services, I expected to see a catalog of services being pulled from somewhere (maybe the TS or the FR?). From this workflow I understand the InfoMan knows of such a catalog (how it does so is opaque) and it takes care of joining providers and facilities as expected.

I guess it’s not strictly necessary to get a services catalog to do this since you can assume your catalog is implicitly defined by whatever service happens to be referenced by either registry, but it still seems strange not to mention where’s the master source of services.

Cheers,

Martin

···

On Thu, Feb 20, 2014 at 2:52 PM, Scott Teesdale steesdale@instedd.org wrote:

Hi Carl,

Great, sounds good to me too. Let me coordinate between the community on who should be the POC / co-sponsor, but I think it makes sense for both communities to help advise the workflow. We have some other related discussion we should continue too, regarding potentially joining IHE to vote and also how we want to continue the change request process as well. Perhaps, in a couple weeks we could plan to sync on how we all want to move forward in terms of process and strategy on this.

Best,

Scott


Martín Verzilli
Manas Technology Solutions
[ar.phone] 5258.5240 #MVR(687)
[us.phone] 312.612.1050 #MVR(687)
[email] mverzilli@manas.com.ar

[web] www.manas.com.ar
[blog] weblogs.manas.com.ar/mverzilli

On Thu, Feb 20, 2014 at 12:38 PM, Carl Leitner litlfred@gmail.com wrote:

It would be great if you were :slight_smile:
Cheers,
-carl

On Feb 20, 2014, at 12:37 PM, Scott Teesdale steesdale@instedd.org wrote:

Hi Carl,

Thanks for sending this around. Are our communities co-owners of this workflow? CC’ed martin here to comment when he has a second as well, I know he may have some recommendations.

Best,

Scott

On Monday, February 17, 2014 3:19:08 PM UTC-5, Carl Leitner wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

Hi Martin.

I suspect your question #2 may reflect a bit of confusion caused by the naming of the IHE interaction ITI-73 “Find Matching Services”. ITI-73 is used to query for organizations, providers, facilities and services – or content that cross-references across all 4 of these. The IHE naming is ambiguous in that “services” is meant to refer to all 4 axes, not just the last one.

Yes – the InfoMan’s job is to cross reference the org | provider | facility | service information. However, to be a CSD-compliant Care Services Directory actor, there is also an onus on each of the individual registries to use the cardinal lists of codes mandated by an implementing jurisdiction so that this cross-referencing is possible. In fact, a Directory actor would be well-served by supporting ITI-73 so that it could also be a Service Finder; this would enable it to query an InfoMan for “legal” facility ID, provider ID, service ID or org ID codes. :wink:

Warmest regards,

Derek.

···

On Mon, Feb 24, 2014 at 4:12 PM, Martin Verzilli mverzilli@manas.com.ar wrote:

Hi Carl, thanks for sharing! Just a couple of doubts:

  1. Step 2:

Validation is defined according to country specific
data governance policies in accessing the InfoMan

So this step answers the question: is this PoS allowed to execute the query identified by the given UUID?

Am I getting it right?

  1. Given it’s a query for services, I expected to see a catalog of services being pulled from somewhere (maybe the TS or the FR?). From this workflow I understand the InfoMan knows of such a catalog (how it does so is opaque) and it takes care of joining providers and facilities as expected.

I guess it’s not strictly necessary to get a services catalog to do this since you can assume your catalog is implicitly defined by whatever service happens to be referenced by either registry, but it still seems strange not to mention where’s the master source of services.

Cheers,

Martin

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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


Derek Ritz

This email may contain confidential information intended only for the recipient. If you receive it by accident, please delete it.

On Thu, Feb 20, 2014 at 2:52 PM, Scott Teesdale steesdale@instedd.org wrote:

Hi Carl,

Great, sounds good to me too. Let me coordinate between the community on who should be the POC / co-sponsor, but I think it makes sense for both communities to help advise the workflow. We have some other related discussion we should continue too, regarding potentially joining IHE to vote and also how we want to continue the change request process as well. Perhaps, in a couple weeks we could plan to sync on how we all want to move forward in terms of process and strategy on this.

Best,

Scott

Martín Verzilli
Manas Technology Solutions
[ar.phone] 5258.5240 #MVR(687)
[us.phone] 312.612.1050 #MVR(687)

[email] mverzilli@manas.com.ar

[web] www.manas.com.ar
[blog] weblogs.manas.com.ar/mverzilli

On Thu, Feb 20, 2014 at 12:38 PM, Carl Leitner litlfred@gmail.com wrote:

It would be great if you were :slight_smile:
Cheers,
-carl

On Feb 20, 2014, at 12:37 PM, Scott Teesdale steesdale@instedd.org wrote:

Hi Carl,

Thanks for sending this around. Are our communities co-owners of this workflow? CC’ed martin here to comment when he has a second as well, I know he may have some recommendations.

Best,

Scott

On Monday, February 17, 2014 3:19:08 PM UTC-5, Carl Leitner wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

<<Sorry… dunno how, but I think I inadvertently cross-posted my reply.>>

Hi Martin.

I suspect your question #2 may reflect a bit
of confusion caused by the naming of the IHE interaction ITI-73 “Find Matching Services”. ITI-73 is used to query for organizations, providers, facilities and services – or content that cross-references across all 4 of these. The IHE naming is ambiguous in that “services” is
meant to refer to all 4 axes, not just the last one.

Yes – the InfoMan’s job is to cross reference the org | provider | facility | service information. However, to be a CSD-compliant Care Services Directory actor, there is also an onus on each of the individual registries to use the cardinal lists of codes mandated by an implementing jurisdiction so that this cross-referencing is possible. In
fact, a Directory actor would be well-served by supporting ITI-73 so that it could also be a Service Finder; this would enable it to query an
InfoMan for “legal” facility ID, provider ID, service ID or org ID codes. :wink:

Warmest regards,

Derek.

···

On Monday, February 24, 2014 4:12:14 PM UTC-5, Martin Verzilli wrote:

Hi Carl, thanks for sharing! Just a couple of doubts:

  1. Step 2:

Validation is defined according to country specific
data governance policies in accessing the InfoMan

So this step answers the question: is this PoS allowed to execute the query identified by the given UUID?

Am I getting it right?

  1. Given it’s a query for services, I expected to see a catalog of services being pulled from somewhere (maybe the TS or the FR?). From this workflow I understand the InfoMan knows of such a catalog (how it does so is opaque) and it takes care of joining providers and facilities as expected.

I guess it’s not strictly necessary to get a services catalog to do this since you can assume your catalog is implicitly defined by whatever service happens to be referenced by either registry, but it still seems strange not to mention where’s the master source of services.

Cheers,

Martin

On Thu, Feb 20, 2014 at 2:52 PM, Scott Teesdale stee...@instedd.org wrote:

Hi Carl,

Great, sounds good to me too. Let me coordinate between the community on who should be the POC / co-sponsor, but I think it makes sense for both communities to help advise the workflow. We have some other related discussion we should continue too, regarding potentially joining IHE to vote and also how we want to continue the change request process as well. Perhaps, in a couple weeks we could plan to sync on how we all want to move forward in terms of process and strategy on this.

Best,

Scott

On Thu, Feb 20, 2014 at 12:38 PM, Carl Leitner litl...@gmail.com wrote:

It would be great if you were :slight_smile:
Cheers,
-carl

On Feb 20, 2014, at 12:37 PM, Scott Teesdale stee...@instedd.org wrote:

Hi Carl,

Thanks for sending this around. Are our communities co-owners of this workflow? CC’ed martin here to comment when he has a second as well, I know he may have some recommendations.

Best,

Scott

On Monday, February 17, 2014 3:19:08 PM UTC-5, Carl Leitner wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

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

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

Scott Teesdale
Project Manager - InSTEDD

Email: stee...@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn


Martín Verzilli
Manas Technology Solutions
[ar.phone] 5258.5240 #MVR(687)
[us.phone] 312.612.1050 #MVR(687)
[email] mver…@manas.com.ar

[web] www.manas.com.ar
[blog] weblogs.manas.com.ar/mverzilli

Just to follow-up, these codes were what was provided, in the case of the connect-a-thon, by the SVS files that Lynn sent us.
Cheers,

-carl

···

On Feb 25, 2014, at 1:10 PM, Derek Ritz derek.ritz@gmail.com wrote:

<<Sorry… dunno how, but I think I inadvertently cross-posted my reply.>>

Hi Martin.

I suspect your question #2 may reflect a bit of confusion caused by the naming of the IHE interaction ITI-73 “Find Matching Services”. ITI-73 is used to query for organizations, providers, facilities and services – or content that cross-references across
all 4 of these. The IHE naming is ambiguous in that “services” is meant to refer to all 4 axes, not just the last one.

Yes – the InfoMan’s job is to cross reference the org | provider | facility | service information. However, to be a CSD-compliant Care Services Directory actor, there is also an onus on each of the individual registries to use the cardinal lists of codes mandated
by an implementing jurisdiction so that this cross-referencing is possible. In fact, a Directory actor would be well-served by supporting ITI-73 so that it could also be a Service Finder; this would enable it to query an InfoMan for “legal” facility ID, provider
ID, service ID or org ID codes. :wink:

Warmest regards,

Derek.

On Monday, February 24, 2014 4:12:14 PM UTC-5, Martin Verzilli wrote:

Hi Carl, thanks for sharing! Just a couple of doubts:

  1. Step 2:

Validation is defined according to country specific

data governance policies in accessing the InfoMan

So this step answers the question: is this PoS allowed to execute the query identified by the given UUID?

Am I getting it right?

  1. Given it’s a query for services, I expected to see a catalog of services being pulled from somewhere (maybe the TS or the FR?). From this workflow I understand the InfoMan knows of such a catalog (how it does so is opaque) and it takes care of joining
    providers and facilities as expected.

I guess it’s not strictly necessary to get a services catalog to do this since you can assume your catalog is implicitly defined by whatever service happens to be referenced by either registry, but it still seems strange not to mention where’s the master
source of services.

Cheers,

Martin

On Thu, Feb 20, 2014 at 2:52 PM, Scott Teesdale > > stee...@instedd.org wrote:

Hi Carl,

Great, sounds good to me too. Let me coordinate between the community on who should be the POC / co-sponsor, but I think it makes sense for both communities to help advise the workflow. We have some other related discussion we should continue too, regarding
potentially joining IHE to vote and also how we want to continue the change request process as well. Perhaps, in a couple weeks we could plan to sync on how we all want to move forward in terms of process and strategy on this.

Best,

Scott

On Thu, Feb 20, 2014 at 12:38 PM, Carl Leitner > > > litl...@gmail.com wrote:

It would be great if you were :slight_smile:
Cheers,

-carl

On Feb 20, 2014, at 12:37 PM, Scott Teesdale stee...@instedd.org wrote:

Hi Carl,

Thanks for sending this around. Are our communities co-owners of this workflow? CC’ed martin here to comment when he has a second as well, I know he may have some recommendations.

Best,

Scott

On Monday, February 17, 2014 3:19:08 PM UTC-5, Carl Leitner wrote:

Hi All

As part of the OpenHIE work, we have been asked to start documenting some of the workflows related to the Health Worker/Provider Registry. Here is a draft workflow diagram for you all to look at:

[

https://wiki.ohie.org/display/documents/CSD+Query+for+services](https://wiki.ohie.org/display/documents/CSD+Query+for+services)

related to the CSD query for services.

I would appreciate any feedback that you have on this to make sure everything is accurate and clear.

Thanks so much!

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to

facility-regis...@googlegroups.com.

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

You received this message because you are subscribed to the Google Groups “Facility Registry (OHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to

facility-regis...@googlegroups.com.

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

Scott Teesdale
Project Manager -
InSTEDD

Email:
stee...@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

Martín Verzilli

Manas Technology Solutions

[ar.phone] 5258.5240 #MVR(687)

[us.phone] 312.612.1050 #MVR(687)

[email]
mver…@manas.com.ar

[web]
www.manas.com.ar

[blog]
weblogs.manas.com.ar/mverzilli

You received this message because you are subscribed to the Google Groups “Interoperability Layer (OpenHIE)” group.

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

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