by Janet Clarke
Hmm … why take another look at the 6.x MIS Person Profile dictionary? – Because the first crucial decisions made here can impact how efficiently you can create or edit users in the future.
As I mentioned in an earlier post, the Person Profile dictionary enables you to create a profile, or set of access settings, that can then be assigned when building individual users. Access to edit or assign profiles within this dictionary can be limited by listing analysts on the first page. User Emulation Restriction and the Security Level assignments are also defined here.
Interestingly, access to Application Databases is assigned in this dictionary, but assignment of the specific menus (and to FOCUS applications) is made through use of another new dictionary – the Menu Procedure Access Dictionary. As a result, some simplicity is lost as you need to remember which databases get assigned where. (New FOCUS applications include EMR, OM, PCM, EDM and PCS.)
The Person Profile dictionary also includes several new or improved fields that define user (Profile) permission to:
- Access patient pictures
- Enter/edit MIS Allergen dictionary
- Enter/confirm patient allergies
- Edit home medications
- Edit patient problems
- Assign diagnoses
- Access specific websites
- Access links within specific websites
- Access printers
- Access to financial report routines & databases
I think having the clinical definitions in MIS will make it easier to manage these fields.
The dictionary also includes a History button that provides you with an audit trail of edits to specific profiles and content changes to round out the features of the Person Profile dictionary.
Turns out the 6.x Person Profile is a mixed bag. Any improvements are off-set by potential confusion – it seems like two steps forward and one step back! When one considers the tremendous endeavor involved in upgrading to 6.x, the Person Profile dictionary does not represent a strong entry in the Pro column.