This file is intended to allow the definition of user classes in such a way that they are useful across packages. It will undoubtedly evolve with more experience in this area. These user classes are then used to support part of the the "authorization" concept - who may do what to a document, order, etc. They are also used to support part of the "subscription" concept - who should receive something, e.g. a notification that a document needs signature. The User Authorization/Subscription file points to the User Class file to allocate authorizations/subscriptions to appropriate user classes. The User Class Membership file links users in the New Person file to User Classes. This file supports an infinite hierarchy of subclasses, with each entry having as many subclasses as desired. Subclasses are contained in the same file, as entries in their own right. A class automatically contains as members all members of its subclasses, as well as explicit members of the class itself.
.01name(+)0;1FREE TEXTBThis is the name of the user class (e.g., Transcriptionist, Medical Record Technician, MIS Manager, Medical Student, Nurse, Resident, etc.).
.02abbreviation0;2FREE TEXTC
.03active(+)0;3SET OF CODES1:Active
.04display name0;4FREE TEXTDNAME
.05person class0;5POINTER8932.1This provides a mapping between the User Class file of ASU and the Person Class file, which encodes the HCFA draft standard Taxonomy of Health Care Providers.
1subclass1;0MULTIPLE8930.01If for example Service Chief is entered as a subclass of Staff Physician, then persons listed as service chiefs inherit all privileges assigned to staff physicians. A subclass of a class is a subset of the class. For example, since the class Staff Physician. Subclasses will be used for inheriting user authorizations/subscriptions. For example, if an entry in the User Authorization/Subscription file states that the user class Staff Physician may sign progress notes, and if the entry states that this entry includes user subclasses, and if Service chief is a subclass of class Staff Physician in the User Class file, then service chiefs may also sign progress notes. If a User Authorization/Subscription file entry includes user subclasses, it also includes subclasses of subclasses, etc.
2ok to distribute2;1BOOLEAN1:YES
Answer "YES" if this individual User Class is to be distributed nationally. Answer "NO" if not.

Referenced by 10 types

  1. REQUEST SERVICES (123.5) -- result mgmt user class
  2. CPE ROLE (232.5) -- role
  4. STANDARD POSITION (403.46) -- user classification
  5. TEAM POSITION (404.57) -- user class
  6. TIU DOCUMENT DEFINITION (8925.1) -- class owner
  7. TIU TEMPLATE (8927) -- editor class
  8. USR AUTHORIZATION/SUBSCRIPTION (8930.1) -- user class
  9. USR CLASS MEMBERSHIP (8930.3) -- user class
  10. PARAMETERS (8989.5) -- entity