The Master Data Model for Veteran Care

Developer Documentation » VDM » Usr_Class-8930

Usr Class (8930)

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.

Global: ^USR(8930,

Domain: Non-Clinical

Properties

Label/Field Name Field # Description Datatype Attributes Range
Name
  name
.01 This is the name of the user class (e.g., Transcriptionist, Medical Record
Technician, MIS Manager, Medical Student, Nurse, Resident, etc.).
STRING INDEXED
REQUIRED
 
Abbreviation
  abbreviation
.02   STRING INDEXED  
Active
  active
.03   ENUMERATION INDEXED
REQUIRED
Active: 1
Inactive: 0
Display Name
  display_name
.04   STRING INDEXED  
Person Class
  person_class
.05 This 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.
POINTER   Person_Class-8932_1
Subclass
  subclass
1 If 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.
POINTER   Usr_Class-8930
Ok To Distribute
  ok_to_distribute
2 Answer “YES” if this individual User Class is to be distributed
nationally. Answer “NO” if not.
BOOLEAN   false: 0
true: 1

↑ Return to top


Document generated on August 31st 2017, 2:55:41 pm