AUTHORIZATION/SUBSCRIPTION (162)    PACKAGE (9.4)

Name Value
NAME AUTHORIZATION/SUBSCRIPTION
PREFIX USR
DEVELOPER (PERSON/SITE) JER/SLC
DEVELOPMENT ISC SALT LAKE
CLASS National
CURRENT VERSION 1.0
SHORT DESCRIPTION User Authorization
VERSION
  • 1.0
    DATE DISTRIBUTED:   2005-11-19 00:00:00
    PATCH APPLICATION HISTORY:
    • 1
      DATE APPLIED:   1997-12-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 1, USR*1.0*1. This patch removes broken subclass pointers
      from file 8930 the USR CLASS FILE.
      
    • 10
      DATE APPLIED:   1998-10-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 10, USR*1.0*10. This patch fixes a problem with an undefined
      when removing a user from class membership. See the National Patch Module
      for a complete description.
      
    • 11 SEQ #11
      DATE APPLIED:   1999-10-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 11, USR*1.0*11. Make data element 8930,.03 required. See the
      National Patch Module for a complete description.
      
    • 12 SEQ #12
      DATE APPLIED:   1999-12-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      AUS patch 12.  USR*1.0*12.  This patch fixes the problem of entering
      the Expiration date less than the Effective date.  BUILD CAN BE FOUND
      ON THE NATIONAL PATCH MODULE UNDER PATCH USR*1.0*12.
      
    • 13 SEQ #13
      DATE APPLIED:   2000-04-17 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch fixes the problem that was detected by patch USR*1.0*12.  Field 
      that will be run during the Post-Install.  This utility routine will print 
      the total number of corrections made to the global ^USR(8930.3).
       
      This patch will also correct the problem of entering a Authorized/Subscription 
      Effective date that is greater than the Expriation date.  This change is 
      changing the routine USRU and the DD(8930.3) input transform on the .04 
      field.
      
      A description of the this build can be found on the NATIONAL PATCH MODULE 
      UNDER USR*1.0*13. 
      .04 (Expiration Date) in global ^USR(8930.3) is a date only field and is 
      showing some invalid entries when a VA Fileman validate is run.  When a 
      clinician is terminated the USR CLASS MEMBERSHIP expiration field is 
      automatically entered with the termination date and time.  This patch will 
      correct the auto termination routine (USRLM) from including the termination 
      time when a clinician is terminated.
       
      The process of correcting the global will be done with a utility (USRFIX) 
      
    • 14 SEQ #14
      DATE APPLIED:   2000-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects a potential problem of a bad cross reference in the 
      will display the cross reference being deleted and also a count.
      
      A description of this build can be found on the NATIONAL PATCH MODULE UNDER 
      USR*1.0*14.
      ^USR(8930.3) global.  The patch will change routine USRUMMBR to not abort 
      with a undefined variable USRCHNG when a bad 0 node pointer is discovered.  
      Instead of the routine aborting it will send a email message to the user 
      DUZ reflecting the bad pointer.  The message will require forwarding to 
      a IRM representative at that site to review the USR(8930.3) global.
      
      Also provided with this patch will be a Post-Install routine that will scan 
      the global and delete any bad AUC or ACU cross references.  The Post-Install 
      
    • 16 SEQ #15
      DATE APPLIED:   2000-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      
      A description of this build can be found on the NATIONAL PATCH MODULE UNDER 
      USR*1.0*16.
      
    • 17 SEQ #16
      DATE APPLIED:   2000-11-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A description of this build can be found on the NATIONAL PATCH MODULE UNDER 
      USR*1.0*17.
      
    • 18 SEQ #17
      DATE APPLIED:   2001-03-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A description of this build can be found on the NATIONAL PATCH MODULE under 
      USR*1.0*18.
      
    • 15
      DATE APPLIED:   2001-04-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      For the description of this build see patch USR*1*15 in the National Patch
      Module.
      
    • 20 SEQ #19
      DATE APPLIED:   2001-08-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A description of this build can be found on the NATIONAL PATCH MODULE under 
      USR*1.0*20.
      
    • 2
      DATE APPLIED:   1998-04-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 2, USR*1.0*2. This patch prevents "terminated" users from
      being selected for class membership. See the National Patch module for
      a complete description.
      
    • 21 SEQ #20
      DATE APPLIED:   2001-09-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A description of this build can be found on the NATIONAL PATCH MODULE under 
      USR*1.0*21.
      
    • 22 SEQ #21
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A description of this build can be found on the NATIONAL PATCH MODULE under 
      USR*1.0*22.
      
    • 19
      DATE APPLIED:   2002-06-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A description of this build can be found on the NATIONAL PATCH MODULE UNDER 
      USR*1*19.
      
    • 23
      DATE APPLIED:   2003-09-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under patch USR*1*23.
      
    • 24
      DATE APPLIED:   2003-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under patch USR*1*24.
      
    • 25 SEQ #26
      DATE APPLIED:   2005-01-18 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this patch may be found under the National Patch Module 
      under USR*1.0*25.
      
    • 27
      DATE APPLIED:   2006-05-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description for this build can be found in the National Patch Module 
      under USR*1*27.
      
    • 30
      DATE APPLIED:   2006-12-27 14:45:55
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See patch USR*1*30 in the National Patch Module.
      
    • 28 SEQ #29
      DATE APPLIED:   2007-06-27 22:17:56
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects three issues with MEMBERHSIP by USER and USER CLASS.
      In "List Membership by Class" only the Expired
      Member listed, not the Active Member.
       
       
      Issue #1-- When looking at Manage Business Rules you will notice 
      when you hit "Add Rule" selection, notice the system defaults to 
      a TIU Object / TITLE when nothing was selected.
       
      Issue #2-- In "List Membership by User"  the dates are 
      list from most current to oldest.
      
    • 29 SEQ #31
      DATE APPLIED:   2009-04-23 13:49:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      his patch prevents incomplete business rules and duplicate business rules
      generated when the search string already matches a member in that class.
      from being created.  It also corrects the document hierarchy issue that
      allowed user access to a note due to a rule at a higher level.  This patch
      includes updates to FileMan fields STATUS (#.02) and ACTION (#.03) in
      AUTHORIZATION/SUBSCRIPTION file (#8930.1) to now require these fields when
      creating rules.  It also includes an updated INPUT TEMPLATE for USR
      AUTHORIZATION/SUBSCRIPTION (#8930.1) to perform requirement matching on
      fields USER CLASS (#.04), AND FLAG (#.05), and USER ROLE (#.06).  The 
      patch prevents the error "Already a member of this class" from being 
      
    • 3
      DATE APPLIED:   1998-06-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 3, USR*1.0*3. This patch removes TIU dependencies from ASU.
      See the National Patch module for a complete description.
      
    • 33
      DATE APPLIED:   2010-06-02 10:46:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this build can be found under patch USR*1*33 in the 
      National Patch Module.
      
    • 37
      DATE APPLIED:   2016-04-07 16:02:29
      APPLIED BY:   USER,FIFTYFOUR
    • 39 SEQ #36
      DATE APPLIED:   2019-10-24 12:16:10
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      PLEASE REFER TO THE PATCH DESCRIPTION FOR USR*1.0*39 FOR DETAILS.
      
    • 4
      DATE APPLIED:   1998-06-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 4, USR*1.0*4. This patch adds options that allow examination
      of class memberships without editing capabilites. See the National
      Patch module for a complete description.
      
    • 5
      DATE APPLIED:   1998-06-25 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 5, USR*1.0*5. This patch eliminates multiple prompting for
      User Classes with that have multiple matches.
      
    • 6
      DATE APPLIED:   1998-08-31 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 6, USR*1.0*6. This patch changes the display of user class
      membership so that all instances of class membership will be displayed.
      See the National Patch Module for a complete description.
      
    • 7
      DATE APPLIED:   1998-09-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 7, USR*1.0*7. This patch changes expanding/collapsing of
      class trees. See the National Patch Module for a complete description.
      
    • 8
      DATE APPLIED:   1998-10-07 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 8, USR*1.0*8. This patch allows for two users to have the same
      name. See the National Patch Module for a complete description.
      
    • 9
      DATE APPLIED:   1998-10-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ASU patch 9, USR*1.0*9. This patch changes the display name from the
      SIGNATURE NAME PRINTED BLOCK to the .01 field of file 200. See the
      National Patch Module for a complete description.
      
    DATE INSTALLED AT THIS SITE:   1997-10-06 00:00:00
    INSTALLED BY:   USER,ONE
    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.
     
    Features
     
    + 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