VBECS responds to the new order request with an The HL7 message is missing application reject (AR) patient last or first name or acknowledgement message one or more name indicating Patient Name(s) not components length(s) found in HL7 Message or exceed(s) the VBECS Patient's Name(s) field size(s) maximum supported value. exceed(s) VBECS maximum supported value. Rejected patient order 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. VBECS Admin: Order mappings to institutions Stop and restart the New orders are not Configure within a division’s <Prod or Test> HL7 Listener showing up in VBECS. Division configuration were changed. Service. The patient being updated in VistA is not in the VBECS No action is required. Patient table and is, therefore, not a blood bank patient. The fields that were updated in VistA are not stored in No action is required. VBECS; therefore, no data will be updated. Schedule the VAFC BATCH UPDATE option to run at the The Taskman scheduled desired frequency (the option VAFC UPDATE is recommended frequency is VBECS: Patient VistA patient not updates scheduled are to run or has every 10 minutes) or use the Update Alerts not showing not up reached in VBECS. the time limit in option Option “One-time the schedule. Queue” in the Taskman Management Options to start the task. The VBECSPTU Logical Link Start the VBECSPTU Logical is not running on the VistA 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. 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. VBECS responds to the new order 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 order 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. VBECS Admin: Configure Division New orders are not showing up in VBECS. Order mappings to institutions within a division’s configuration were changed. Stop and restart the <Prod or Test> HL7 Listener Service. VBECS: Patient Update Alerts VistA patient updates are not showing up in VBECS. The patient being updated in VistA is not in the VBECS Patient table and is, therefore, not a blood bank patient. No action is required. The fields that were updated in VistA are not stored in VBECS; therefore, no data will be updated. No action is required. The Taskman scheduled option VAFC UPDATE is not scheduled to run or has not reached the time limit in the schedule. Schedule the VAFC BATCH UPDATE option to run at the desired frequency (the recommended frequency is every 10 minutes) or use the option “One-time Option Queue” in the Taskman Management Options to start the task. The VBECSPTU Logical Link is not running on the VistA system. Start the VBECSPTU 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.
vbecs_2_2_1_tech_security_guide.docx