I don’t think I have a different view of the SHR, it really depends on how the group envisions the software being deployed and/or used. I’ve brought some biases
to the commentary which reflect our environment/development which may not be the target environment for OpenSHR.
···
Great, thanks Justin. You comment are very useful. I’ve just been reading the ones from OpenSHR. If you have any fundamentally different views we are interested in hearing
those to. These documents are very much working drafts
Cheers,
Ryan
On Wed, Feb 27, 2013 at 10:16 AM, Ryan rg.crichton@gmail.com wrote:
Great, thanks Justin. You comment are very useful. I’ve just been reading the ones from OpenSHR. If you have any fundamentally different view we are interested in hearing those welcome. These documents are very much working drafts
Cheers,
Ryan
On Tue, Feb 26, 2013 at 10:01 PM, Justin (Mohawk College) justin.fyfe1@mohawkcollege.ca wrote:
Hi Ryan,
Sorry for not getting to this sooner than I had hoped. We had some domestic projects that required a little TLC … I have posted comments/questions/thoughts in the SHR document and should work through the interoperability layer later
today/tomorrow.
Cheers
-Justin
On Tuesday, February 26, 2013 6:14:33 AM UTC-5, Ryan Crichton wrote:
Hi all,
As most of you are aware we are in the process of evaluating the options for a Shared Health Record and Interoperability layer for use with the OpenHIE project. This involves reviewing what we have created for Rwanda and looking at new
options as well.
At the moment we are trying to define the requirements for a SHR and an Interoperability Layer for use within OpenHIE so that we have something to evaluate against.
We would like to ask you to help us by reviewing the documentation that has been created from the discussions of these communities and ensure we have captured your idea of a SHR and Interoperability layer correctly. These are designed to
be stick men that we are ready to alter as need be so feel free to add comments, or point out things that we have missed, or even suggest completely different paradigms that we should explore as a group. Here are the links for review. Please review the sections
marked use cases and requirements:
SHR: https://docs.google.com/document/d/1Vv_2QPr5nfVWmAp3YuT__8l3zect1ZLvzRKvivxkvls/edit#
Interoperability Layer: https://docs.google.com/document/d/1doz07xPGcta_1lu1f_9xgNuveN8d70dU0hgz7P6tJtk/edit#
Thanks all, we hope to go over the input that we have received on the next call. We will send out an invite soon.
Thanks,
Ryan
–
Ryan Crichton
Senior Software 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 “OpenHIM-Dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
openhim-dev+unsubscribe@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
–
Ryan Crichton
Senior Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile:
+27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org
–
Ryan Crichton
Senior Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org