Shared Health Record Tool Recommendation

Legacy openhie-shr
1

Hi Everyone,

We’re nearing the end of our tool evaluations and have put together a recommendation argument based on the results.

See the attached first version of this document.

Based on our evaluations, we currently feel that OpenMRS is the best option to move forward with.

Executive Summary

Several tools were evaluated for their viability as an SHR for OpenHIE. The tool that best matched our requirements was OpenMRS. Given the strength of the OpenMRS data layer and API, its modularity and extensibility, the previous work as part of the RHEA project and its large, active community, we believe that OpenMRS would be highly suitable for use as an OpenHIE SHR. However OpenMRS does have several shortcomings (support for easily storing unstructured data for instance) and therefore further development will be necessary in order to align OpenMRS with the OpenHIE SHR requirements.

The full evaluations are available here:

https://wiki.ohie.org/display/SUB/Shared+Health+Record+Evaluation+Tool

The evaluation tool was designed based on the requirements available here:

https://wiki.ohie.org/pages/viewpage.action?pageId=9437206

Any feedback is more than welcome (even if it’s just an affirmation!) and any comments can either be sent to the mailing list, or discussed on our SHR community call.

We will be discussing this topic in depth on our next call taking place on Tues 2 July 2013 4pm CAT / 10am EDT.

Kind Regards

Hannes

Shared Health Record Recommendation V1.0.pdf (103 KB)

···

–
Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

2

Although we have many (many!) excellent connections into the OpenMRS
developer community, I still think it would be helpful to get a sense of how
well (or poorly) our requirements align with OpenMRS's current product plan
and development schedule. I do not recommend we fork (that isn't likely
needed) -- but I do believe we should expect to dedicate and fund some
developer resources specifically to our OpenHIE requirements as these are
unlikely to already be on the radar.

Just a thought...

Derek Ritz, P.Eng., CPHIMS-CA
ecGroup Inc.
+1 (905) 515-0045
www.ecgroupinc.com

···

From: openhie-shr@googlegroups.com [mailto:openhie-shr@googlegroups.com] On
Behalf Of Hannes Venter
Sent: June 26, 2013 9:37 AM
To: openhie-shr
Subject: Shared Health Record Tool Recommendation

Hi Everyone,

We're nearing the end of our tool evaluations and have put together a
recommendation argument based on the results.
See the attached first version of this document.

Based on our evaluations, we currently feel that OpenMRS is the best option
to move forward with.

Executive Summary
Several tools were evaluated for their viability as an SHR for OpenHIE. The
tool that best matched our requirements was OpenMRS. Given the strength of
the OpenMRS data layer and API, its modularity and extensibility, the
previous work as part of the RHEA project and its large, active community,
we believe that OpenMRS would be highly suitable for use as an OpenHIE SHR.
However OpenMRS does have several shortcomings (support for easily storing
unstructured data for instance) and therefore further development will be
necessary in order to align OpenMRS with the OpenHIE SHR requirements.

The full evaluations are available here:
https://wiki.ohie.org/display/SUB/Shared+Health+Record+Evaluation+Tool
The evaluation tool was designed based on the requirements available here:
https://wiki.ohie.org/pages/viewpage.action?pageId=9437206

Any feedback is more than welcome (even if it's just an affirmation!) and
any comments can either be sent to the mailing list, or discussed on our SHR
community call.
We will be discussing this topic in depth on our next call taking place on
Tues 2 July 2013 4pm CAT / 10am EDT.

Kind Regards
Hannes

--
Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@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/groups/opt_out.

3

Hi Derek,

Thanks for the point, I think it is a valid one and something that our team will look into and feedback on. I agree that we will more than likely need to contribute technically towards our direction.

Regards,

Carl

···

On Wed, Jun 26, 2013 at 3:45 PM, Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Although we have many (many!) excellent connections into the OpenMRS

developer community, I still think it would be helpful to get a sense of how

well (or poorly) our requirements align with OpenMRS’s current product plan

and development schedule. I do not recommend we fork (that isn’t likely

needed) – but I do believe we should expect to dedicate and fund some

developer resources specifically to our OpenHIE requirements as these are

unlikely to already be on the radar.

Just a thought…

Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

www.ecgroupinc.com

From: openhie-shr@googlegroups.com [mailto:openhie-shr@googlegroups.com] On

Behalf Of Hannes Venter

Sent: June 26, 2013 9:37 AM

To: openhie-shr

Subject: Shared Health Record Tool Recommendation

Hi Everyone,

We’re nearing the end of our tool evaluations and have put together a

recommendation argument based on the results.

See the attached first version of this document.

Based on our evaluations, we currently feel that OpenMRS is the best option

to move forward with.

Executive Summary

Several tools were evaluated for their viability as an SHR for OpenHIE. The

tool that best matched our requirements was OpenMRS. Given the strength of

the OpenMRS data layer and API, its modularity and extensibility, the

previous work as part of the RHEA project and its large, active community,

we believe that OpenMRS would be highly suitable for use as an OpenHIE SHR.

However OpenMRS does have several shortcomings (support for easily storing

unstructured data for instance) and therefore further development will be

necessary in order to align OpenMRS with the OpenHIE SHR requirements.

The full evaluations are available here:

https://wiki.ohie.org/display/SUB/Shared+Health+Record+Evaluation+Tool

The evaluation tool was designed based on the requirements available here:

https://wiki.ohie.org/pages/viewpage.action?pageId=9437206

Any feedback is more than welcome (even if it’s just an affirmation!) and

any comments can either be sent to the mailing list, or discussed on our SHR

community call.

We will be discussing this topic in depth on our next call taking place on

Tues 2 July 2013 4pm CAT / 10am EDT.

Kind Regards

Hannes

–

Hannes Venter

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes

E-mail: hannes@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/groups/opt_out.

–

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

–
Carl Fourie
Assistant Director of Programs, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 71 540 4477 | Office: +27 21 701 0939 | Skype: carl.fourie17
E-mail: carl@jembi.org