|DESCRIPTION OF ENHANCEMENTS
Subject: Missing and undefined data
1. Users are allowed to be on the system during the installation.
2. It is not necessary to place TaskMan in a WAIT/STOP state.
3. When prompted 'Want to DISABLE Scheduled Options, Menu Options,
and Protocols? Yes// <return>, respond YES. When prompted
to select the option(s) you would like to place out of order,
enter the following:
4. Review your Mapped Routine set. If any of the routines listed in
the ROUTINE SUMMARY section are mapped on your system, they
should be unmapped at this time.
5. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This
option will load the KIDS package onto your system.
6. The patch has now been loaded into a Transport global on your
system. You now need to use KIDS to install the Transport global.
7. From the Kernel Installation and Distribution System Menu, select
the Installation menu. On the KIDS Installation menu, you may
elect to use the following options:
a. Verify checksums in the Transport Global - this option will
allow you to ensure the integrity of the routines that are in
the Transport Global.
b. Compare Transport Global to the Current System - this option
will allow you to view all changes that will be made when the
patch is installed. It compares all components of the patch
(routines, DDs, templates, etc.).
c. Backup a Transport Global - this option will create a backup
message of any routines exported with the patch. It will NOT
backup any other changes such as DDs or templates.
Use the Install Package(s) options and select the package:
8. If the routines were unmapped as part of step 4, they should be
returned to the mapped set once the installation has run to
Install patch AFJX*5.1*6 prior to the installation of this patch.
AFJXWCPL - An uncoordinated addition of a new cross-reference in Lab
Package resulted in an undefined at NXTST+2^AFJXWCPL. The code at
CHSET+7 was modified to exclude the handling of the new
AFJXPNHI - The variable I was reported to be undefined at
PART2^AFJXPNHI. This variable was used as a dummy index for a For
Loop and was not used elsewhere. The For Loop was changed to an
AFJXPNHI - The site was reporting that NHE reports were not being
found by the alerts mechanism. Investigation found two problems.
The first was that the parsing mechanism that parsed the titles in
the Alerts Message was using spaces in locating data. Since the
spaces were used the data after the patient name was mis-parsed if
there was a third item present in the name (such as Jr/Sr. a number,
etc). The code in AFJXPNHI was modified to use other characteristics
to allow a proper parsing.
The second is that if the patients name is spelled differently at
the server and client the Alerts will not display the messages since
a built in check (the two names are the same) fails. Since this is a
design feature a decision or how to handle this is still open
(Follow the completed reports model where this is available, or
extend the security to the complete report).
Milwaukee, Chillicothe, Danville
The following is a list of the routines included in this patch.
The second line value of each of these routines will look like:
<tab>;;5.1;Network Health Exchange;**[patch list]**;date
Routine Name Before Patch After Patch Patch List
============ ============ =========== ==========
AFJXEN7 N/A 6822968 7
AFJXPNHI 6813365 7299167 2,7
AFJXWCPL 7386440 7733101 7
* From CHECK^XTSUMBLD
To test if the transport has been corrupted, you can use the
"Verify Package Integrity" option. This option is under
Utilities under the KIDS menu. It will compare the checksums in
the build with the current checksums and list any that differ.
Environment Check Routine:
The routine AFJXEN7 checks to see if NHE version 5.1 with patch
6 is installed before installation proceeds. On failure, a
message is sent to the user detailing the problems encountered.
The routine AFJXEN7 may be removed upon successful patch 7
2 routines (AFJXPNHI, AFJXWCPL) are modified in this patch.
WHEN? Anytime. This patch is so brief (only two routines) that it
should not be queued.
HOW LONG? Installation will take less than 2 minutes.
Use the INSTALL/CHECK MESSAGE option on the PackMan and respond
YES at the prompt 'Want to Continue with load? YES// <return>.