| DESCRIPTION OF ENHANCEMENTS |
This patch provides two new features, "Don't Purge" and "Reprocessing"
1. Users are allowed to be on the system during the installation.
2. Check and make sure that the 'HL PURGE TRANSMISSIONS' option is not
scheduled during the time of installation.
3. Stop all the incoming filers.
4. AXP SITES: Review your mapped set. If any of the routines listed in
the Routine Summary section are mapped, they should be removed from
the mapped set 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
2. Clear the flag field "DON'T PURGE" (#772,15) to allow the message
system. You now need to use KIDS to install the Transport global.
On the KIDS menu, under the 'Installation' menu, use the following
options:
Verify Checksums in Transport Global
Print Transport Global
Compare Transport Global to Current System
Backup a Transport Global
Install Package(s)
INSTALL NAME: HL*1.6*33
to be purged by the "HL PURGE TRANSMISSIONS" option. Either of the
=========
Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,
and Protocols?'.
7. MSM Sites - Answer 'YES' to the question 'Want to MOVE routines to
other CPUs?'. Enter the names of your Compute and Print server(s).
8. AXP Sites: Rebuild your mapped set if necessary.
9. Restart all the incoming filers, which have been stopped in step #3.
10. Re-schedule 'HL PURGE TRANSMISSIONS' option if this option was
scheduled and has been stopped in step #2.
following two extrinsic functions may be used for this purpose:
$$TOPURG^HLCIRN or $$SETPURG^HLCIRN(0)
3. Reprocessing the message by calling the extrinsic function:
$$REPROC^HLCIRN(IEN,RTN)
where: IEN is the child message IEN (or the parent message IEN).
RTN is the routine to be Xecuted for reprocessing the
messages, which were requested by the CIRN project. The new extrinsic
message.
These extrinsic functions and their associated parameters, return values,
and results are described as follows:
$$DONTPURG^HLCIRN():
purpose: to set the "DON'T PURGE" field (#772,15).
input: none
return value: 1 means field has been successfully set
function calls allow the VISTA/DHCP applications to interface with HL7
-1 means call has failed; nothing has been changed
$$TOPURG^HLCIRN():
purpose: to clear the "DON'T PURGE" field (#772,15).
input: none
return value: 0 means field has been successfully cleared
-1 means call has failed; nothing has been changed
$$SETPURG^HLCIRN(STATUS):
purpose: either to set (STATUS=1) or to clear (STATUS=0) the
in the following ways:
"DON'T PURGE" field (#772,15).
input: STATUS=1 used to set the "DON'T PURGE" field.
STATUS=0 used to clear the "DON'T PURGE" field.
return value: 1 means field has been successfully set
0 means field has been successfully cleared
-1 means call has failed; nothing has been changed
$$REPROC^HLCIRN(IEN,RTN):
purpose: to reprocess message.
input: IEN= the child message IEN (or the parent message
IEN) of file #772.
RTN= routine, to be Xecuted for reprocessing the
message.
return value: 0 means call has been successfully completed
-1 means call has failed; nothing has been changed
The extrinsic functions, $$DONTPURG^HLCIRN(), $$TOPURG^HLCIRN(), and
$$SETPURG^HLCIRN(STATUS) should be called by one of the following
routines:
- RTN routine, which is provided to $$REPROC^HLCIRN(IEN,RTN).
1. Set the new flag field "DON'T PURGE" (#772,15) to prevent a message
- routine stored in field "GENERATE/PROCESS ROUTINE"(#101,771).
- routine stored in field "GENERATE/PROCESS ACK ROUTINE"(#101,772).
When called by these routines, HL7 assumes that the variables,
HLMTIENS(child message IEN of file #772) and HLMTIEN(parent message IEN of
file #772), are already properly defined. Otherwise, if they are called
elsewhere, at least the HLMTIEN should be defined in order to make them to
work. If only HLMTIEN is defined, then the call will only update the
entry of parent message. Of course, having only a defined HLMTIENS is
enough for HL7 to find the corresponding value for HLMTIEN, and
being purged by the "HL PURGE TRANSMISSIONS" option. Either of the
consequently HL7 will update entries for both child and parent massages.
The IEN, which is provided to $$REPROC^HLCIRN(IEN,RTN) should be the child
message IEN of file #772. This will make HL7 update the "STATUS" for both
child and parent message entries. If the IEN is the parent message IEN,
then only the "STATUS" of the parent message entry will be updated.
Routine Summary:
================
following two extrinsic functions may be used for this purpose:
The following is a list of the routines included in this patch. The
second line of each of these routines now looks like:
<tab>;;1.6;HEALTH LEVEL SEVEN;**[patch list]**;Oct 13, 1995
Checksums:
==========
Routine Name Checksum Before Checksum After Patch List
$$DONTPURG^HLCIRN or $$SETPURG^HLCIRN(1)
------------ --------------- -------------- ------------
HLCIRN N/A 4336697 33
HLTPCK1 4288888 4143076 8,33
HLUOPT1 9958836 9990663 10,13,21,33
From CHECK^XTSUMBLD
Installation Instructions:
==========================
|
