medfetch wrote on Thursday, January 05, 2017:
First I hope we agree that the current "default" menu is an eyesore. It makes for a steep learning curve for users. They have to learn what to ignore, and ignore it forever instead of giving them what they need up front.
I haven't got around to the Billing/Back Office Menu yet. It is definitely a required role-based menu. I wanted to first sit down with the billing company I use and go through their work-flows to create something logical. Life is short and time is a commodity, but I will look to do this next week.
What did you think of the role-based menus that are present? To a new comer opening openEMR for the first time, they make sense compared to the current "default" menu. They can get to work quite quickly with a lot less instruction. Should we add some other menu items to these roles?
The demo today allows any user to change their menu as a user-preference. ACL restricts what they can actually do based on the type of priviledges they were assigned. This is just for show for the demo.
Part of the role-based menu concept is that the menus will be customizable at the admin level - what you want on a given menu is all that's the user can see. It would not be adjustable as a user preference unless you are priviledged. This should really only be done by someone who knows openEMR and for most people, this would be another really good reason to pay for support. What I propose, while this customizable menu is being built, is to consider deploying these pre-cast (essentially immutable) role-based menus in the interim, if you want. You can always feed up the default menu...
Since there are two concepts in this thread, the role-based menu and the new default menu, I'll start a new thread and post pics of the menus for those who want to see them that way rather than the demo.