OpenMRS as the SHR design

Hi all,

We at Jembi have put together a design for how OpenMRS can be made to act like an SHR. I would like to get the communities feedback and input on how this looks. We have incorporated much of the modifications that we have discussed previously and written this up into a more concrete design.

You can find the design document here: https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document

Please can you read through this and post to this thread if you have any feedback or if you have some better ideas on how this design can be done. We can also discuss this on the next SHR call.

Cheers,

Ryan

···


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

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

Hi Ryan.

As one who is expert with the OpenMRS technology stack, and equally expert regarding what are the requirements for our OpenHIE SHR, can you broadly estimate the effort (in effort-weeks, maybe) for us to get from where we are to where we need to be?

My initial reaction to reading the linked page was… wow, we need to make a lot of changes.

Thanks,

Derek.

Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

www.ecgroupinc.com

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and destroy the message and any attachments.

···

Le présent courriel et les documents qui y sont joints sont confidentiels et protégés et s’adressent exclusivement au destinataire mentionné ci-dessus. L’expéditeur ne renonce pas aux droits et privilèges qui s’y rapportent ni à leur caractère confidentiel. Toute prise de connaissance, diffusion, utilisation ou reproduction de ce message ou des documents qui y sont joints, ainsi que des renseignements que chacun contient, par une personne autre que le destinataire prévu est interdite. Si vous recevez ce courriel par erreur, veuillez le détruire immédiatement et m’en informer.

From: openhie-shr@googlegroups.com [mailto:openhie-shr@googlegroups.com] On Behalf Of Ryan Crichton
Sent: October 2, 2013 8:00 AM
To: openhie-shr@googlegroups.com
Subject: OpenMRS as the SHR design

Hi all,

We at Jembi have put together a design for how OpenMRS can be made to act like an SHR. I would like to get the communities feedback and input on how this looks. We have incorporated much of the modifications that we have discussed previously and written this up into a more concrete design.

You can find the design document here: https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document

Please can you read through this and post to this thread if you have any feedback or if you have some better ideas on how this design can be done. We can also discuss this on the next SHR call.

Cheers,

Ryan

Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@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.

Hi Derek,

There are a fair number of changes that need to be made. I’m looking at around a 6 month time frame to get to the level described in the design doc but we will have something to show earlier than that. The full discrete CDA support will take some time to get right however.

Cheers,

Ryan

···

On Thu, Oct 3, 2013 at 3:38 PM, Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Ryan.

As one who is expert with the OpenMRS technology stack, and equally expert regarding what are the requirements for our OpenHIE SHR, can you broadly estimate the effort (in effort-weeks, maybe) for us to get from where we are to where we need to be?

My initial reaction to reading the linked page was… wow, we need to make a lot of changes.

Thanks,

Derek.


Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

www.ecgroupinc.com

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and destroy the message and any attachments.


Le présent courriel et les documents qui y sont joints sont confidentiels et protégés et s’adressent exclusivement au destinataire mentionné ci-dessus. L’expéditeur ne renonce pas aux droits et privilèges qui s’y rapportent ni à leur caractère confidentiel. Toute prise de connaissance, diffusion, utilisation ou reproduction de ce message ou des documents qui y sont joints, ainsi que des renseignements que chacun contient, par une personne autre que le destinataire prévu est interdite. Si vous recevez ce courriel par erreur, veuillez le détruire immédiatement et m’en informer.

From: openhie-shr@googlegroups.com [mailto:openhie-shr@googlegroups.com] On Behalf Of Ryan Crichton
Sent: October 2, 2013 8:00 AM
To: openhie-shr@googlegroups.com
Subject: OpenMRS as the SHR design

Hi all,

We at Jembi have put together a design for how OpenMRS can be made to act like an SHR. I would like to get the communities feedback and input on how this looks. We have incorporated much of the modifications that we have discussed previously and written this up into a more concrete design.

You can find the design document here: https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document

Please can you read through this and post to this thread if you have any feedback or if you have some better ideas on how this design can be done. We can also discuss this on the next SHR call.

Cheers,

Ryan

Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@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.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

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

Hi,

I would agree with Ryan’s estimate, but we may be able to cut down on what components we will have to take care of if we can get the greater OpenMRS community to support some of our requirements, and dedicate community resources to complete them.

For example, building OpenMRS notes seems to be a prime example where the core team members may be involved. Perhaps (based on decisions made during the OMRS implementer meeting) we can organize a OMRS-SHR sprint together with the OpenMRS community ?

···

On Thu, Oct 3, 2013 at 9:54 AM, Ryan Crichton ryan@jembi.org wrote:

Hi Derek,

There are a fair number of changes that need to be made. I’m looking at around a 6 month time frame to get to the level described in the design doc but we will have something to show earlier than that. The full discrete CDA support will take some time to get right however.

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+unsubscribe@googlegroups.com.

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

On Thu, Oct 3, 2013 at 3:38 PM, Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Ryan.

As one who is expert with the OpenMRS technology stack, and equally expert regarding what are the requirements for our OpenHIE SHR, can you broadly estimate the effort (in effort-weeks, maybe) for us to get from where we are to where we need to be?

My initial reaction to reading the linked page was… wow, we need to make a lot of changes.

Thanks,

Derek.


Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

www.ecgroupinc.com

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and destroy the message and any attachments.


Le présent courriel et les documents qui y sont joints sont confidentiels et protégés et s’adressent exclusivement au destinataire mentionné ci-dessus. L’expéditeur ne renonce pas aux droits et privilèges qui s’y rapportent ni à leur caractère confidentiel. Toute prise de connaissance, diffusion, utilisation ou reproduction de ce message ou des documents qui y sont joints, ainsi que des renseignements que chacun contient, par une personne autre que le destinataire prévu est interdite. Si vous recevez ce courriel par erreur, veuillez le détruire immédiatement et m’en informer.

From: openhie-shr@googlegroups.com [mailto:openhie-shr@googlegroups.com] On Behalf Of Ryan Crichton
Sent: October 2, 2013 8:00 AM
To: openhie-shr@googlegroups.com
Subject: OpenMRS as the SHR design

Hi all,

We at Jembi have put together a design for how OpenMRS can be made to act like an SHR. I would like to get the communities feedback and input on how this looks. We have incorporated much of the modifications that we have discussed previously and written this up into a more concrete design.

You can find the design document here: https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document

Please can you read through this and post to this thread if you have any feedback or if you have some better ideas on how this design can be done. We can also discuss this on the next SHR call.

Cheers,

Ryan

Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@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.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

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

E-mail: ryan@jembi.org

Hi Suranga,

Yes, that is a good plan. I’m planning to try talk to a number of the members of the core OpenMRS community to see where our plans overlap so that we can work together on some of this. I’l try keep this group updated on conversations that occur during the conference this coming week.

Cheers,

Ryan

···

On Thu, Oct 3, 2013 at 8:01 PM, Suranga Kasthurirathne suranga@jembi.org wrote:

Hi,

I would agree with Ryan’s estimate, but we may be able to cut down on what components we will have to take care of if we can get the greater OpenMRS community to support some of our requirements, and dedicate community resources to complete them.

For example, building OpenMRS notes seems to be a prime example where the core team members may be involved. Perhaps (based on decisions made during the OMRS implementer meeting) we can organize a OMRS-SHR sprint together with the OpenMRS community ?


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

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

On Thu, Oct 3, 2013 at 9:54 AM, Ryan Crichton ryan@jembi.org wrote:

Hi Derek,

There are a fair number of changes that need to be made. I’m looking at around a 6 month time frame to get to the level described in the design doc but we will have something to show earlier than that. The full discrete CDA support will take some time to get right however.

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+unsubscribe@googlegroups.com.

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

On Thu, Oct 3, 2013 at 3:38 PM, Derek Ritz (ecGroup) derek.ritz@ecgroupinc.com wrote:

Hi Ryan.

As one who is expert with the OpenMRS technology stack, and equally expert regarding what are the requirements for our OpenHIE SHR, can you broadly estimate the effort (in effort-weeks, maybe) for us to get from where we are to where we need to be?

My initial reaction to reading the linked page was… wow, we need to make a lot of changes.

Thanks,

Derek.


Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

www.ecgroupinc.com

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and destroy the message and any attachments.


Le présent courriel et les documents qui y sont joints sont confidentiels et protégés et s’adressent exclusivement au destinataire mentionné ci-dessus. L’expéditeur ne renonce pas aux droits et privilèges qui s’y rapportent ni à leur caractère confidentiel. Toute prise de connaissance, diffusion, utilisation ou reproduction de ce message ou des documents qui y sont joints, ainsi que des renseignements que chacun contient, par une personne autre que le destinataire prévu est interdite. Si vous recevez ce courriel par erreur, veuillez le détruire immédiatement et m’en informer.

From: openhie-shr@googlegroups.com [mailto:openhie-shr@googlegroups.com] On Behalf Of Ryan Crichton
Sent: October 2, 2013 8:00 AM
To: openhie-shr@googlegroups.com
Subject: OpenMRS as the SHR design

Hi all,

We at Jembi have put together a design for how OpenMRS can be made to act like an SHR. I would like to get the communities feedback and input on how this looks. We have incorporated much of the modifications that we have discussed previously and written this up into a more concrete design.

You can find the design document here: https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document

Please can you read through this and post to this thread if you have any feedback or if you have some better ideas on how this design can be done. We can also discuss this on the next SHR call.

Cheers,

Ryan

Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@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.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

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

E-mail: ryan@jembi.org