Abstract:
To make the system more user friendly and interactive, it is required to develop a role based home page. Growing of health care industry and demand of electronic medical records made the developers a greater concern to present the system as per the user role. The different screens will guide to work on the system in the better way. Roles are simply a comma-delimited String of role names that are added to the Principal to associate the current user with one or more roles.
Content:
I like the idea posted on ttp://openmrs.org/wiki/Unassigned_Projects. The title is ROLE BASED HOME PAGE .My efforts will actually aim to complete different tasks. Despite that, all have something in common. They enhance the interface to manage an OPENMRS site. In this project to define the homepage as per the role defined to a user. In the developing nation, there may be multiple novice users who are working on the medical record system. The data manager as well as data entry personal will face the same problem. What I'm doing here is just using a static page as a home page. You'll need to flag the static
page as "Promoted to front page" and "static on front page". Also, it will look better if you change the default story publishing preference to make all other content not be promoted to the front page by default. While someone could override this, as long as you have control over the content creators, it works well enough.
To overcome this there are milestones to be competed:
· User Interface change as per the user.
· Template layout and system flow as per the role of a user.
· Appropriate unit tests for newly developed functionality (All test cases to be charted in a phase wise.
· Implementer-specific documentation so that environments can begin using the new feature
· Evidence of one implementation using the feature.
(I worked on management projects especially on medical management system. I understand the concept of user understanding and user flexibility in working with the system. The configuration of the system
modules change as per system requirement.).For the documentation I’ll prepare a Gantt chart and UML diagrams (use case, class and sequence diagram) in the ongoing phase of project development. The system will be designed in CSS, JavaScript and XHTML. And it will help in look and feel if I’ll try AJAX functionality in it.
Profit for Open MRS Demand of electronic medical records in developing countries will face different sort of users. So to remove this flaw, the role based home page come on to act. Different users will have different interface and help in understanding the system very well. OPENMRS will get easy accessibility.
1. Facilitate the use of OpenMRS by allowing the user to change and reorganize information more quickly, thus making the interface more intuitive and responsive.
2. Easier deployment of OpenMRS installations to clients by adapting the user interface to their needs.
E.g. a site for a medical dealer audience requires different interface than one that sells custom-made suits.
There are a number of ways to perform role-based authorization, once you have specified the user's roles. One of the more common approaches is to use the
element in the Web.config file. With this element, you can restrict or grant access to the Web application based on roles. For example, imagine that you wanted to allow only those playing the Administrator or Can Edit roles to a particular Web application or directory in a Web application. To do so, you would simply need to add the following line in your directory's Web.config file:
Sample not final
Some sort of view of role based home page.
The role names are: Patient, Person relationship, Doctors, admin, data managers, users and business orders/ Stakeholder.
The functionalities are:
* Enabling form authentication.
* Authenticating user on every request
Additional info: http://docs.google.com/Doc?id=dcx96g4h_582f9x4rcs
