PATIENT REPRESENTATIVE (134)    PACKAGE (9.4)

Name Value
NAME PATIENT REPRESENTATIVE
PREFIX QAC
DEVELOPER (PERSON/SITE) CATHY WILLIAMSON/HISC
*LOWEST FILE NUMBER 745
*HIGHEST FILE NUMBER 745.49
DEVELOPMENT ISC HISC
CLASS National
CURRENT VERSION 2.0
SHORT DESCRIPTION PATIENT REPRESENTATIVE PACKAGE
VERSION
  • 2.0
    DATE DISTRIBUTED:   2005-11-19 00:00:00
    PATCH APPLICATION HISTORY:
    • 1
      DATE APPLIED:   1996-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See Description in NPM.
      
    • 12 SEQ #10
      DATE APPLIED:   1999-10-03 00:00:00
      APPLIED BY:   USER,ONE
    • 4
      DATE APPLIED:   2000-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch does a rollup of data from local sites into a mailmessage,
      and sends it to the national database.
      
    • 14 SEQ #12
      DATE APPLIED:   2000-10-12 00:00:00
      APPLIED BY:   USER,ONE
    • 13 SEQ #13
      DATE APPLIED:   2000-11-06 00:00:00
      APPLIED BY:   USER,ONE
    • 15 SEQ #14
      DATE APPLIED:   2001-01-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch creates an option that can be used to transmit data from
      one month to the national database.  The name of the option is Manual
      Rollup.
      
    • 16 SEQ #15
      DATE APPLIED:   2001-07-10 00:00:00
      APPLIED BY:   USER,ONE
    • 17 SEQ #16
      DATE APPLIED:   2002-06-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is an enhancement project that will make major changes to the 
      same way in existing reports.  Each has a suffix of Non-CSS to 
      distinguish it from the original ten Customer Service Standards.  The 
      Customer Service Standard field in the CONTACT ISSUE CODE file (#745.2) 
      has been populated and is being exported with the patch.
       
      This patch changes the input transform of the Division field (#37) of the 
      CONSUMER CONTACT file (#745.1).  Currently, only integrated sites 
      received a prompt for Division, and the choices were limited to those 
      Medical Centers making up the integrate group.  Now, all sites will get 
      the prompt and choices are amongst those MEDICAL CENTER DIVISION file 
      CONTACT ISSUE CODE file (#745.2).  Existing codes will be inactivated, 
      (#40.8) entries which point to the INSTITUTION file (#4).  The Division 
      field remains a pointer to the INSTITUTION file (#4).
       
      A new field, Internal Appeal (#43) has been added to the CONSUMER CONTACT 
      file (#745.1).  This field will store whether or not a Report of Contact 
      will go through the Internal Appeal process.  The Ad Hoc Report has been 
      updated to include this new field.  Internal Appeal will take the place 
      of the Refer to SEAT field.
       
      The user will no longer be prompted for the Level of Satisfaction field 
      and new codes will be exported, resulting in a smaller list of active 
      (#36 of the CONSUMER CONTACT file (#745.1)).
       
      The second problem was that the division field pointed to the INSTITUTION
      file (#4) and only legacy sites were to be available as choices.  With
      this patch any entry in the site's MEDICAL CENTER DIVISION file (#40.8)
      that points to the INSTITUTION file will be available. Both integrated and
      non-integrated sites will be able to enter the division. 
       
      This patch will also correct two problems with the Patient Representative
      Roll-up.  
      codes.  Only these nationally exported codes will be in use.
       
      The first problem dealt with the fact that once a record was transmitted,
      it would be evaluated for re-transmission only when it was closed.  Also,
      the roll-up did not take into account the fact that records can be
      re-opened and edited after closing.  Any record that was re-opened was not
      being evaluated for re-transmission.  With this patch any record edited
      will be evaluated for transmission regardless of whether or not it was
      previously transmitted, independent of record status.
       
      This patch will export seven new entires in the CUSTOME SERVICE STANDARD  
      file (#745.6).  These codes will be added in order to bring the Customer 
      Service Standards field better match the Customer Satisfaction survey.  
      These codes are not Customer Service Standards, but can be tracked in the 
      
    • 18 SEQ #17
      DATE APPLIED:   2002-09-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A problem was discovered with the Service/Discipline Issue Totals [QAC 
      SERV/DISC ISSUE TOT] report - it would not report results when just one 
      Division was selected.  The same code is used for the Discipline Issue 
      Totals [QAC DISC ISSUE TOT] report, and the fix made with this patch 
      addresses both reports.
      
    • 20 SEQ #18
      DATE APPLIED:   2007-06-27 23:17:10
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Sites are seeing Contact Numbers that do not follow the
      proper format. The sites are not able to enter new contact
      numbers because of the incorrect contact numbers.
      This patch will correct the bad contact numbers when the
      post install routine is run.
      
    • 19 SEQ #19
      DATE APPLIED:   2007-09-05 00:14:34
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch contains the VistA objects to run PATS (Patient Advocate
      Tracking System), the application that replaces the legacy Patient
      Representative system.
       
      It includes both objects used to retrieve VistA data while the PATS
      application is running, and objects used to migrate the legacy data from
      the FileMan files to the new PATS Oracle tables on a central server.
      
    • 3 SEQ #2
      DATE APPLIED:   1997-10-06 00:00:00
      APPLIED BY:   USER,ONE
    • 21 SEQ #20
      DATE APPLIED:   2007-12-12 22:37:34
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Associated patches: (v)QAC*2*19    <<= must be installed BEFORE 
      The Patient Advocate Tracking System (PATS) has two remote procedure calls
      option will load the KIDS package onto your system.
       
       2. The patch has now been loaded into a Transport global on your system. 
      From the KIDS menu, you can use the following options:
       
              Verify Checksums in Transport Global (optional)
              Print Transport Global (optional)
              Compare Transport Global to Current System (optional)
              Backup a Transport Global (optional)
       
      (RPC) that return data from the NEW PERSON file. The RPC names are QACV
       5. From the KIDS menu, under the 'Installation' menu, use the following
      option to install the patch:
       
        Install Package(s) QAC*2.0*21
        .
        .
        .
        Want KIDS to INHIBIT LOGONs during the install? YES// NO
       
        Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
      KEY HOLDERS VLH and QACV PERSON LOOKUP VLH. Both RPCs execute the same
       
       
      DOCUMENTATION:
      ================= 
      Documents for the PATS system can be obtained by using FTP from the
      appropriate Customer Service directory:
        
          OI FIELD OFFICE    FTP ADDRESS    DIRECTORY
          ===============    ===========    ==================
                             download.vista.domain.ext
      code in routine QACVEMPX. The RPCs return NAME, TITLE and MAIL CODE for
          Albany                            ftp.fo-albany.domain.ext
          Hines                             ftp.fo-hines.domain.ext 
          Salt Lake City                    ftp.fo-slc.domain.ext
        
       Document can also be downloaded from the VistA Documentation Library
      (VDL) Web page:
        
          <http://www.domain.ext/vdl/section.asp?secid=4>
       
       
      selected employees.
       ROUTINE SUMMARY - CHECK^XTSUMBLD results
       ========================================
       The second line of the routines will look like:
        
       ;;2.0;Patient Representative;**19,21**;07/25/1995
        
       Routine Name    Before Patch    After Patch     Patch list
       ==========      =========       ========        =======
       QACVEMPX        6135557         9113636         **19,21**
       
       
       
      Routine Information:
      ====================
       
       
      The second line of each of these routines now looks like:
       ;;2.0;Patient Representative;**[Patch List]**;07/25/1995;Build 4
       
      The checksums below are new checksums, and
       can be checked with CHECK1^XTSUMBLD.
      Problem #1
       
      Routine Name: QACVEMPX
          Before: B18632980   After: B39562803  **19,21**
       
      Routine list of preceding patches: 19
      ----------
      Currently, if the TITLE or MAIL CODE contain an ampersand character (&), 
      the PATS java code interprets this as a reserved xml character and fails.
      `QAC*2*21'
      This is experienced in 4 places in PATS.
       
      1. Adding a New Report of Contact (ROC), Cover Sheet tab, the system
      should display a drop-down list of Information Takers. Without the patch,
      the drop-down list of Info Takers is not present.
       
      2. Edit a ROC, search by Information Taker option, should display a 
      drop-down list of Information Takers. Without the patch, the drop-down
      list of Info Takers is not present.
       
                          
      3. Edit a ROC, Resolution tab, adding a new Issue Code, when user tries to
      look up an Employee Involved. Without the patch, the users receive the 
      error: "A problem was encountered while attempting to communicate with 
      VistA. This problem appears to be related with VistALink. Try again. If
      this problem persists contact the support desk for further assistance."
       
      4. Edit a ROC, Notification tab, when user tries to look up an Employee 
      to send a notification. Without the patch, the users receive the 
      error: "A problem was encountered while attempting to communicate with 
      VistA. This problem appears to be related with VistALink. Try again. If
      Subject:  Employee Lookup Bugs in PATS
      this problem persists contact the support desk for further assistance."
       
      The fix is to use the Kernel routine $$SYMENC^MXMLUTL in routine QACVEMPX
      to replace reserved xml symbols in the TITLE and MAIL CODE output with
      their coded values.
       
      Problem #2
      ----------
      The NEW PERSON file may contain last names standardized under an old 
      format that removed all punctuation except for hyphens, and last names 
       
      standardized under a newer format that also leaves spaces and apostrophes 
      in the last name. Thus you may find names like O'BRIEN as well as OBRIEN.
       
      When a user enters O'Brien as a lookup value, PATS was only using the old 
      name standardization, so was only finding matches to the last name 
      OBRIEN, but was not finding O'BRIEN.
       
      This occurs in two different places in PATS.
       
      1. Edit a ROC, Resolution tab, adding a new Issue Code, when user tries to
      Category:  ROUTINE
      look up an Employee Involved.
       
      2. Edit a ROC, Notification tab, when user tries to look up an Employee 
      to send a notification.
       
      After the patch is installed, if a user enters a last name containing
      either an apostrophe or a space, PATS will look for matches to the name
      both with and without the apostrophe or space. Thus, if a user enters
      O'Brien, PATS will find names matching both O'BRIEN and OBRIEN, if there
      are any.
       
       
      ASSOCIATED NOIS:
       ===============
       Remedy: HD0000000200638
       Remedy: HD0000000202881
       Remedy: HD0000000204329
       Remedy: HD0000000207038
       Remedy: HD0000000207041
        
       ASSOCIATED E3R:
      Description:
       ==============
       n/a
        
       TEST SITES:
       ===========
      PORTLAND (OR) VAMC  -  648
      PHOENIX VAMC        -  644
      LONG BEACH,CA VAMC  -  600
      CHEYENNE VAMC       -  442
      UPSTATE NEW YORK HCS-  528
      ===========
      CENTRAL TEXAS HCS   -  674
       
        
       INSTALLATION INSTRUCTIONS:
       ==========================
       >>> Users may remain on the system
       >>> TaskMan does NOT need to be stopped
       >>> Time to install patch is less than 2 minutes
       
       1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This 
      
    • 5 SEQ #3
      DATE APPLIED:   1998-03-18 00:00:00
      APPLIED BY:   USER,ONE
    • 7 SEQ #4
      DATE APPLIED:   1998-08-31 00:00:00
      APPLIED BY:   USER,ONE
    • 6 SEQ #5
      DATE APPLIED:   1998-09-24 00:00:00
      APPLIED BY:   USER,ONE
    • 8 SEQ #6
      DATE APPLIED:   1999-01-19 00:00:00
      APPLIED BY:   USER,ONE
    • 10 SEQ #7
      DATE APPLIED:   1999-03-29 00:00:00
      APPLIED BY:   USER,ONE
    • 11 SEQ #8
      DATE APPLIED:   1999-06-02 00:00:00
      APPLIED BY:   USER,ONE
    • 9 SEQ #9
      DATE APPLIED:   1999-06-22 00:00:00
      APPLIED BY:   USER,ONE
    DATE INSTALLED AT THIS SITE:   1996-09-24 00:00:00
DESCRIPTION
This package supports the work of the Patient Representative by
collecting data on patient and non-patient contacts.
FILE
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
ENVIRONMENT CHECK ROUTINE QACIPRE0
ENVIRONMENT CHECK DONE DATE 1996-09-24 16:41:18
POST-INITIALIZATION ROUTINE QACIPOST
POST-INIT COMPLETION DATE 1996-09-24 16:42:04