Our general feeling has been that we don't want to spend the time fixing the HTML Form Entry use case (HTML-285) but instead focus on the general use case (TRUNK-1640) with the intent that it should solve the needs of the user that that reported HTML-285. I was keeping HTML-285 open with the intention of closing it once TRUNK-1640 was implemented and we confirmed that it supported Jonathan Gallingan's use case. Perhaps it would be better if I marked HTML-285 as "won't fix" at this point to avoid confusion?
@Ben-are you referring to the "Filtering Forms on Dashboard" project? I assume that Mathis is planning on building this functionality to meet Jonathan's requirements for his implementation. If TRUNK-1640 is indeed a GSoC project, there will have to be some co-ordination... I don't know if end of summer would meet Jonathan's timeframe. Mark From: [email protected] [mailto:[email protected]] On Behalf Of Ben Wolfe Sent: Thursday, April 12, 2012 9:00 AM To: [email protected] Subject: Re: [OPENMRS-DEV] Fwd: Regarding ticket TRUNK-1640: Add roles-based form display feature https://tickets.openmrs.org/browse/TRUNK-1640 is actually listed a summer of code project https://wiki.openmrs.org/display/RES/Summer+Of+Code+2012 . That is a bigger api-based change that will work for all form-based entry methods (formentry, htmlformentry, and xforms) The https://tickets.openmrs.org/browse/HTML-285 is just modify some work in htmlformentry done by Jembi to work with newer versions of openmrs. It will only work with htmlformentry. I'm not sure what the PHR module uses. I think it uses its own authentication mechanism to verify the patient is looking at their own page and/or it is a clinician looking at its own patient and grants proxy privileges. This isn't the same issue. (and we're trying to limit the use of proxy privileges going forward in favor of something yet-to-be-determined that is more secure and sustainable) https://wiki.openmrs.org/display/docs/PHR+Module Ben On Wed, Apr 11, 2012 at 3:18 PM, Joaquín Blaya <[email protected]<mailto:[email protected]>> wrote: Hi Mathias, Though I can't help you with the ticket itself, I would ask that this also work for XForms if possible i.e. it doesn't display, or doesn't let you edit depending on roles. Though I don't know much about how the mechanism works, I think since both HTML and XForms are called from the same page when you click on the icon, it might not need any additional work. I've also added this to the ticket. Joaquín ___________________________________________________________________ Gerente de Desarrollo, eHealth Systems<http://www.ehs.cl/> Research Fellow, Escuela de Medicina de Harvard<http://hms.harvard.edu/> Moderador, GHDOnline.org<http://www.ghdonline.org/> On Wed, Apr 11, 2012 at 2:17 PM, Mathias Lin | Meta Healthcare <[email protected]<mailto:[email protected]>> wrote: (Not sure if my previous mail got through to the mailing list - I see it in my sent folder and list archive, but haven't received it in my inbox nor spam folder myself. Therefore again..) This mail concerns ticket "TRUNK-1640: Add roles-based form display feature", which is related to https://tickets.openmrs.org/browse/HTML-285 and therefore my question below probably addresses Ben & Darius directly: As I understand, the feature is almost done/issue resolved but some minor feedback is yet unfinished, and the ticket is unassigned at the moment (due to time constraints of the initial author). I will meet with Jonathan (the initial creator of ticket HTML-285) to discuss his requirements in detail as he needs his for his system implementation. As I understand, the ticket 1640 would resolve his issue actually, so I am looking into picking up this 1640 ticket, however, I would need some clarification the status, how to best implement/finish it, and eventually one of the core team members that I can turn to in case of any questions along the way, since this issue concerns the core, not an external module. Also, a rough estimation about the complexity of the task would be helpful. Another question that is related is: I am aware of the PHR module at https://wiki.openmrs.org/display/docs/PHR+Module, which also deals with authentication and authorization in certain ways. I wonder how/if these modules implement two entirely different mechanisms, or if they're in some way related (though a bit different, one is role-centric, the other is user-centric; plus HTML-1640 is directly built into the core). -> or do we have two developments here in parallel that could actually solve the same issue. - Mathias IRC: mathiaslin Skype: mathias.lin _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected]<mailto:[email protected]> with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]<mailto:[email protected]>?body=SIGNOFF%20openmrs-devel-l] ________________________________ Click here to unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe<mailto:[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]
