medfetch wrote on Friday, January 06, 2017:
Ultimately menu access will should be limited on account creation using a mechanism built alongside the current process, if not directly in this.
Currently the demo allows anyone to toggle to any role as a user preference. (All the ACL restrictions are still present.)
If I find during my day that I (as a clinician) need to perform a task not in the "Clinical Staff" menu, I switch over to the default. Over time, if the task I could not do from the Clinical Menu is a task that should be in the Clinical Menu, I add it.
What I am asking is for anyone to look at the menus and suggest what other tasks should be included out-of-the-box for a given role.
Once an instance of openEMR is deployed, the practices can:
1. switch everyone to the "default" menu and continue as if there were no role-based menus (current)
2. manually go in and alter the code like I do (bad idea)
3. pay for support to add menu items (most logical)
4. we build a web based menu-builder that allows the admin user to edit the menus to suit their needs