Difference between revisions of "User Views"
| Line 5: | Line 5: | ||
There are three ways user views can be created or modified: | There are three ways user views can be created or modified: | ||
<ol> | <ol> | ||
<li>From the [[Roles]] setup page.</li> | <li>From the [[Roles]] setup page.<br/> | ||
<li>From the [[Users]] setup page.</li> | <i>This is ideal for designing a user view that should be used by a wide number of users, such as internal views for all pharmacy staff.</i></li> | ||
<li>From the home page actions menu.</li> | <li>From the [[Users]] setup page.<br/> | ||
<i>For creating or amending user views for an individual user.</i></li> | |||
<li>From the home page actions menu.<br/> | |||
<i>If the user has the <strong>EDITVIEWS</strong> permission they can create or modify their own user views from the actions menu.</i></li> | |||
</ol> | </ol> | ||
No matter where the user view is created from the process is broadly the same. | No matter where the user view is created from the process is broadly the same. | ||
=Creating a new user view= | |||
It's worthwhile reiterating the importance of choosing the correct avenue for creating user views. While it may seem self-evident that user views are best created from the Users setup page this is usually not true. | |||
When user views are created or modified on the Users setup page, or by the user themselves from the actions menu, that new user view is only created or modified for that individual user. That is sometimes the desired outcome of course, <strong>but more often than not it makes sense for user views to be created equally for whole groups of users</strong>. For example all pharmacy staff likely need access to all outstanding prescriptions for their entire pharmacy, ward staff should only be able to see prescriptions for their assigned ward, and porters probably only need to see bagged prescriptions that are waiting for collection & delivery. | |||
When creating a new user view or modifying an existing one, carefully consider whether it should apply to multiple users or just an individual. | |||
Revision as of 10:20, 4 October 2022
User views, sometimes known as homepages, are how users and pharmacies can view and interact with the live prescription data flowing through PTS and are the primary viewpoint into your system data. Whether it be the pharmacy homepages, the ward views, outpatient collection status screen or the mobile app; all are customised user views.
This page discusses how user views are created. See the User Views & Homepages page for more information on user views.
There are three ways user views can be created or modified:
- From the Roles setup page.
This is ideal for designing a user view that should be used by a wide number of users, such as internal views for all pharmacy staff. - From the Users setup page.
For creating or amending user views for an individual user. - From the home page actions menu.
If the user has the EDITVIEWS permission they can create or modify their own user views from the actions menu.
No matter where the user view is created from the process is broadly the same.
Creating a new user view
It's worthwhile reiterating the importance of choosing the correct avenue for creating user views. While it may seem self-evident that user views are best created from the Users setup page this is usually not true.
When user views are created or modified on the Users setup page, or by the user themselves from the actions menu, that new user view is only created or modified for that individual user. That is sometimes the desired outcome of course, but more often than not it makes sense for user views to be created equally for whole groups of users. For example all pharmacy staff likely need access to all outstanding prescriptions for their entire pharmacy, ward staff should only be able to see prescriptions for their assigned ward, and porters probably only need to see bagged prescriptions that are waiting for collection & delivery.
When creating a new user view or modifying an existing one, carefully consider whether it should apply to multiple users or just an individual.