VBECS responds to the patient update request with an application reject (AR) acknowledgement message The HL7 message is missing indicating Patient Name(s) not patient last or first name or found in HL7 Message or one or more name Patient's Name(s) field size(s) components length(s) exceed(s) VBECS maximum exceed(s) the VBECS supported value. Rejected maximum supported value. patient update messages due to invalid patient name message content are recorded on the Windows Event Log (Finding Application Log Entries from Email Alerts) and an email message containing the MSH segment of the rejected HL7 message as a means to identify the message in the server event log is sent to the interface failure alert recipient set in VBECS Administrator for immediate action. The two patient identifiers in the merge do not exist in No action is required. VBECS and, therefore, cannot be merged. The VBECPTM Logical Link is the VBECSPTM Logical not running on the Link. system. The VBECS <Prod or Test> HL7 Listener Windows Start or restart the VBECS Service is not running or is <Prod or Test> HL7 Listener locked on the application Windows Service. server. VistA Patient Merge VBECS: Patient Network connectivity issue Contact local system support. events are not showing up Merge Alerts Failed patient merge in VBECS. messages due to invalid patient name message content The HL7 message is missing are recorded on the Windows patient last or first name or Event Log and an email one or more name message containing the MSH components length(s) segment of the rejected HL7 exceed(s) the VBECS message as a means to maximum supported value. identify the message in the server event log is sent to the interface failure alert recipient set in VBECS Administrator for immediate action. The VistA HL7 System The VBECS <Prod or Test> Link Monitor shows more HL7 Listener Windows Start or restart the VBECS VistA: HL7 MESSAGES TO SEND Service is not running or is <Prod or Test> HL7 Listener System Link than MESSAGES SENT locked on the VBECS Windows Service. Monitor for the OERR-VBECS Application server. Logical Link and is hung in Network connectivity issue Contact local system support. an state. “Open”
The HL7 message is missing patient last or first name or one or more name components length(s) exceed(s) the VBECS maximum supported value. VBECS responds to the patient update request with an application reject (AR) acknowledgement message indicating Patient Name(s) not found in HL7 Message or Patient's Name(s) field size(s) exceed(s) VBECS maximum supported value. Rejected patient update messages due to invalid patient name message content are recorded on the Windows Event Log (Finding Application Log Entries from Email Alerts) and an email message containing the MSH segment of the rejected HL7 message as a means to identify the message in the server event log is sent to the interface failure alert recipient set in VBECS Administrator for immediate action. VBECS: Patient Merge Alerts VistA Patient Merge events are not showing up in VBECS. The two patient identifiers in the merge do not exist in VBECS and, therefore, cannot be merged. No action is required. The VBECPTM Logical Link is not running on the system. the VBECSPTM Logical Link. The VBECS <Prod or Test> HL7 Listener Windows Service is not running or is locked on the application server. Start or restart the VBECS <Prod or Test> HL7 Listener Windows Service. Network connectivity issue Contact local system support. The HL7 message is missing patient last or first name or one or more name components length(s) exceed(s) the VBECS maximum supported value. Failed patient merge messages due to invalid patient name message content are recorded on the Windows Event Log and an email message containing the MSH segment of the rejected HL7 message as a means to identify the message in the server event log is sent to the interface failure alert recipient set in VBECS Administrator for immediate action. VistA: HL7 System Link Monitor The VistA HL7 System Link Monitor shows more MESSAGES TO SEND than MESSAGES SENT for the OERR-VBECS Logical Link and is hung in an “Open” state. The VBECS <Prod or Test> HL7 Listener Windows Service is not running or is locked on the VBECS Application server. Start or restart the VBECS <Prod or Test> HL7 Listener Windows Service. Network connectivity issue Contact local system support.
vbecs_2_1_0_tech_security_guide.docx