{"aaData": [["1", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
Invalid Event Protocol IEN
\n"], ["10", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nA routine to process the incoming message was not entered in the\nGenerate/Process Routine field in the Protocol file.\n
\n
\n", "
Missing Processing Routine
\n"], ["100", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe lower level protocol could not secure internal entry numbers\nto file #870.\n
\n
\n", "
LLP Could not Enqueue the Message
\n"], ["101", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
LLP Unable to Dequeue Message
\n"], ["102", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nA message was Nak'ed look at the individual message\nerror field to see why.\n
\n
\n", "
Message was NAK'ed
\n"], ["103", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
LLP Exceeded Retry Param
\n"], ["104", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe message sent by DHCP was low level NAK'd by the other system.\nLook at this link's output queue for more information.  This information\nwill be found in the STATUS field of individual messages.\n
\n
\n", "
Message Low Level NAK'd by Other System
\n"], ["105", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe lower level protocol header "tvv" is malformed. Check message\nthat was sent to DHCP.\n
\n
\n", "
Tvv is Malformed
\n"], ["106", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nLLP exceeded READ TIMEOUT parameter in file 870 while reading in a\nmessage.\n
\n
\n", "
LLP Timed Out While Reading in a Message
\n"], ["107", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nMessage has an incorrect or missing checksum\n
\n
\n", "
Message did not Validate, Look at Checksums
\n"], ["108", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe response message received was not what was expected. This only happens\nwith bi-directional messages.  \n
\n
\n", "
Incorrect Message Received
\n"], ["109", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nMessage has already been received and processed.  This is a duplicate.\n
\n
\n", "
Duplicate Message
\n"], ["11", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe continuation parameter cannot be more than 180 characters in length.\n
\n
\n", "
Continuation Pointer Parameter too Long
\n"], ["12", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe header segment for the incoming message is missing.\n
\n
\n", "
Missing Message Header Segment
\n"], ["13", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nInformation in the message header segment was incorrect or missing.\n
\n
\n", "
Application Reject Error
\n"], ["14", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe Server Application field in the Protocol file (#101) did not have\na value for the event driver protocol identified by the value in the EID\nparameter.\n
\n
\n", "
Server Application Missing in Protocol File
\n"], ["15", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nNo clients are defined for this server protocol. Unless the application\nintends to submit a specific client using the HLL("LINKS") array, this\nmessage should not be sent.\n
\n
\n", "
No Client
\n"], ["16", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe server protocol has been placed OUT OF SERVICE. The message has been\nrejected by the HL7 Message Service. The sending application must retain\nthe message for later transmission.\n
\n
\n", "
Server Protocol Disabled
\n"], ["17", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nAn error occured during the generation of the message.\n
\n
\n", "
Error During Generation
\n"], ["18", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nAn error occured during the processing of the message.\n
\n
\n", "
Error During Processing
\n"], ["2", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
Event Data Missing
\n"], ["200", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe IEN that was passed to the routine does not exist in the\nassociated file.\n
\n
\n", "
Invalid Internal Entry Number
\n"], ["201", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe IEN should have been passed to the routine, but it was not.\nPlease look at the routine to determine which IEN should be used.\n
\n
\n", "
Missing Internal Entry Number
\n"], ["202", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe direction of the queue is not in the list:\nIN, OUT, 1, 2\nThe number 1 can be used to specify the "IN" queue\nThe number 2 can be used to specify the "OUT" queue\n
\n
\n", "
Invalid Direction
\n"], ["203", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nA queue direction (IN or OUT) must be passed to tell which\nqueue you are acting on.\n
\n
\n", "
Direction not Given
\n"], ["204", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nFILE^DICN returned a -1 error code for some reason.  Please record\nthe conditions used to create the record and inform an HL7 developer.\n
\n
\n", "
DICN Error
\n"], ["AC-NO 870", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
AC xref pointing to non-existent link
\n"], ["AC-NO 773", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe CHECK 773 AC XREF monitors calls CHECKAC^HLEVX002.  One of the checks\nof this monitor is for ^HLMA("AC",I/O,LINK,IEN773) entries that point to\na non-existent file 773 entry.  When this occurs, an entry is made using\nthis AC-NO 773 entry.\n
\n
\n", "
AC xref pointing to non-existent 773
\n"], ["AC-HUNG", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
AC xref that doesn't process
\n"], ["870-DINUM", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe LINK (870) CHECKS monitor checks the HL Logical Link file (#870) for \nvarious types of problems in the IN and OUT queues.  If an entry is not \nproperly DINUMd, processing problems occur.  This entry records this type\nproblem.\n
\n
\n", "
Incorrectly DINUMd 870 queue entry
\n"], ["870-SKIP", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe LINK (870) CHECKS monitor checks the HL Logical Link file (#870) for\nvarious types of problems in the IN and OUT queues.  Each queue \nmultiple's IENs must be sequential.  If any IEN is skipped, processing \nproblems occur.  This entry records this type problem.\n
\n
\n", "
Skipped 870 queue entry
\n"], ["870-STUB", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
Stub 870 queue entry
\n"], ["AC-PROC'D", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe CHECK 773 AC XREF monitor checks the ^HLMA("AC",I/O,LINK,IEN) \ncross-reference.  This xref should exist only for un-processed entries.  \nIf an entry has been processed, and the AC xref exists, the entry is \nrecorded using this entry.\n
\n
\n", "
AC xref for a processed entry
\n"], ["773 PURGE", "
HEALTH LEVEL SEVEN
\n", "
EVENT MONITOR NOTIFICATION
\n", "
NO
\n", "
YES
\n", "
1
\n", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
Set of records purged from file 773 durring approx one hour.
\n"], ["772 PURGE", "
HEALTH LEVEL SEVEN
\n", "
EVENT MONITOR NOTIFICATION
\n", "
NO
\n", "
YES
\n", "
1
\n", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThis is a notification of records purged in file 772 via the Fast Purge.\n
\n
\n", "
Set of records purged from file 772 durring approx one hour.
\n"], ["SRVR ERROR", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThis event signals that an error was encountered while trying to send or receive\nand event at a remote location. If encountered locally, the event id and ien\nare stored as application data.  If remote, the mailman message id is stored.\n
\n
\n", "
HL7 EVENT LOG SERVER ENCOUNTERED AN ERROR
\n"], ["FILE-HLDIE", "
HEALTH LEVEL SEVEN
\n", "
OPERATIONAL ERROR
\n", "
NO
\n", "
NO
\n", "", "
REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
7
\n", "
YES
\n", "", "", "
\nAPI calls in HLTP4 to FILE^DIE have been changed to FILE^HLDIE, using\ndirect hard sets of data.  If any call to FILE^HLDIE fails the pre-\nexecution checks, an event is recorded in the "logger" using this\nevent type.  (And, FILE^DIE is called instead of FILE^HLDIE.)\n
\n
\n", "
FILE~HLDIE Error
\n"], ["3", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
Missing Generation Routine
\n"], ["4", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
Invalid Array Parameter Value
\n"], ["5", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "", "
Invalid Priority Parameter Value
\n"], ["6", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe security parameter cannot be more than 40 characters in length.\n
\n
\n", "
Security Parameter too Long
\n"], ["7", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nOne or more of the input parameters required for this entry point\nis missing.\n
\n
\n", "
Missing Input Parameter(s)
\n"], ["8", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nThe local array HLS() or global array ^TMP("HLS",$J) is incomplete or\nmissing.\n
\n
\n", "
Invalid or Missing Message Array
\n"], ["9", "
HEALTH LEVEL SEVEN
\n", "
HL7 SYSTEM MESSAGE ERROR
\n", "
NO
\n", "
NO
\n", "", "
NOT REQUIRED
\n", "
HEALTH LEVEL SEVEN
\n", "
3
\n", "
YES
\n", "", "", "
\nAn error ocurred while the application was processing the message.  The\nspecific problem encountered is described in the error message field.\n
\n
\n", "
Application Level Error
\n"]]}