A way forward

[Surajit Nundy]

Dear all:

We are all very grateful that you have spent so much time and given this question your valuable consideration.  The messages posted to the group this week have been truly illuminating and helpful, at least to me, and serve as a great example of how discussions can really help a collaboration.  

We do need to make a decision and move forward now. To take a step back, our motivation in this is to:-

1.  Design Raxa to be a point-of-care system that is extensible and scalable

- work for other providers with similar needs to those at JSS

- be easily extensible by people wishing to customize and enhance the system for their own different needs

- serve as a potential platform for public health initiatives with large data

2.  Design a system that would be able to withstand unreliable power and network availability (please see attached network diagram)
- work on server and clients in the few acres at JSS 
- sync to a cloud server using an unreliable connection
- connect the cloud with devices at remote community health locations using less reliable wireless networks

but perhaps most importantly,

3.  Actually create a system!

- our volunteer development model is good for evolution, not great for revolution

- we need to create a working system soon that we can iterate on

- We are biting off a lot as it is and it is important that we reign in aspirations until we have created something

Given these considerations, here is a 2-phase approach.  Initially, we use the relational databases in OpenMRS and build out functionality in the backend to accomplish some of the (non-trivial) syncing that will allow us to deal with the unreliablility in the system.  Subsequently (v2 for Matt), we add in functionality like CouchDB and CouchApps to make the application scalable, fault-tolerant and elegant.  

Shuro

[Surajit Nundy]

It looks like the attachment was blocked by Google Groups. I have
uploaded the network diagram to
https://wiki.openmrs.org/display/projects/Raxa+JSS+EMR+Application+Architecture.

Thanks,
Shuro

[Saptarshi Purkayastha]

Hi Shuro,

I was able to see the attachment in the first email that you sent

Thanks for conveying this to the group and we hope everyone sees the reasons why we have taken the decision.

We hope the contributors can now start implementing the UX from the user-stories that have been worked on...

---
Regards,
Saptarshi PURKAYASTHA

My Tech Blog:  http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE

--
You received this message because you are subscribed to the Google Groups "Raxa JSS EMR Database" group.
To post to this group, send email to raxa-jss-e...@googlegroups.com.
To unsubscribe from this group, send email to raxa-jss-emr-dat...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/raxa-jss-emr-database?hl=en.

[Daniel Pepper]

As someone who has been at JSS for the past few months, I’ve seen the daily need for an information system – any system – that can reliably serve the needs outlined below. Against this pressing are balanced the ambitions of our project. I agree with the strategy to proceed with a modified OpenMRS, while continuing to explore our interest in CouchDB and CouchApps in the hopes it can become, as Shuro states, a scalable, fault-tolerant, and elegant reality in version 2.

Best,
 Daniel

[judy wawira]

Looks good

--

You received this message because you are subscribed to the Google Groups "Raxa JSS EMR Database" group.
To post to this group, send email to raxa-jss-e...@googlegroups.com.
To unsubscribe from this group, send email to raxa-jss-emr-dat...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/raxa-jss-emr-database?hl=en.

--
Judy