OpenHIE Provider Registry Community Call: MINUTES

Greetings All,

Please find attached the minutes from today’s Provider Registry Community Call. To recap, we were able to establish the following proposed goals for this Community which we will be exploring further during our
next call to be held on March 6th at 10:00 am:

  1. Build towards an Interlinked Registry Profile/standards development

a. Health Provider Directory (HPD) standard (already published)

b. Interlinked registry (in development through OpenHIE)

  1. Develop state-of-the-art open source provider registry that functions independently and as part of larger OpenHIE to be adapted to country specific implementations

  2. Support country customizations and implementations of Provider Registry

  3. Develop client system use cases and reference implementations

As mentioned, as a topic for our next call, we will be reviewing the HPD to ensure it meets the needs of the proposed use cases. Please see the below link to view the HPD profile:

http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_HPD.pdf

We also wanted to mention that IntraHealth is in the process of hiring a full-time Open Source Community Manager. This Community Manager will be responsible for supporting both the OpenHIE Provider Registry
Community and the growing open source community around iHRIS. Feel free to forward the below job posting to anyone you think may do a good job supporting the OpenHIE Provider Registry Community.

https://www6.ultirecruit.com/INT1028/JobBoard/JobDetails.aspx?__ID=*D62E9D723785EE24

Kind regards,

Tiffany

Tiffany Jager| Program Officer, Global Informatics

OPENHIE Provider Registry Community Call_Feb 20_MINUTES.docx (18.5 KB)

···

**IntraHealth International |**Because Health Workers Save Lives.

6340 Quadrangle Drive, Suite 200 | Chapel Hill, NC 27517

t. +1 (919) 313-9144 |
tjager@intrahealth.org

twitter |
facebook

Dear Tiffany,

Thank you for the update meeting. We are following this process closely and hope we can implement this registry in the near future.

Tunga

···

On 20/02/2013 23:47, Tiffany Jager wrote:

Greetings All,

Please find attached the minutes from today's Provider Registry Community Call. To recap, we were able to establish the following proposed goals for this Community which we will be exploring further during our next call to be held on March 6^th at 10:00 am:

1. Build towards an Interlinked Registry Profile/standards development

a.Health Provider Directory (HPD) standard (already published)

b.Interlinked registry (in development through OpenHIE)

2. Develop state-of-the-art open source provider registry that functions independently and as part of larger OpenHIE to be adapted to country specific implementations

3. Support country customizations and implementations of Provider Registry

4. Develop client system use cases and reference implementations

**

As mentioned, as a topic for our next call, we will be reviewing the HPD to ensure it meets the needs of the proposed use cases. Please see the below link to view the HPD profile:

http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_HPD.pdf

We also wanted to mention that IntraHealth is in the process of hiring a full-time Open Source Community Manager. This Community Manager will be responsible for supporting both the OpenHIE Provider Registry Community and the growing open source community around iHRIS. Feel free to forward the below job posting to anyone you think may do a good job supporting the OpenHIE Provider Registry Community.

https://www6.ultirecruit.com/INT1028/JobBoard/JobDetails.aspx?__ID=*D62E9D723785EE24

Kind regards,

Tiffany

*Tiffany Jager *| Program Officer, Global Informatics

*IntraHealth International <http://www.intrahealth.org> | *Because Health Workers Save Lives.**

6340 Quadrangle Drive, Suite 200 | Chapel Hill, NC 27517

*t.*+1 (919) 313-9144 | tjager@intrahealth.org <mailto:%20tjager@intrahealth.org>

*twitter <http://twitter.com/IntraHealth> | facebook <http://www.facebook.com/IntraHealth>*

**

**

--
You received this message because you are subscribed to the Google Groups "Provider Registry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to provider-registry+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi all,

I missed this call, but one thing I couldn’t quite understand from the minutes is how HPD’s approach was selected for the provider registry, or even if it’s a settled approach or just a proposal.

Was this discussed?

Cheers,

Chris

···

On 21 February 2013 08:33, Tungamirirai Simbini simbinit@gmail.com wrote:

Dear Tiffany,

  Thank you for the update meeting. We are following this process

closely and hope we can implement this registry in the near
future.

  Tunga




  On 20/02/2013 23:47, Tiffany Jager wrote:

Greetings All,

        Please find

attached the minutes from today’s Provider Registry
Community Call. To recap, we were able to establish the
following proposed goals for this Community which we will be
exploring further during our next call to be held on March 6th
at 10:00 am:

      1. Build towards an Interlinked Registry

Profile/standards development

a. Health
Provider Directory (HPD) standard (already published)

b. Interlinked
registry (in development through OpenHIE)

      2. Develop state-of-the-art open source

provider registry that functions independently and as part of
larger OpenHIE to be adapted to country specific
implementations

      3. Support country customizations and

implementations of Provider Registry

      4. Develop client system use cases and

reference implementations


        As mentioned,

as a topic for our next call, we will be reviewing the HPD
to ensure it meets the needs of the proposed use cases.
Please see the below link to view the HPD profile:

http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_HPD.pdf

        We also wanted

to mention that IntraHealth is in the process of hiring a
full-time Open Source Community Manager. This Community
Manager will be responsible for supporting both the OpenHIE
Provider Registry Community and the growing open source
community around iHRIS. Feel free to forward the below job
posting to anyone you think may do a good job supporting the
OpenHIE Provider Registry Community.

https://www6.ultirecruit.com/INT1028/JobBoard/JobDetails.aspx?__ID=*D62E9D723785EE24

Kind regards,

Tiffany

** Tiffany
Jager** | Program
Officer, Global Informatics

IntraHealth
International
|
Because
Health Workers Save Lives.

              6340

Quadrangle Drive, Suite 200 | Chapel Hill, NC 27517

t. +1
(919) 313-9144 |
tjager@intrahealth.org

twitter
>
facebook



  You received this message because you are subscribed to the Google

Groups “Provider Registry” group.

  To unsubscribe from this group and stop receiving emails from it,

send an email to provider-registry+unsubscribe@googlegroups.com.

  For more options, visit [https://groups.google.com/groups/opt_out](https://groups.google.com/groups/opt_out).

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

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

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

Dear Chris,

Thanks for your questions and perhaps we should have clarified this at the beginning of the call.

On our last call we discussed the HPD Profile as one possible approach to developing a provider registry. As people were not familiar with HPD, there was interest on our last call discussing what is the HPD Profile and we were presenting it here. This
was largely to build common language and give community participants enough familiarity with HPD to effectively evaluate it. Do you see any gaps?

As to why we are looking at the HPD, we have been encouraged by the larger OpenHIE community to consider the IHE profiles. That being said, nothing has been set it stone, and we are certainly very open to other directions or standards.

For our work in Rwanda specifically, we have decided to use the HPD Profile for our future work on the provider registry.

Hope that clarify matters.

Also, thanks for starting the conversation with me about linking the facility registry with the provider registry. The Facility API would be great for providing a rich data set of facilities for a provider registry, and it makes sense to me to try and
align a provider registry with a facility registry when both are being implemented in the same country. If we were to take the HPD profile forward, a suggested next step would be to map the Facility Registry API to the relevant bits of the HPD Profile –
it would be great to have your expertise here.

In the absence of a facility registry, we should also think about how to populate facilities in a provider registry. One thing mentioned was SDMX-HD for publishing the facility lists. For a concrete example from Kenya, you can take a look here:

http://bazaar.launchpad.net/~his-interop/kenya-sdmx-hd/trunk/view/head:/outputs/DSD/DSD.xml#L1224

What is nice about this is we have a standards complaint minimal amount of information encapsulated here to represent a facility in a provider registry (a code and a name).

Cheers,

-carl

···

On Mar 6, 2013, at 10:59 AM, Chris Ford christophertford@gmail.com wrote:

Hi all,

I missed this call, but one thing I couldn’t quite understand from the minutes is how HPD’s approach was selected for the provider registry, or even if it’s a settled approach or just a proposal.

Was this discussed?

Cheers,

Chris

On 21 February 2013 08:33, Tungamirirai Simbini > simbinit@gmail.com wrote:

Dear Tiffany,

Thank you for the update meeting. We are following this process closely and hope we can implement this registry in the near future.

Tunga

On 20/02/2013 23:47, Tiffany Jager wrote:

Greetings All,

Please find attached the minutes from today’s Provider Registry Community Call. To recap, we were able to establish the following proposed goals for this Community which we will be exploring further during our
next call to be held on March 6th at 10:00 am:

  1. Build towards an Interlinked Registry Profile/standards development
   a.           

Health Provider Directory (HPD) standard (already published)

  b.           

Interlinked registry (in development through OpenHIE)

  1. Develop state-of-the-art open source provider registry that functions independently and as part of larger OpenHIE to be adapted to country specific implementations
  1. Support country customizations and implementations of Provider Registry
  1. Develop client system use cases and reference implementations

As mentioned, as a topic for our next call, we will be reviewing the HPD to ensure it meets the needs of the proposed use cases. Please see the below link to view the HPD profile:

http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_HPD.pdf

We also wanted to mention that IntraHealth is in the process of hiring a full-time Open Source Community Manager. This Community Manager will be responsible for supporting both the OpenHIE Provider Registry
Community and the growing open source community around iHRIS. Feel free to forward the below job posting to anyone you think may do a good job supporting the OpenHIE Provider Registry Community.

https://www6.ultirecruit.com/INT1028/JobBoard/JobDetails.aspx?__ID=*D62E9D723785EE24

Kind regards,

Tiffany

Tiffany Jager | Program Officer, Global Informatics

**IntraHealth International |**Because Health Workers Save Lives.

6340 Quadrangle Drive, Suite 200 | Chapel Hill, NC 27517

t. +1
(919) 313-9144 | tjager@intrahealth.org

twitter |
facebook



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

To unsubscribe from this group and stop receiving emails from it, send an email to
provider-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 “Provider Registry” group.

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

provider-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 “Provider Registry” group.

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

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

Thanks for the context. :slight_smile:

···

On 6 March 2013 20:03, Carl Leitner cleitner@capacityplus.org wrote:

Dear Chris,

Thanks for your questions and perhaps we should have clarified this at the beginning of the call.

On our last call we discussed the HPD Profile as one possible approach to developing a provider registry. As people were not familiar with HPD, there was interest on our last call discussing what is the HPD Profile and we were presenting it here. This
was largely to build common language and give community participants enough familiarity with HPD to effectively evaluate it. Do you see any gaps?

As to why we are looking at the HPD, we have been encouraged by the larger OpenHIE community to consider the IHE profiles. That being said, nothing has been set it stone, and we are certainly very open to other directions or standards.

For our work in Rwanda specifically, we have decided to use the HPD Profile for our future work on the provider registry.

Hope that clarify matters.

Also, thanks for starting the conversation with me about linking the facility registry with the provider registry. The Facility API would be great for providing a rich data set of facilities for a provider registry, and it makes sense to me to try and
align a provider registry with a facility registry when both are being implemented in the same country. If we were to take the HPD profile forward, a suggested next step would be to map the Facility Registry API to the relevant bits of the HPD Profile –
it would be great to have your expertise here.

In the absence of a facility registry, we should also think about how to populate facilities in a provider registry. One thing mentioned was SDMX-HD for publishing the facility lists. For a concrete example from Kenya, you can take a look here:

http://bazaar.launchpad.net/~his-interop/kenya-sdmx-hd/trunk/view/head:/outputs/DSD/DSD.xml#L1224

What is nice about this is we have a standards complaint minimal amount of information encapsulated here to represent a facility in a provider registry (a code and a name).

Cheers,

-carl

On Mar 6, 2013, at 10:59 AM, Chris Ford christophertford@gmail.com wrote:

Hi all,

I missed this call, but one thing I couldn’t quite understand from the minutes is how HPD’s approach was selected for the provider registry, or even if it’s a settled approach or just a proposal.

Was this discussed?

Cheers,

Chris

On 21 February 2013 08:33, Tungamirirai Simbini > > simbinit@gmail.com wrote:

Dear Tiffany,

Thank you for the update meeting. We are following this process closely and hope we can implement this registry in the near future.

Tunga

On 20/02/2013 23:47, Tiffany Jager wrote:

Greetings All,

Please find attached the minutes from today’s Provider Registry Community Call. To recap, we were able to establish the following proposed goals for this Community which we will be exploring further during our
next call to be held on March 6th at 10:00 am:

  1. Build towards an Interlinked Registry Profile/standards development
   a.           

Health Provider Directory (HPD) standard (already published)

  b.           

Interlinked registry (in development through OpenHIE)

  1. Develop state-of-the-art open source provider registry that functions independently and as part of larger OpenHIE to be adapted to country specific implementations
  1. Support country customizations and implementations of Provider Registry
  1. Develop client system use cases and reference implementations

As mentioned, as a topic for our next call, we will be reviewing the HPD to ensure it meets the needs of the proposed use cases. Please see the below link to view the HPD profile:

http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_HPD.pdf

We also wanted to mention that IntraHealth is in the process of hiring a full-time Open Source Community Manager. This Community Manager will be responsible for supporting both the OpenHIE Provider Registry
Community and the growing open source community around iHRIS. Feel free to forward the below job posting to anyone you think may do a good job supporting the OpenHIE Provider Registry Community.

https://www6.ultirecruit.com/INT1028/JobBoard/JobDetails.aspx?__ID=*D62E9D723785EE24

Kind regards,

Tiffany

Tiffany Jager | Program Officer, Global Informatics

**IntraHealth International |**Because Health Workers Save Lives.

6340 Quadrangle Drive, Suite 200 | Chapel Hill, NC 27517

t. +1
(919) 313-9144 | tjager@intrahealth.org

twitter |
facebook



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

To unsubscribe from this group and stop receiving emails from it, send an email to
provider-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 “Provider Registry” group.

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

provider-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 “Provider Registry” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
provider-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 “Provider Registry” group.

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

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