{"aaData": [["EVENT MONITOR", "
ACTIVE
\n", "
Monitors the Event Monitor
\n", "
480
\n", "", "
YES
\n", "
\nThis monitor monitors the Event Monitor system!  In other words, it\nmonitors itself.\n
\n
\n", "", "", "", "
MOTHER~HLEVX001
\n", ""], ["PURGE EVENT LOG", "
ACTIVE
\n", "
Purges records from file 776.4
\n", "
1440
\n", "", "
NO
\n", "", "", "", "", "
PURGE~HLEMEP
\n", ""], ["SEND EVENTS", "
ACTIVE
\n", "
distributes events to remote locations
\n", "
30
\n", "
\nThis distributes local events to remote locations.  Whether or not an event\nis sent is determined by the type of event and a screen the application developer\ncan set up.\n
\n
\n", "
NO
\n", "", "", "", "", "
SENDALL~HLEMSND
\n", ""], ["LINK (870) CHECKS", "
INACTIVE
\n", "
File 870 entry w/stub status search
\n", "
720
\n", "
\nM code logic flow for this routine is:\n \n - Loops through file 870 storing in ^XTMP all stub entries.\n \n - Loops through file 870 again, after requeue-minutes, searching\n   for all stub entries.  Compares to previous record of stub\n   entries.  If a stub entry still remains from last loop, a\n   notification message is sent off-station to the VistA HL7\n   team.\n
\n
\n", "
YES
\n", "
\nThis event monitor search the IN QUEUE and the OUT QUEUE of the HL \nLogical Link file (#870) for entries that are stuck in the STUB status.\n
\n
\n", "", "", "
\n
\n\n
\n", "
CHK870~HLEVX000
\n", ""], ["CHECK 773 AC XREF", "
ACTIVE
\n", "
Check file 773 AC xref
\n", "
1440
\n", "", "
YES
\n", "", "", "", "
\n
\n\n
\n", "
CHECKAC~HLEVX002
\n", ""], ["FAST HL7 PURGE #1", "
ACTIVE
\n", "
This is the main Fast Purge Job.
\n", "
60
\n", "
\nThis job utilized the AI cross-reference to purge records in file 772 and 773\npurpose is to prevent purging from getting backed up when the messaging system\nis under very heavy load.\nwith maximum efficiency. It is not guaranted to purge all records that need\npurging, but should quickly purge the vast majority of such records.  Its\nmain limitation is that it limits itself to messages that have a status of\nSuccessfully Completed.\n\nThere are two Fast Purge jobs. This one is the main job, in that it should be\nrunning nearly continuously.  The second job will be started less frequently,\nand if there is no work to do will go back to sleep for several hours.  Its\n
\n
\n", "
NO
\n", "", "", "", "", "
FAST1~HLUOPTF2
\n", ""], ["FAST HL7 PURGE #2", "
ACTIVE
\n", "
Fast Purge for overload situations.
\n", "
180
\n", "
\nThis job utilized the AI cross-reference to purge records in file 772 and 773\nbacked up when the messaging system is under very heavy load.\n\nThe other Fast Purge Job will run nearly continuously, and should be able to\nkeep up with the purging under all but the most severe workloads.\nwith maximum efficiency. It is not guaranted to purge all records that need\npurging, but should quickly purge the vast majority of such records.  Its\nmain limitation is that it limits itself to messages that have a status of\nSuccessfully Completed.\n\nThere are two Fast Purge jobs.  This one is the        backup job, in that it\nwill be started less frequently, and if there is no work to do will go back to\nsleep for several hours.  Its purpose is to prevent purging from getting\n
\n
\n", "
NO
\n", "", "", "", "", "
FAST2~HLUOPTF2
\n", ""]]}