| DESCRIPTION OF ENHANCEMENTS |
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
|
