OpenMRS as Shared Health Record using SHR Adapter Module

[May Buenavides]

Hi!

We would like to try implementing OpenMRS as Shared Health Record just like what they did in Rwanda. 

Based on the installation guide, an omod file of the said Adapter Module has has to be imported to the OpenMRS.

However, I cannot seem to find/download an omod file of the adapter module; though, I was able to get a copy of the source code but for some reason, I cannot build it successfully.

 

Can you guys help us out on this? :)

Thanks!

----------------------------------------------------

May Buenavides

Department of Science and Technology

Advance Science and Technology Institute

Philippines

[Ryan Crichton]

Hi May,

The current SHR adapter module that is used for the Rwandan HIE may be quite specific to the Rwandan use case. So you may have to modify it for your needs. This community is now looking a re-designing this module to be more generally applicable and to make use of IHE standard profile as the interface into the SHR. You can find out more about what we are planning to develop here: https://wiki.ohie.org/display/SUB/Shared+Health+Record+Community+Documentation. In particular this design may be interesting to you: https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document. Note, we are just starting development of these components now and this design is still changing quite a bit.

That being said, I have some experience with that module so I can try help you to get it built. Could you send the full text output from your screenshot? Some text is cut off so I can't see what the problem could be. You could try building it again as that may have just been some sort of connectivity issue.

Cheers,

Ryan

--
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/groups/opt_out.

--

Ryan Crichton

Software Developer, Jembi Health Systems |  SOUTH AFRICA

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

[Pascal Brandt]

Hi May,

What are you seeing when you try to build the module? Running the following two commands:

git clone https://github.com/jembi/rhea-shr-adapter.git
cd rhea-shr-adapter/ && mvn clean install

results in a successful build for me:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] RHEA SHR Adapter Web Service ...................... SUCCESS [1.838s]
[INFO] RHEA SHR Adapter Web Services API ................. SUCCESS [7.339s]
[INFO] RHEA SHR Adapter Web Service OMOD ................. SUCCESS [14.785s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

I've attached the OMOD that is produced.

Cheers,

Pascal

--

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/groups/opt_out.

--
Pascal Brandt
Senior Software Developer, Jembi Health Systems |  SOUTH AFRICA
Mobile: +27 84 827 9342 | Office: +27 21 701 0939 | Skype: psbrandt
E-mail: pas...@jembi.org

[Pascal Brandt]

Hi Elmer,

No problem at all. Ryan and I both suspect that the build failure is being caused by connectivity issues (problems downloading artifacts from the maven repositories).

Please also make sure to take note of Ryan's response - the current SHR module has been developed for a specific use case.

Cheers,

Pascal

On 23 October 2013 15:52, Elmer Peramo <elmer...@gmail.com> wrote:

Hello Pascal,

May is out of the office right now, but she will get back to you as soon as she arrive to work tomorrow morning. (It's nighttime here in the Philippines.) We do appreciate your help so much, as we are just trying to beat a deadline in our implementation. Thank you for the attachment. I hope we make it work.

Best regards,
Elmer

[Tucker, Mark]

Hi May (et al)

 

We are doing some work at Regenstrief to beef up the HL7 processing used by OpenMRS.

Suranga (who wrote some/all???) of the Rwandan adaptor, is changing it to add better document handling, etc, as sketched out in the OpenMRS as a SHR design document.

 

We are also going to see if the very sophisticated HL7 processing we do for the Regenstrief EMR (RAMRS), can be adapted to be used in OpenMRS.

 

In any event, we would welcome your participation in the SHR calls.

 

 

Mark

 

 

From: openh...@googlegroups.com [mailto:openh...@googlegroups.com] On Behalf Of Ryan Crichton
Sent: Wednesday, October 23, 2013 6:02 AM
To: May Buenavides
Cc: openh...@googlegroups.com; Jep ASTI; Elmer Peramo; Milo Gillesania
Subject: Re: OpenMRS as Shared Health Record using SHR Adapter Module

 

Hi May,

 

The current SHR adapter module that is used for the Rwandan HIE may be quite specific to the Rwandan use case. So you may have to modify it for your needs. This community is now looking a re-designing this module to be more generally applicable and to make use of IHE standard profile as the interface into the SHR. You can find out more about what we are planning to develop here: https://wiki.ohie.org/display/SUB/Shared+Health+Record+Community+Documentation. In particular this design may be interesting to you: https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document. Note, we are just starting development of these components now and this design is still changing quite a bit.

 

That being said, I have some experience with that module so I can try help you to get it built. Could you send the full text output from your screenshot? Some text is cut off so I can't see what the problem could be. You could try building it again as that may have just been some sort of connectivity issue.

 

Cheers,

Ryan

On Wed, Oct 23, 2013 at 11:44 AM, May Buenavides <emeyw...@gmail.com> wrote:

Hi!

 

We would like to try implementing OpenMRS as Shared Health Record just like what they did in Rwanda. 

 

Based on the installation guide, an omod file of the said Adapter Module has has to be imported to the OpenMRS.

 

However, I cannot seem to find/download an omod file of the adapter module; though, I was able to get a copy of the source code but for some reason, I cannot build it successfully.

 

 

 

 

 

 

Can you guys help us out on this? :)

 

Thanks!

 

 

----------------------------------------------------

May Buenavides

Department of Science and Technology

Advance Science and Technology Institute

Philippines

--
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/groups/opt_out.

 

--

Ryan Crichton

Software Developer, Jembi Health Systems |  SOUTH AFRICA

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

[May Buenavides]

Hi,

We are trying to make the OpenMRS work as SHR on minimal/general use cases, so for now I think there is no problem with the adapter being designed specifically for Rwanda.

Yes, I think there is a connectivity issue, perhaps our proxy here in the office is preventing the project from downloading the necessary dependencies.

Anyway, I was able to import the omod file Pascal Brandt sent (thanks!). 

After that, the installation guide says that I need to configure the SHR module...

Configuring the SHR module

After installing the module, you need to assign a value to the 'Sending Facility' global property which it adds to the global properties page. This property does not have a default value, so its importaint to set it immidiately after you install it. 

where will I change the value of the said global property? is it somewhere here?

Also, I tried this GET request /openmrs/ws/rest/RHEA/patient/encounters?patientId=1234&idType=ECID (Note: our sample data came from here. ) but I'm getting this error:

Thanks in advance! :)

[Suranga Kasthurirathne]

Hi May,

I am the culprit responsible for many of your woes :-)

In this case, the 'Sending Facility' can be set to some default text string for test purposes. You can find it in the OpenMRS global properties page.

Hmm.... I cant really see the error message you received when making that request. Are you sure you included it in the email ? and does the system already contain a patient with that identifier type and id value ?

--

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/groups/opt_out.

--
Best Regards,

Suranga

[May Buenavides]

Hi Suranga,

Is the "Sending Facility" property necessary for the adapter to work properly? :)

Regarding the error, yes, our database contains that patient. So this request /openmrs/ws/rest/RHEA/patient/encounters?patientId=1234&idType=ECID should return something because it is in the database as shown here:

 I just can't seem to verify if this part of request is correct /openmrs/ws/rest/RHEA/patient/encounters?patientId=1234&idType=ECID. On what table can I verify the idType property? it is not in the person or patient table.

Thanks!

[May Buenavides]

Guys! :)

What are the URI Conventions for invoking OpenMRS as SHR REST web services ?

Does that make sense? :P   I'm looking for something like this:

• GET /ws/rest/resource?q=query = search
• GET /ws/rest/resource/uuid = retrieve
• POST /ws/rest/resource = create
• • Request body contains data to persist (not in request params)
• POST /ws/rest/resource/uuid = partial update of the resource
• • Request body contains just the fields to update (not in request params)
• PUT = replace value of entire object (we don't use this yet)
• DELETE /ws/rest/resource/uuid = void for data, retire for metadata
• DELETE /ws/rest/resource/uuid?purge=true = purge (aka delete from the database entirely)

... I got that from here.

So far I still can't get a successful response when I try to make this request: /openmrs/ws/rest/RHEA/patient/encounters?patientId=1234&idType=ECID

Currently, I'm using OpenMRS 1.9, demo data from here, modules Rest Web Services 2.2.ea6287 & RHEA SHR Web Service 1.0.

Could there be a conflict in the versions of the modules I'm using? 

Sorry for all the questions...

Help would be much appreciated :)

Thanks in advance!

[Pascal Brandt]

Hi,

Disclaimer: I've never used this module.

Perhaps some the following resources could be useful:

• https://jembiprojects.jira.com/wiki/display/RHEAPILOT/RHEA+SHR+Adapter+module+Installation+guide
  
• https://jembiprojects.jira.com/wiki/display/RHEAPILOT/RHEA+Training+manual+for+the+SHR+Adapter+Module and child pages such as this one.
  

Hope this helps.

Ciao,

Pascal

--
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/groups/opt_out.

--

[Kari Schoonbee]

Here is another resource that shows how the REST service is supposed to work.

https://jembiprojects.jira.com/wiki/display/RHEAPILOT/Query+for+previous+patient+encounters+-+Internal

Do you have a Patient Identifier Type Called "ECID" set up and made sure that there is a patient that has an identifier of that type with value "1234"? The patient_id row in the DB is only the primary key in the table and has nothing to do with the Patient Identifier you're querying for.

Kind regards

Kari

[Suranga Kasthurirathne]

Hi, 

I would concur with what Kari says above. So you need to be looking in your Patient_identifier table instead.

And also, do you get any kind of error message on your tomcat log, or whatever tool you're using to make restful calls ?

Best Regards,

Suranga

[May Buenavides]

Hi!

Thanks for all your inputs.

It appears that I do not have an ECID Patient Identifier Type, so I added one.

Now I have patientId=1234 with an identifier_type=3 which points to the identifier type ECID (see image below)

With that, I still get an error when I execute this request: /openmrs/ws/rest/RHEA/patient/encounters?patientId=1234&idType=ECID

This error is not listed in here: https://jembiprojects.jira.com/wiki/display/RHEAPILOT/Query+for+previous+patient+encounters+-+Internal so I'm a bit clueless as to what causes it because as far as our data is concerned, we only have one patient with id=1234.

Thanks!

[Hannes Venter]

Hi May,

Your almost there. You need to pass to value for the patient's ECID identifier in the URL instead of the internal patient id:

/openmrs/ws/rest/RHEA/patient/encounters?patientId=1233TS-3&idType=ECID

The patient id 1234 is basically only used internally in OpenMRS, so it will never get referenced externally.

This is where the ECID comes in; it's a universal identifier that can be used throughout the health information exchange.

Kind Regards

Hannes

--
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/groups/opt_out.

--
Hannes Venter

Software Developer, Jembi Health Systems |  SOUTH AFRICA

Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: han...@jembi.org

[May Buenavides]

wooooow! Thanks so much for all your help, I am now getting a successful response when invoking this request: /openmrs/ws/rest/RHEA/patient/encounters?patientId=1233TS-3&idType=ECID

Indeed, patient identifier should be used instead of the patient ID .

[Suranga Kasthurirathne]

Hi,

Great to hear that it worked out.

Please feel free to test it out, ask questions or "throw stones" at our design. We'd love to hear your input :-)

--

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/groups/opt_out.

--
Best Regards,

Suranga

[Jeff Xiong]

Nice to see another project besides Rwanda is using this approach.

I'm curious how you feel about the performance of OpenMRS - essentially, using relational database on a scale of a country. Anyone got any responding time or throughput challenge so far?

在 2013年10月23日星期三UTC+5:30下午3时14分48秒，May Buenavides写道：

[Ryan Crichton]

Hi Jeff,

We have performed an analysis of OpenMRS for us as an SHR. It is a worry to us but we have some ideas around database clustering and database optimization that we would like to try.

You can find the performance report here: https://wiki.ohie.org/display/SUB/Performance+evaluation+of+OpenMRS

Cheers,

Ryan

--

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/groups/opt_out.

--

Ryan Crichton

Software Developer, Jembi Health Systems |  SOUTH AFRICA

[May Buenavides]

Hi!

Thanks for all your inputs!

Anyway, we are still on the early stages of development of our OpenHIE.

Will keep you guys posted :)

​----------------------------------------------------

May F Buenavides

Department of Science and Technology

​

​

​

Ad

​​

vanced Science and Technology Institute

​

Philippines

--
You received this message because you are subscribed to a topic in the Google Groups "Shared Health Record (OpenHIE)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhie-shr/ZdOGVkdQvbk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhie-shr...@googlegroups.com.

[Paul John Serrano]

Hi Guys,

I'm Pol and I'm also from the Philippines working with May.

I would just like to ask the method or API call in obtaining a session using a REST API client.

I'm currently trying to call OpenMRS-SHR API via a REST API client but it seems that I can't find any reference to obtain a session.

I can successfully do it via curl with this command:

curl -i -u admin:test "http://202.90.xxx.xxx:8080/openmrs/ws/rest/RHEA/patient/encounters?idType=ECID&patientId=2370AM-5"

Is there an initial API call to obtain a session from the OpenMRS-SHR?

Your help is very much appreciated!

Thanks,

Pol

[Hannes Venter]

Hi Pol,

All you have to do to authenticate requests to the SHR is provide http basic auth details.

There's no need to create a session using an API call.

It should be possible with your REST client to set the Authentication header in the request.

The value of this should be Basic authdetails where authdetails is the base64 encoded value of user:password.

For example, in your case (admin:test) the Authentication header should read: Basic YWRtaW46dGVzdA==

Your client may also have useful methods for simply setting the username and password for auth, but you'd have to see if there's something like that available.

Hope this helps!

Hannes

Hannes Venter

Software Developer, Jembi Health Systems |  SOUTH AFRICA

[Paul John Serrano]

Hi Hannes,

Thanks a lot for this! It worked! :)

-Pol

--

Paul John M. Serrano