| DESCRIPTION OF ENHANCEMENTS |
This patch provides several reporting options for Alerts, including
This patch adds the following options:
List of Test Sites
==================
ANN ARBOR, MI
CLEVELAND, OH
DAYTON, OH
DUBLIN, GA
DURHAM, NC
FARGO, ND
LEXINGTON, KY
LITTLE ROCK, AR (C)
MARYLAND HCS
NEW JERSEY HCS
NORTH CHICAGO, IL
NORTHERN CALIFORNIA HCS
PALO ALTO HCS
PHILADELPHIA, PA
PHOENIX, AZ
SAN FRANCISCO, CA
Report Menu for Alerts (XQAL REPORTS MENU)
Routine Summary:
================
The following routines are included in this patch. The second
line of each of these routines now looks like:
<tab>;;8.0;KERNEL;**[patch list]**;Jul 10, 1995
Checksums:
==========
Checksums obtained using CHECK^XTSUMBLD
Rtn Nm Chksum Before Chksum After Patch List
------ ------------- ------------ ----------
XQARPRT1 N/A 33282029 **316**
XQARPRT2 N/A 33312830 **316**
List of preceding patches: none
This menu provides several options for generating reports on alerts for
Blood Bank Team Coordination:
=============================
Clearance - Approved 8/21/2003
Installation Instructions:
1. Users ARE allowed to be on the system during the
installation.
users or patients.
2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.
This option will load the KIDS (Kernel Installation and Distribution
System) package onto your system.
3. You DO NOT need to stop TaskMan or the background filers.
4. The patch has now been loaded into a transport global on your
system. On the KIDS menu, select the 'Installation' menu and use
the following options:
Verify Checksums in Transport Global
Print Transport Global
Compare Transport Global to Current System
Backup a Transport Global
Return to Programmers Prompt and use "D ^XPDKRN":
Select KIDS OPTION: Install
=======
Install Package(s)
Select INSTALL NAME: XU*8.0*316
==========
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//
NO
==
Want KIDS to INHIBIT LOGONs during the install? YES// NO
==
Want to DISABLE Scheduled Options, Menu Options, and Protocols?
YES// NO
==
User Alerts Count Report (XQAL USER ALERTS COUNT)
5. AXP Sites - Answer 'NO' to the question 'Want to MOVE
routines to other CPUs?'.
ones that: list users with large number of alerts in the ALERTS file
This option is used to generate a report on users who have more than a
specified number of alerts in the ALERTS file (#8992). The report covers
a specified range of dates, and can be sorted by user name, number of
alerts, or by service/section. In addition, the report in each of these
formats may be generated by Divisions if desired.
For each user who has the specified number of alerts or more, the report
includes the user name, the section/service for the user, the number of
alerts in the ALERTS file, the last sign-on date, the number of Critical
alerts or Abnormal Imaging alerts, and the date of the oldest alert.
(#8992); list alerts for a specified user from a specified date; list
The counting of alerts may also be restricted to those alerts which contain
specific text or phrases.
Critical Alerts Count Report (XQAL CRITICAL ALERT COUNT)
This option is used to generate a report of users who have more than a
specified number of alerts containing the word 'critical' or the words
'abnormal imaging' between the specified start and end dates. The report
alerts for a specified patient for a specified day or date range.
is presented in descending order for the number of critical/abnormal
imaging alerts present.
For each user who has the specified number of critical/abnormal
imaging alerts or more, the report includes the user name, the
section/service for the user, the number of alerts in the ALERTS file, the
last sign-on date, the number of Critical alerts or Abnormal Imaging
alerts, and the date of the oldest alert.
Since the retention period for alerts in the ALERT TRACKING file
List Alerts for a user from a specified date (XQAL ALERT LIST FROM DATE)
This option is used to obtain a list of alerts from the ALERT TRACKING
file (#8992.1) for a specified user for a specified date range. The user
may select all of the alerts to be displayed, or enter specific text or
phrases to select only alerts which contain the specified text. In the
latter case, the user may also select to see only those alerts which match
the criteria and are only info only alerts, only action alerts, or both.
The listing includes the internal entry number for the alert in the ALERT
(#8992.1) is currently a site parameter, some users may have alerts
TRACKING file, the date and time the alert was generated, the message
text of the alert, and information about any option or routine to be
executed for processing the alert.
Patient Alert List for specified date (XQAL PATIENT ALERT LIST)
This option is used to obtain a list of alerts for a specified patient
from the ALERT TRACKING file (#8992.1) for a selected date range (it is
recommended that this range be only a few days at most, since every entry
in the ALERTS file that no longer are present in the ALERT TRACKING file,
in the ALERT TRACKING file in the selected date range must be checked to
provide a complete listing of alerts for a patient).
A prompt is provided to obtain a quick scan listing of dates with at least
some alerts for the patient on it based on OR and DVB alerts (other
patient related alerts need to be identified by looking at each alert's
message text and are included in the full list, but not the quick scan).
The user may select all of the alerts to be displayed, or enter specific
text or phrases to select only alerts which contain the specified text.
data from both sources is used when necessary.
In the latter case, the user may also select to see only those alerts
which match the criteria and are info only alerts, only action alerts,
or both.
The listing includes the internal entry number for the alert in the ALERT
TRACKING file, the date and time the alert was generated, the message
text of the alert, and information about any option or routine to be
executed for processing the alert.
View data for Alert Tracking file entry (XQAL VIEW ALERT TRACKING ENTRY)
This option can be used to obtain a listing of data in captioned format for
selected entries in the ALERT TRACKING file (#8992.1). The internal entry
numbers for the entries to be listed must be entered individually.
There were no NOIS or E3Rs related to this patch.
|
