Name | Value |
---|---|
NAME | ORCL CPRS ACCESS |
MENU TEXT | GUI Access - Tabs, RPL |
UPPERCASE MENU TEXT | GUI ACCESS - TABS, RPL |
PACKAGE | ORDER ENTRY/RESULTS REPORTING |
DESCRIPTION | This option provides input template access for editing CPRS GUI access the CPRS GUI application. In addition, the Tools/Options menu restricts access to patient selection settings. Scenario B - The user sees all tabs and can select from all patients. Scenario C - The user has no access to the CPRS GUI. Scenario D - The user has access to the Reports Tab only, and all patients. restrictions in the NEW PERSON file [^VA(200,] for cover sheet tabs and The following matrix should indicate what to expect: Restr. Pt. List OE/RR Team Tab(s) Scenario = = = = = = = = = = = = = = = = = = = = = = = (blank) (none) (none) C (blank) XYZ Team (none) C (blank) XYZ Team RPT C Y (none/invalid) RPT C N XYZ Team RPT D Y XYZ Team RPT A user-specific restricted patient selection lists. N N/A COR B N N/A COR, RPT B Y N/A COR B Y N/A COR, RPT B (blank) N/A COR C (blank) N/A COR, RPT C It will be seen that the "COR" tab overrules other tab settings, allows access to all tabs, and also allows access to all patients - except when the "RESTRICTED PATIENT SELECTION" entry is left blank. Note that more than one entry can be made for the same tab. For example, a "RPT" tab entry could be made for a user with valid dates equating to the second week of the current month, then another "RPT" entry made with dates allowing access for the first week of the next month. To create a duplicate entry of the same tab, the user must select "No" when prompted for the new entry on a blank line. Some users may not be familiar with this standard Fileman behavior. The ruling logic for multiple entries of the same tab is: Note that there is a logic path followed by the GUI application with If any entry for a given tab allows access to the tab as of the date of login, then the tab is allowed, regardless of any other entries which may exist for that tab. regard to the entries in all of these fields under discussion. The possible scenarios are: Scenario A - The user is restricted to, and sees only, the REPORTS tab of |
CREATOR | ADAM,ADAM |
DIC {DIC} | VA(200, |
DIC(0) | AEMQ |
TYPE | edit |
DIE | VA(200, |
DR {DIE} | [OR USER ACCESS OPTIONS] |
NO UP-ARROW | BACK JUMPING OK, NO EXIT |