Difference between revisions of "Q:In v11 there is a Security Setting of Document - Invalidate which applies to all Documents. How do I give Invalidate Note privledges to a user without allowing them to invalidate all Documents?"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
To allow a user to invalidate a note in v11 without allowing them to invalidate all document types, you need to do two things.  Please note, that although this is an example of "invalidating a note", this same technique applies to all users and document types.
+
To allow a user to invalidate a note in v11 without allowing them to invalidate all [[Document_Type | document types]], two things need to be done.  Please note, that although this is an example of "invalidating a note", this same technique applies to all users and document types.
  
  
 
'''Security Setting'''
 
'''Security Setting'''
  
First you need to give the user the Security Setting of '''Document-Invalidate'''.
+
[[TWAdmin]] / [[Security_Admin | Security Admin]])
 +
 
 +
Assign the user a security classification that includes the code "Document-Invalidate".
  
  
 
'''User Finalization Authority level'''
 
'''User Finalization Authority level'''
  
Next, in order for a user to access, invalidate, etc… a document type, you need to make sure the '''users Finalization Authority Level is set the same or higher than the Document Type Finalization Authority Level'''.
+
TWAdmin / User Admin
 +
 
 +
TWAdmin / Dictionaries / Document Type
 +
 
 +
Next, ensure the Finalization Authority Level for the user is set the same or higher than the Document Type Finalization Authority Level.
 +
 
 +
 
 +
The converse is true for Document Types that a user should not access.  Ensure their Finalization Authority Level is lower than the Document Type Finalization Authority Level.
 +
 
 +
Note that there is also a [[Security_Gates | security gate]] of "document invalidate without finalization authority".  If this gate is left unlocked and users have the same [[V11_Security_Codes | security code]] in their security classification group, they will still be able to invalidate notes that they don't have proper finalization authority on.  To prevent this, remove the code or make sure the gate is locked.
  
  
The same goes for Document Types you do not want the user to access; make sure their Finalization Authority Level is lower than the Document Type Finalization Authority Level.
+
Return to [[V11 FAQ]]

Latest revision as of 16:49, 16 June 2015

To allow a user to invalidate a note in v11 without allowing them to invalidate all document types, two things need to be done. Please note, that although this is an example of "invalidating a note", this same technique applies to all users and document types.


Security Setting

TWAdmin / Security Admin)

Assign the user a security classification that includes the code "Document-Invalidate".


User Finalization Authority level

TWAdmin / User Admin

TWAdmin / Dictionaries / Document Type

Next, ensure the Finalization Authority Level for the user is set the same or higher than the Document Type Finalization Authority Level.


The converse is true for Document Types that a user should not access. Ensure their Finalization Authority Level is lower than the Document Type Finalization Authority Level.

Note that there is also a security gate of "document invalidate without finalization authority". If this gate is left unlocked and users have the same security code in their security classification group, they will still be able to invalidate notes that they don't have proper finalization authority on. To prevent this, remove the code or make sure the gate is locked.


Return to V11 FAQ