{"aaData": [["1", "Invalid Event Protocol IEN", "
\nThe event protocol IEN that was provided could not be found in the\nProtocol file (#101).\n\n
\nA routine to process the incoming message was not entered in the\nGenerate/Process Routine field in the Protocol file.\n\n
\nThe lower level protocol could not secure internal entry numbers\nto file #870.\n\n
\nLLP unable to dequeue message from file #870\n\n
\nA message was Nak'ed look at the individual message\nerror field to see why.\n\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
\nThe lower level protocol header "tvv" is malformed. Check message\nthat was sent to DHCP.\n\n
\nLLP exceeded READ TIMEOUT parameter in file 870 while reading in a\nmessage.\n\n
\nMessage has an incorrect or missing checksum\n\n
\nThe response message received was not what was expected. This only happens\nwith bi-directional messages. \n\n
\nMessage has already been received and processed. This is a duplicate.\n\n
\nThe continuation parameter cannot be more than 180 characters in length.\n\n
\nThe header segment for the incoming message is missing.\n\n
\nInformation in the message header segment was incorrect or missing.\n\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
\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\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
\nAn error occured during the generation of the message.\n\n
\nAn error occured during the processing of the message.\n\n
\nEvent data (server application, message type or event type) is missing\nfrom the Protocol file (#101).\n\n
\nThe IEN that was passed to the routine does not exist in the\nassociated file.\n\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
\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
\nA queue direction (IN or OUT) must be passed to tell which\nqueue you are acting on.\n\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
\nThe Generate/Process Routine field in the Protocol file (#101) is not\nfilled in.\n\n
\nThe array parameter value is not 'L' for local or 'G' for global. These\nare the only allowable values.\n\n
\nThe priority parameter does not have a first character of 'I' for\nimmediate or 'D' for delayed. These are the only allowable values.\n\n
\nThe security parameter cannot be more than 40 characters in length.\n\n
\nOne or more of the input parameters required for this entry point\nis missing.\n\n
\nThe local array HLS() or global array ^TMP("HLS",$J) is incomplete or\nmissing.\n\n\nAn error ocurred while the application was processing the message. The\nspecific problem encountered is described in the error message field.\n\n