Rowan, which ideas/projects are you using? Do you have project pages for each of those on our wiki or somewhere else?
I started a skeleton for Roger's idea here so that we don't forget it: https://wiki.openmrs.org/display/projects/Anatomical+Drawing+Custom+Datatype+%28Design+Page%29 I like Christian's idea for a module too, can you start a page for that? I encourage everyone to at least jot down ideas when you come up with them. We continually have people asking for longer-than-normal projects that are also outside the standard release cycle (aka no time crunch). If we have even skeleton ideas we can expand them and hand them out to volunteers as they come forward. Ben On Thu, Oct 27, 2011 at 11:15 AM, Rowan Seymour <[email protected]>wrote: > I should maybe try reading your emails before replying. I'm not familiar > with the database messaging module but I'll check it out. Though I still > figure that to be able to add translations you have to be working with the > source code, so you might as well be using a tool at that level. > > > On 26 October 2011 20:54, Joaquín Blaya <[email protected]>wrote: > >> Rowan, >> As I mentioned there's already an eclipse plugin to do this the >> ResourceBundle, however, I don't see this as a programmer tool, but >> rather something that we should give to implementers and non-technical >> people who will be able to translate it, my guess was that this was >> the reason for the database messaging module, but it needs the couple >> of tweeks I mentioned. >> >> Joaquín >> ___________________________________________________________________ >> Gerente de Desarrollo, eHealth Systems >> Research Fellow, Escuela de Medicina de Harvard >> Moderador, GHDOnline.org >> >> >> >> On Tue, Oct 25, 2011 at 9:14 AM, Rowan Seymour <[email protected]> >> wrote: >> > @Roger cool idea but perhaps beyond our scope as it would be a >> modification >> > to OpenMRS core >> > @Joaquín I wonder if that shouldn't be implemented as an Eclipse plugin >> > rather than an OpenMRS module? It sounds like a developer tool rather >> than >> > something for OpenMRS users. I wonder if such a tool already exists for >> > Spring based applications? >> > On 24 October 2011 15:01, Friedman, Roger (CDC/CGH/DGHA) (CTR) >> > <[email protected]> wrote: >> >> >> >> How about an "anatomical drawing" custom datatype? There would be >> >> selectable "canvases" which would be line drawings of different parts >> of the >> >> anatomy (whole body back and front; hand/arm top/bottom; retinas; >> etc.). >> >> The user could draw on the selected canvas, adding lines (with color), >> areas >> >> (with color and texture), text (boxes and callouts). >> >> >> >> >> >> >> >> From: [email protected] [mailto:[email protected]] On Behalf Of Rowan >> Seymour >> >> Sent: Monday, October 24, 2011 2:34 AM >> >> To: [email protected] >> >> Subject: Re: [OPENMRS-DEV] Student module ideas >> >> >> >> >> >> >> >> Christian, Joaquín >> >> >> >> >> >> >> >> Thanks for these - I think we have two very suitable module ideas here >> - >> >> I'll get back to you for more details shortly. >> >> >> >> On 24 October 2011 05:53, Christian Neumann <[email protected]> wrote: >> >> >> >> Another idea is a 'Know your OpenMRS database'. >> >> >> >> >> >> >> >> Using OpenMRS for a couple of years and having multiple responsible >> >> persons touching it, we have accumulated quite a few different >> encounter >> >> types and obs. It is not straight forward to see which encounter types >> have >> >> which and how many obs's and underlying concepts. >> >> >> >> >> >> >> >> An 'database archeology' tool that prints out the number of encounters >> per >> >> encounter type, and the numbers of obs with matching concepts per >> encounter >> >> type will be helpful. Maybe together with the first and last time an >> >> encounter type was used. This would help a lot to understand and to >> tidy up >> >> the database. >> >> >> >> >> >> >> >> christian >> >> >> >> >> >> >> >> On Oct 22, 2011, at 2:35 PM, Joaquín Blaya wrote: >> >> >> >> Rowan, >> >> >> >> other ideas that occur to me >> >> >> >> 1. Improving the database messaging module so that you can ask it which >> >> labels are missing for a specific language. For extra credit, it >> would then >> >> list those for you and you would be able to type in the translation >> and it >> >> would automatically save that to the appropriate messages.properties >> file. >> >> Something similar to the ResourceBundle tool for >> >> Eclipse http://sourceforge.net/projects/eclipse-rbe/ >> >> >> >> >> >> >> >> 2. Perhaps fixing tickets to make more modules functional with 1.8? I >> >> have two modules that work with 1.6, but not with 1.8. >> >> >> >> Joaquín >> >> ___________________________________________________________________ >> >> Gerente de Desarrollo, eHealth Systems >> >> Research Fellow, Escuela de Medicina de Harvard >> >> Moderador, GHDOnline.org >> >> >> >> On Fri, Oct 21, 2011 at 9:58 AM, Christian Neumann <[email protected]> >> >> wrote: >> >> >> >> Appointment date suggestion >> >> >> >> >> >> >> >> This would be another client-side hack or modification to HTML form >> entry >> >> so that appointment dates could be suggested based on some >> >> logic (from Christian Neumann) >> >> >> >> >> >> >> >> I think this could also be done 'properly' in HFE. The obs tag might be >> >> able to take additional validation rules as parameters for date obs. I >> can >> >> see these use cases: >> >> >> >> - Relative to the encounter date the appointment date should not be >> more >> >> than x months in the future. >> >> >> >> - The appointment date must be greater than the encounter date. >> >> >> >> - The appointment date can be restricted to certain weekdays (not all >> the >> >> clinics offer service all days during the week). Ideally this is tight >> to >> >> the encounter location. >> >> >> >> - More difficult will be the validation based on other obs or drugs. >> If a >> >> patient only gets drugs for 20 days, the appointment date can't be much >> >> later. >> >> >> >> >> >> >> >> christian >> >> >> >> >> >> >> >> ________________________________ >> >> >> >> Click here to unsubscribe from OpenMRS Developers' mailing list >> >> >> >> >> >> >> >> ________________________________ >> >> >> >> Click here to unsubscribe from OpenMRS Developers' mailing list >> >> >> >> >> >> >> >> ________________________________ >> >> >> >> Click here to unsubscribe from OpenMRS Developers' mailing list >> >> >> >> >> >> >> >> -- >> >> Rowan Seymour >> >> tel: +250 783835665 >> >> http://twitter.com/rowanseymour >> >> >> >> ________________________________ >> >> >> >> Click here to unsubscribe from OpenMRS Developers' mailing list >> >> >> >> ________________________________ >> >> Click here to unsubscribe from OpenMRS Developers' mailing list >> > >> > >> > -- >> > Rowan Seymour >> > tel: +250 783835665 >> > http://twitter.com/rowanseymour >> > >> > ________________________________ >> > Click here to unsubscribe from OpenMRS Developers' mailing list >> >> _________________________________________ >> >> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to >> [email protected] with "SIGNOFF openmrs-devel-l" in the body >> (not the subject) of your e-mail. >> >> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] >> > > > > -- > *Rowan Seymour* > tel: +250 783835665 > http://twitter.com/rowanseymour > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
