DavidWhitten at 19:09, 20 September 2019

2019-09-20T19:09:15Z

← Older revision		Revision as of 19:09, 20 September 2019
Line 280:		Line 280:

	</pre>		</pre>

			VA Document (on this wiki) : [[File:Hl71 6p109sp.doc]]

DavidWhitten at 19:05, 20 September 2019

2019-09-20T19:05:05Z

@@ Line 211: / Line 211: @@
 PURGE EVENT LOG                 ACTIVE        1440  PURGE~HLEMEP
 SEND EVENTS                     ACTIVE          30  SENDALL~HLEMSND
 So this apparently these tools let us track possible problems with HL7 messaging.
 The question I have to ask is why they seem to explode our journal space when
 we first start up the non-production environment.
 Does any know if we should be checking these reports regularly ?
 Are problems common or uncommon?
 Thanks for your input.
@@ Line 224: / Line 269: @@
 -870-3834
-PS: I put this e-mails data at http://www.vistapedia.com/index.php/HL7_Event_Monitor/Journal_Growth
+PS: I put this e-mails data at
-and did find a document which may be relevant:
+http://www.vistapedia.com/index.php/HL7_Event_Monitor/Journal_Growth
 Event Monitor Development Guide (HL7 Patch 106) - VA.gov
 </pre>

DavidWhitten at 18:51, 20 September 2019

2019-09-20T18:51:34Z

← Older revision		Revision as of 18:51, 20 September 2019
Line 224:		Line 224:
	713-870-3834		713-870-3834

	PS: I put this e-mails data at		PS: I put this e-mails data at http://www.vistapedia.com/index.php/HL7_Event_Monitor/Journal_Growth

	and did find a document which may be relevant:		and did find a document which may be relevant:

	Event Monitor Development Guide (HL7 Patch 106) - VA.gov		Event Monitor Development Guide (HL7 Patch 106) - VA.gov

	</pre>		</pre>

DavidWhitten: Created page with "Up: HL7_Event_Monitor

 Email of 20-Sep-2019 by David Whitten to Hardhats  Does anyone know about the ^XTMP global and the series of nodes apparently created by HL7 ?..."

2019-09-20T18:50:07Z

Created page with "Up: HL7_Event_Monitor <pre> Email of 20-Sep-2019 by David Whitten to Hardhats Does anyone know about the ^XTMP global and the series of nodes apparently created by HL7 ?..."

New page

Up: [[HL7_Event_Monitor]]
<pre>
Email of 20-Sep-2019 by David Whitten to Hardhats

Does anyone know about the ^XTMP global and the series of nodes apparently created by HL7 ?

ie: there are nodes in the ^XTMP() global with a first subscript of either: "HLEV CHK773AC "_<Timson Date+Time> or
"HLEV STUB "_<Timson Date+Time>

Apparently "HLEV" means Health Level Seven Event Monitoring.
The nodes seem to get SET in the HLEVX* routines. The dates on these routines are in February 2004 or so.
Notably the HLEV CHK773AC nodes are set in the routine ^HLEVX002

Soon after we copy our Production environment to make a test or training or development environment, there is something
that runs and fills up a LOT of journal files. This seems to be run as a background task since the Journal files have a
process id that has %ZTMS1 running if it finishes before we notice.

The sub-routine LIST^HLEVX lists these "monitors"

LIST N I,T W @IOF,$$CJ^XLFSTR("Official VistA HL7 Event Monitor Code",IOM),!,$$
;;
;;The "monitors" that are officially included in the VistA HL7 package are
;;listed below.
;;
;;Routine Monitor-Name
;;============================================================================
;;SYSTEM^HLEVX001^EVENT MONITOR
;;CHK870^HLEVX000^STUB 870 SEARCH & MORE
;;CHKXREF^HLEVX002^XREF CHECK - FILE 772 & 773
Q

I searched the OPTION File#19 for menus related to Monitoring and found these options:

Select OPTION: SEARCH FILE ENTRIES

OUTPUT FROM WHAT FILE: TASKS// 19 OPTION (10367 entries)

-A- SEARCH FOR OPTION FIELD: ROUTINE
-A- CONDITION: [ CONTAINS
-A- CONTAINS: HLEV

-B- SEARCH FOR OPTION FIELD:

IF: A// ROUTINE CONTAINS (case-insensitive) "HLEV"

STORE RESULTS OF SEARCH IN TEMPLATE:

SORT BY: NAME//
START WITH NAME: FIRST//
FIRST PRINT FIELD: [CAPTIONED

Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number
(IEN)
Heading (S/C): OPTION SEARCH//
DEVICE: TELNET
OPTION SEARCH SEP 20,2019 14:27 PAGE 1
--------------------------------------------------------------------------------

NUMBER: 9978 NAME: HLEV EDIT MASTER
MENU TEXT: Edit parameters TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: E7769^HLEVSTUP
UPPERCASE MENU TEXT: EDIT PARAMETERS

NUMBER: 9979 NAME: HLEV EDIT MASTER ON-OFF
MENU TEXT: Turn on/off monitoring TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: ONOFFPAR^HLEVAPI0
UPPERCASE MENU TEXT: TURN ON/OFF MONITORING

NUMBER: 9976 NAME: HLEV EDIT MONITOR
MENU TEXT: Enter/edit event monitors TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: E7761^HLEVSTUP
UPPERCASE MENU TEXT: ENTER/EDIT EVENT MONITORS

NUMBER: 9977 NAME: HLEV EDIT MONITOR ON-OFF
MENU TEXT: Turn on/off event monitor TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: ONOFFEV^HLEVAPI0
UPPERCASE MENU TEXT: TURN ON/OFF EVENT MONITOR

NUMBER: 9991 NAME: HLEV GRANT REMOTE LICENSE
MENU TEXT: Grant remote request license
TYPE: run routine CREATOR: WVEHR,PATCH INSTALLER
PACKAGE: HEALTH LEVEL SEVEN ROUTINE: OPENMAIL^HLEVSRV3
UPPERCASE MENU TEXT: GRANT REMOTE REQUEST LICENSE

NUMBER: 9986 NAME: HLEV MASTER JOB NOW
MENU TEXT: Run monitor master job now
TYPE: run routine CREATOR: WVEHR,PATCH INSTALLER
PACKAGE: HEALTH LEVEL SEVEN ROUTINE: MSTNOW^HLEVMST0
UPPERCASE MENU TEXT: RUN MONITOR MASTER JOB NOW

NUMBER: 9981 NAME: HLEV MASTER JOB START
MENU TEXT: Monitoring master job start
TYPE: run routine CREATOR: WVEHR,PATCH INSTALLER
PACKAGE: HEALTH LEVEL SEVEN ROUTINE: STARTMST^HLEVMST0
UPPERCASE MENU TEXT: MONITORING MASTER JOB START

NUMBER: 9982 NAME: HLEV MASTER JOB STOP
MENU TEXT: Stop monitoring master job
TYPE: run routine CREATOR: WVEHR,PATCH INSTALLER
PACKAGE: HEALTH LEVEL SEVEN ROUTINE: UNQUEUE^HLEVMST0
UPPERCASE MENU TEXT: STOP MONITORING MASTER JOB

NUMBER: 9984 NAME: HLEV MONITOR DETAILS
MENU TEXT: Results of a monitor run TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER PACKAGE: HEALTH LEVEL SEVEN
ROUTINE: CTRL^HLEVREP2
UPPERCASE MENU TEXT: RESULTS OF A MONITOR RUN

NUMBER: 9983 NAME: HLEV MONITOR MAP REPORT
MENU TEXT: Map of monitoring activity
TYPE: run routine CREATOR: WVEHR,PATCH INSTALLER
PACKAGE: HEALTH LEVEL SEVEN ROUTINE: CTRL^HLEVREP1
UPPERCASE MENU TEXT: MAP OF MONITORING ACTIVITY

NUMBER: 9980 NAME: HLEV ONE-TIME MONITOR RUN
MENU TEXT: One-time monitor run TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER PACKAGE: HEALTH LEVEL SEVEN
ROUTINE: ONETIME^HLEVAPI1
UPPERCASE MENU TEXT: ONE-TIME MONITOR RUN

NUMBER: 9973 NAME: HLEV PRINT MASTER SETUP
MENU TEXT: Settings of monitoring parameters
TYPE: run routine CREATOR: WVEHR,PATCH INSTALLER
ROUTINE: VIEW7769^HLEVREP(1)
UPPERCASE MENU TEXT: SETTINGS OF MONITORING PARAMET

NUMBER: 9972 NAME: HLEV PRINT MONITOR SETUP
MENU TEXT: Monitor setup details TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: SHOW7761^HLEVREP
UPPERCASE MENU TEXT: MONITOR SETUP DETAILS

NUMBER: 9989 NAME: HLEV REPORT CONDENSED MONITOR
MENU TEXT: Condensed monitor report TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: CONDMON^HLEVREP0
UPPERCASE MENU TEXT: CONDENSED MONITOR REPORT

NUMBER: 9988 NAME: HLEV REPORT MONITOR RECIPIENTS
MENU TEXT: Message recipients TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: RECIP^HLEVREP0
UPPERCASE MENU TEXT: MESSAGE RECIPIENTS

NUMBER: 9990 NAME: HLEV REPORT REMOTE REQUESTABLE
MENU TEXT: Remote requestable report TYPE: run routine
CREATOR: WVEHR,PATCH INSTALLER ROUTINE: REMREQO^HLEVREP3
UPPERCASE MENU TEXT: REMOTE REQUESTABLE REPORT

NUMBER: 9985 NAME: HLEV-INFORMATION-SERVER
MENU TEXT: Event monitoring server TYPE: server
CREATOR: DEWAYNE,ROBERT PACKAGE: HEALTH LEVEL SEVEN
ROUTINE: HLEVSRV SERVER BULLETIN: XQSERVER
SERVER ACTION: RUN IMMEDIATELY SERVER MAIL GROUP: HLEV SERVER
SERVER AUDIT: NO SUPRESS BULLETIN: YES, SUPRESS IT
SERVER REPLY: REPLY ON ERROR ONLY SAVE REQUEST: Do not save request
UPPERCASE MENU TEXT: EVENT MONITORING SERVER

17 MATCHES FOUND.

I ran the apparent top menu:

Select OPTION NAME: HLEV MENU MAIN Event monitoring menu
Master job not started. Not time yet...
-------- Master job status is ACTIVE --------
Last master job run was 9 min 51 sec ago...
Next run [task# 4556391] is 1 hr 50 min 9 sec in the future...
-------- Event monitoring status is ACTIVE --------

Setup & maintenance options ... [HLEV MENU SETUP]
Run-time options ... [HLEV MENU RUNTIME]

Select Event monitoring menu Option: Run-time options
Settings of monitoring parameters [HLEV PRINT MASTER SETUP]
Monitor setup details [HLEV PRINT MONITOR SETUP]
One-time monitor run [HLEV ONE-TIME MONITOR RUN]
Map of monitoring activity [HLEV MONITOR MAP REPORT]
Results of a monitor run [HLEV MONITOR DETAILS]
Run monitor master job now [HLEV MASTER JOB NOW]
Select Run-time options Option:

Select Event monitoring menu Option: SETup & maintenance options
Monitor setup & maintenance ... [HLEV MENU SETUP-MONITOR]
System setup & maintenance ... [HLEV MENU SETUP-MASTER]
Reports ... [HLEV MENU REPORTS]

Select Setup & maintenance options Option: REPOrts
Condensed monitor report [HLEV REPORT CONDENSED MONITOR]
Message recipients [HLEV REPORT MONITOR RECIPIENTS]
Remote requestable report [HLEV REPORT REMOTE REQUESTABLE]

Select Reports Option: CONDensed monitor report
Short Monitor Report

================================================================================

This option displays monitor information in brief format. If you wish to see
more of the information for this monitor, please use the 'Expanded monitor
report' menu option.
* Previous selection: NAME from A to ZZZ
START WITH NAME: A//
GO TO NAME: ZZZ//
DEVICE: 0;P-OTHER;79;1000 TELNET
Monitor report SEP 20,2019 14:32 PAGE 1
REQUE
NAME STATUS MIN M STARTUP
-------------------------------------------------------------------------------

CHECK 773 AC XREF ACTIVE 1440 CHECKAC~HLEVX002
EVENT MONITOR ACTIVE 480 MOTHER~HLEVX001
FAST HL7 PURGE #1 ACTIVE 60 FAST1~HLUOPTF2
FAST HL7 PURGE #2 ACTIVE 180 FAST2~HLUOPTF2
LINK (870) CHECKS ACTIVE 720 CHK870~HLEVX000
PURGE EVENT LOG ACTIVE 1440 PURGE~HLEMEP
SEND EVENTS ACTIVE 30 SENDALL~HLEMSND

So this apparently these tools let us track possible problems with HL7 messaging.
The question I have to ask is why they seem to explode our journal space when
we first start up the non-production environment.

Does any know if we should be checking these reports regularly ?
Are problems common or uncommon?

Thanks for your input.

Dave Whitten
713-870-3834

PS: I put this e-mails data at

and did find a document which may be relevant:
Event Monitor Development Guide (HL7 Patch 106) - VA.gov
</pre>

HL7 Event Monitor/Journal Growth - Revision history

DavidWhitten at 19:09, 20 September 2019

DavidWhitten at 19:05, 20 September 2019

DavidWhitten at 18:51, 20 September 2019

DavidWhitten: Created page with "Up: HL7_Event_Monitor
Email of 20-Sep-2019 by David Whitten to Hardhats Does anyone know about the ^XTMP global and the series of nodes apparently created by HL7 ?..."