SHR-Connector module

Hi team,

I am Maimoona from IHS (Interactive Health Solution), and we are working on a project eCODIRS (openmrs based) that needs to integrate with OpenHIE.
Following the ohie wiki what we have got is the process below.

We have a custom PoC and to export data to Shared Health Record we would need a module “Rhea/SHR Adapter module”. OpenMRS repository does not have this module. Could you please guide where I can find the latest module. Also we have our own custom concept dictionary and we understand that to integrate with SHR we would have to register our terms with OHIE terminology service. Demo apps currently donot have all concepts required by our application, so we may need to create those. Do we need to follow any standard medical dictionary for this?

Also from workflows it seems that we may need to verify each of our Client, HealthWorker, Facility, from central ohie installation. And before submitting post request to SHR we would perform this verification for each record.

Please guide if process above is missing any important step.

Many thanks,
Maimoona

Hi Maimoona,

The SHR adapter module was used for the Rwandan HIE which later became the basis for OpenHIE. This module can be found here: https://github.com/jembi/rhea-shr-adapter However, we are moving about from using that module as we are trying to be more standards-based. That module accepts HL7 messages but in a non-standard form. We are currently building a new set of modules that better supports the creation of a SHR using OpenMRS. These modules use the XDS.b profile defined by IHE to send clinical information is a standard based way.

These modules are not yet complete but are being built out at the moment, here they are if you would like to take a look:

https://github.com/jembi/openmrs-module-shr-xds-b-repository

https://github.com/jembi/openmrs-module-shr-cdahandler

https://github.com/jembi/openmrs-module-shr-contenthandler

For additional medical concepts you will need to add these to the Terminology service. It may be best to ask about this on the terminology service mailing list if you would like more details. (https://groups.google.com/forum/?hl=en&fromgroups#!forum/terminology-services)

Hope this helps,

Ryan

···

On Mon, Sep 15, 2014 at 9:21 AM, maimoona.kausar@ihsinformatics.com wrote:

Hi team,

I am Maimoona from IHS (Interactive Health Solution), and we are working on a project eCODIRS (openmrs based) that needs to integrate with OpenHIE.
Following the ohie wiki what we have got is the process below.

We have a custom PoC and to export data to Shared Health Record we would need a module “Rhea/SHR Adapter module”. OpenMRS repository does not have this module. Could you please guide where I can find the latest module. Also we have our own custom concept dictionary and we understand that to integrate with SHR we would have to register our terms with OHIE terminology service. Demo apps currently donot have all concepts required by our application, so we may need to create those. Do we need to follow any standard medical dictionary for this?

Also from workflows it seems that we may need to verify each of our Client, HealthWorker, Facility, from central ohie installation. And before submitting post request to SHR we would perform this verification for each record.

Please guide if process above is missing any important step.

Many thanks,
Maimoona

You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr+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 Ryan, it was really helpful.

Trying exploring repository and documentation, it appears that rhea-poc-adapter-module (https://github.com/jembi/rhea-poc-adapter) is the one that we need. We want to use ohie existing software as it is, only thing is we have our custom POC (openmrs based) client and to send data to SHR we need adapter module that should send data to SHR. Having a look on the code it appears that it was built specifically for Rawanda, but we can use it for our client after making changes.

For testing purposes we would be using ohie public demo installation (http://demo.ohie.org/), is it the latest one?

Is our approach to use poc-adapter module correct or we should use any other module?

Could you please refer ohie wiki part that I should read as an implementer and software developer to make our client application integrate with existing ohie software.

Many thanks,
Maimoona

···

On Monday, September 15, 2014 2:02:20 PM UTC+5, Ryan Crichton wrote:

Hi Maimoona,

The SHR adapter module was used for the Rwandan HIE which later became the basis for OpenHIE. This module can be found here: https://github.com/jembi/rhea-shr-adapter However, we are moving about from using that module as we are trying to be more standards-based. That module accepts HL7 messages but in a non-standard form. We are currently building a new set of modules that better supports the creation of a SHR using OpenMRS. These modules use the XDS.b profile defined by IHE to send clinical information is a standard based way.

These modules are not yet complete but are being built out at the moment, here they are if you would like to take a look:

https://github.com/jembi/openmrs-module-shr-xds-b-repository

https://github.com/jembi/openmrs-module-shr-cdahandler

https://github.com/jembi/openmrs-module-shr-contenthandler

For additional medical concepts you will need to add these to the Terminology service. It may be best to ask about this on the terminology service mailing list if you would like more details. (https://groups.google.com/forum/?hl=en&fromgroups#!forum/terminology-services)

Hope this helps,

Ryan

On Mon, Sep 15, 2014 at 9:21 AM, maimoon...@ihsinformatics.com wrote:

Hi team,

I am Maimoona from IHS (Interactive Health Solution), and we are working on a project eCODIRS (openmrs based) that needs to integrate with OpenHIE.
Following the ohie wiki what we have got is the process below.

We have a custom PoC and to export data to Shared Health Record we would need a module “Rhea/SHR Adapter module”. OpenMRS repository does not have this module. Could you please guide where I can find the latest module. Also we have our own custom concept dictionary and we understand that to integrate with SHR we would have to register our terms with OHIE terminology service. Demo apps currently donot have all concepts required by our application, so we may need to create those. Do we need to follow any standard medical dictionary for this?

Also from workflows it seems that we may need to verify each of our Client, HealthWorker, Facility, from central ohie installation. And before submitting post request to SHR we would perform this verification for each record.

Please guide if process above is missing any important step.

Many thanks,
Maimoona

You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr...@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: ry...@jembi.org

Hi Maimoona,

You are on the right track. That module is specific to Rwanda but you could make changes to make it work for your use case.

The OpenHIE demo site is using the old way that we used for Rwanda at the moment, however, it will be changing to the newer module in the near future.

If you are just getting started I’d suggest exploring the newer way using the XDS.b profile and see if that would work for you as that is the way we are going to be moving. Here is how we are thinking about a SHR at the moment: https://wiki.ohie.org/pages/viewpage.action?pageId=19464697

Also you may want to browse the workflows we expect to support with the SHR:

Ryan

···

On Thu, Sep 18, 2014 at 6:37 AM, maimoona.kausar@ihsinformatics.com wrote:

Thanks Ryan, it was really helpful.

Trying exploring repository and documentation, it appears that rhea-poc-adapter-module (https://github.com/jembi/rhea-poc-adapter) is the one that we need. We want to use ohie existing software as it is, only thing is we have our custom POC (openmrs based) client and to send data to SHR we need adapter module that should send data to SHR. Having a look on the code it appears that it was built specifically for Rawanda, but we can use it for our client after making changes.

For testing purposes we would be using ohie public demo installation (http://demo.ohie.org/), is it the latest one?

Is our approach to use poc-adapter module correct or we should use any other module?

Could you please refer ohie wiki part that I should read as an implementer and software developer to make our client application integrate with existing ohie software.

Many thanks,
Maimoona

On Monday, September 15, 2014 2:02:20 PM UTC+5, Ryan Crichton wrote:

Hi Maimoona,

The SHR adapter module was used for the Rwandan HIE which later became the basis for OpenHIE. This module can be found here: https://github.com/jembi/rhea-shr-adapter However, we are moving about from using that module as we are trying to be more standards-based. That module accepts HL7 messages but in a non-standard form. We are currently building a new set of modules that better supports the creation of a SHR using OpenMRS. These modules use the XDS.b profile defined by IHE to send clinical information is a standard based way.

These modules are not yet complete but are being built out at the moment, here they are if you would like to take a look:

https://github.com/jembi/openmrs-module-shr-xds-b-repository

https://github.com/jembi/openmrs-module-shr-cdahandler

https://github.com/jembi/openmrs-module-shr-contenthandler

For additional medical concepts you will need to add these to the Terminology service. It may be best to ask about this on the terminology service mailing list if you would like more details. (https://groups.google.com/forum/?hl=en&fromgroups#!forum/terminology-services)

Hope this helps,

Ryan

On Mon, Sep 15, 2014 at 9:21 AM, maimoon...@ihsinformatics.com wrote:

Hi team,

I am Maimoona from IHS (Interactive Health Solution), and we are working on a project eCODIRS (openmrs based) that needs to integrate with OpenHIE.
Following the ohie wiki what we have got is the process below.

We have a custom PoC and to export data to Shared Health Record we would need a module “Rhea/SHR Adapter module”. OpenMRS repository does not have this module. Could you please guide where I can find the latest module. Also we have our own custom concept dictionary and we understand that to integrate with SHR we would have to register our terms with OHIE terminology service. Demo apps currently donot have all concepts required by our application, so we may need to create those. Do we need to follow any standard medical dictionary for this?

Also from workflows it seems that we may need to verify each of our Client, HealthWorker, Facility, from central ohie installation. And before submitting post request to SHR we would perform this verification for each record.

Please guide if process above is missing any important step.

Many thanks,
Maimoona

You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr...@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: ry...@jembi.org

You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr+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