|DESCRIPTION OF ENHANCEMENTS
Authorization/Subscription Utility version 1.0
rules are defined at a general level in either the Document Definition or
User Class Hierarchies, they are "inherited" by more specfic "descendent"
classes or TITLES.
+ ASU lets you define, populate, and retrieve information about user
classes. These user classes can be defined hospital-wide or more
narrowly for a specific service and can be used across DHCP to replace
and/or complement keys.
+ ASU lets you link user classes with orders and order events or with
TIU Document Definitions and document events. This part of ASU defines
behavior for orders and TIU documents only. In a future version, it may
be extended to define behavior for other clinical entitites.
+ User classes can be populated via a multiple field in the New Person
file pointing to the User Class file.
+ Class members may be active or inactive.
This package implements a User Class Hierarchy which is useful for
+ The Authorization/Subscription file links events (e.g., Sign) with
Document/Order type (e.g., Clinical Warning Note) with User Classes
(e.g., Provider Class).
+ ASU allows infinite hierarchies of subclasses.
+ ASU allows one level of document type to inherit document definition
from a higher level.
identifying the roles that different users fulfill within the hospital,
and allows for the specification of business rules for the handling of
documents by members of such groups. ASU provides a method for identifying
who is AUTHORIZED to do something to a particular kind of document in a
given status (e.g., An UNSIGNED CLINICAL DOCUMENT may be EDITED by a
PROVIDER who is also the EXPECTED SIGNER of the document). When such