STANDARD DATA DICTIONARY #776.3 -- HL7 MONITOR EVENT TYPE FILE 3/24/25 PAGE 1
STORED IN ^HLEV(776.3, (44 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 1.6)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
DD ACCESS: @
RD ACCESS: @
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
IDENTIFIED BY: BRIEF DESCRIPTION (#4.01)
PRIMARY KEY: A (#38)
Uniqueness Index: C (#349)
File, Field: 1) CODE (776.3,.01) 2) PACKAGE NAME (776.3,.08)
POINTED TO BY: TYPE field (#.02) of the HL7 MONITOR EVENT File (#776.4)
EVENT TYPES field (#.01) of the EVENT TYPES sub-field (#776.52) of the HL7 MONITOR EVENTS PROFILE File (#776.5)
CROSS
REFERENCED BY: CODE(B)
INDEXED BY: PACKAGE & PACKAGE NAME (AC), CODE & PACKAGE NAME (C)
776.3,.01 CODE 0;1 FREE TEXT (Required) (Key field)
MONITOR EVENT TYPE CODE
INPUT TRANSFORM: K:$L(X)>14!($L(X)<1)!'(X'?1P.E) X
LAST EDITED: OCT 27, 2003
HELP-PROMPT: Answer must be 1-14 characters in length. A suggested guidline is to prefex the code with the
namespace fo the package creating the new code.
DESCRIPTION: This is the code assigned by an application to a particular type of event. The combination of
fields, Code and Assigning Package, should be unique.
CROSS-REFERENCE: 776.3^B
1)= S ^HLEV(776.3,"B",$E(X,1,30),DA)=""
2)= K ^HLEV(776.3,"B",$E(X,1,30),DA)
RECORD INDEXES: C (#349)
776.3,.02 PACKAGE 0;2 POINTER TO PACKAGE FILE (#9.4) (Required)
ASSIGNING PACKAGE
LAST EDITED: OCT 27, 2003
HELP-PROMPT: What package is creating this new code?
FIELD INDEX: AC (#348) MUMPS ACTION
Short Descr: Stuffs the package name into field .08
Description: This index stuffs the name of the package into the Package Name field, based on the pointer value
of the Package field.
Set Logic: D SETPKG^HLEMDD($G(DA),$G(X2(1)),$G(X1(2)))
Kill Logic: Q
X(1): PACKAGE (776.3,.02) (Subscr 1) (forwards)
X(2): PACKAGE NAME (776.3,.08) (Subscr 2) (forwards)
776.3,.03 CATEGORY 0;3 SET (Required)
MONITOR EVENT TYPE CATEGORY
'1' FOR HL7 SYSTEM MESSAGE ERROR;
'2' FOR APPLICATION MESSAGE ERROR;
'3' FOR OPERATIONAL ERROR;
'4' FOR EVENT MONITOR NOTIFICATION;
LAST EDITED: JUL 10, 2003
HELP-PROMPT: What category best describes the event type?
DESCRIPTION: HL7 System Message Errors are errors discovered by the HL7 system while processing a particular
message. Application Message Errors are errors discovered by an appication while processing a
particular message. This type of error is defined by the application and usually involve
application-specific business rules. Operational Errors are not related to a specific message,
rather,they are related to a site. An common example is a logical link that fails. An Event
Monitor Notification is any sort of status update message that may be posted by the Event Monitors.
776.3,.04 URGENT 0;4 SET
'0' FOR NO;
'1' FOR YES;
'2' FOR URGENT IF ACTION FAILS;
LAST EDITED: JUL 22, 2003
HELP-PROMPT: Is it urgent that this events of this type be reviewed?
776.3,.05 CONGLOMERATE 0;5 SET
'0' FOR NO;
'1' FOR YES;
LAST EDITED: JUL 09, 2003
HELP-PROMPT: Should events of this type be counted over a particular time period and reported as a single event?
DESCRIPTION: This field determines whether or not discrete events of this type are counted over a defined period
of time and reported as a single event along with the count.
Events that are conglomerated can not store application-specific data with the event.
776.3,.06 HOURS COVERED 0;6 NUMBER
PERIOD IN HOURS TO CONGLOMERATE
INPUT TRANSFORM: K:+X'=X!(X>9999)!(X<.1)!(X?.E1"."1.N) X
LAST EDITED: AUG 05, 2003
HELP-PROMPT: What period in number of hours should this event type cover?
DESCRIPTION: If events of this type are to be conglomerated, this field defines the period in hours over which
the events of this type are to be counted.
776.3,.07 REVIEW 0;7 SET
REVIEW EVENTS OF THIS TYPE?
'0' FOR NOT REQUIRED;
'1' FOR REQUIRED;
'2' FOR ONLY IF ACTION FAILS;
LAST EDITED: JUL 14, 2003
HELP-PROMPT: Should this type of event be reviewed?
776.3,.08 PACKAGE NAME 0;8 FREE TEXT (Key field)
INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X
LAST EDITED: OCT 27, 2003
HELP-PROMPT: Answer with the exact name of the package as found in the Package file.
DESCRIPTION: This field will be used in the key definition rather then the field PACKAGE because KIDS will not
resolve the pointers in the PACKAGE file if the field is part of the key.
FIELD INDEX: AC (#348) MUMPS ACTION
Short Descr: Stuffs the package name into field .08
Description: This index stuffs the name of the package into the Package Name field, based on the pointer value
of the Package field.
Set Logic: D SETPKG^HLEMDD($G(DA),$G(X2(1)),$G(X1(2)))
Kill Logic: Q
X(1): PACKAGE (776.3,.02) (Subscr 1) (forwards)
X(2): PACKAGE NAME (776.3,.08) (Subscr 2) (forwards)
RECORD INDEXES: C (#349)
776.3,.09 DAYS TILL PURGE 0;9 NUMBER (Required)
DAYS TO KEEP BEFORE PURGING
INPUT TRANSFORM: K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X
LAST EDITED: JUL 25, 2003
HELP-PROMPT: How many days should events of this type be tracked before they are purged?
776.3,.1 ACTIVE 0;10 SET
'0' FOR NO;
'1' FOR YES;
LAST EDITED: DEC 11, 2003
HELP-PROMPT: Should events of this type be logged?
DESCRIPTION: This field can be used to disable a particular event type. It is a safety feature - if large
numbers of events of a particular tye are generated and it is discovered that logging them is not
useful then the logging can be turned off via this field.
776.3,1 ACTION 1;E1,20 FREE TEXT
AUTOMATIC ACTION FOR EVENT TYPE
INPUT TRANSFORM: K:'$L($T(@X)) X
LAST EDITED: JUL 10, 2003
HELP-PROMPT: What routine, in the format ^, should be executed when events of this type occur?
DESCRIPTION: The action will be executed when the event occurs. For conglomerated events, the action is
executed when the time period expires.
NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
776.3,2 SERVER LOCATIONS 2;0 POINTER Multiple #776.32
LAST EDITED: JUL 10, 2003
776.32,.01 DOMAIN 0;1 POINTER TO DOMAIN FILE (#4.2) (Multiply asked)
SERVER LOCATION FOR EVENT TYPE
LAST EDITED: JUL 10, 2003
HELP-PROMPT: What locations will monitor servers be located for this event type?
DESCRIPTION: This will be a list of Mailman Domains where events of this type should be sent for centralized
monitoring.
CROSS-REFERENCE: 776.32^B
1)= S ^HLEV(776.3,DA(1),2,"B",$E(X,1,30),DA)=""
2)= K ^HLEV(776.3,DA(1),2,"B",$E(X,1,30),DA)
776.32,2 SCREEN 1;E1,245 MUMPS
INPUT TRANSFORM: K:$L(X)>245 X D:$D(X) ^DIM
LAST EDITED: OCT 02, 2003
HELP-PROMPT: Enter MUMPS code to be Xecuted when an event of this type occurs. It should set $T to 1 if the
event should be sent to this remote location.
DESCRIPTION: This field provides a method for application developers to screen which events are sent to a
remote server. At the point at which an event occurs, Event Logging determines what remoted
locations to send the event. If an application wishes to provide remoted viewing of its events
then for those Event Types for which it is concerned it should make an entry in the Server
Locations multiple. It can further screen which events to send by associating a MUMPS screen with
that SERVER LOCATION. When Xecuted, the screen should set $T=1 if the event should be sent to
the remote server, 0 otherwise. The HLEVENT() array is defined at the point at which the screen
is executed. A complete description of that array is provided for the $$EVENT^HLEME() API that
is provide for application developers using the HL7 package.
776.3,3 FULL DESCRIPTION 3;0 WORD-PROCESSING #776.33
LAST EDITED: JUL 22, 2003
LAST EDITED: JUL 22, 2003
HELP-PROMPT: Enter a complete description of what this events of this type signfy.
776.3,4.01 BRIEF DESCRIPTION 4;1 FREE TEXT
INPUT TRANSFORM: K:$L(X)>80!($L(X)<1) X
LAST EDITED: JUL 22, 2003
HELP-PROMPT: Answer must be 1-80 characters in length
FILES POINTED TO FIELDS
DOMAIN (#4.2) SERVER LOCATIONS:DOMAIN (#.01)
PACKAGE (#9.4) PACKAGE (#.02)
File #776.3
Record Indexes:
C (#349) RECORD REGULAR IR LOOKUP & SORTING
Unique for: Key A (#38), File #776.3
Short Descr: Uniqueness Index for Key 'A' of File #776.3
Set Logic: S ^HLEV(776.3,"C",X(1),X(2),DA)=""
Kill Logic: K ^HLEV(776.3,"C",X(1),X(2),DA)
Whole Kill: K ^HLEV(776.3,"C")
X(1): CODE (776.3,.01) (Subscr 1)
X(2): PACKAGE NAME (776.3,.08) (Subscr 2)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):