the event viewer and be able to identify the appropriate patient information. Table 10 describes the ERR codes (e.g., 203 like in the above example) descriptions. Table 10: Troubleshooting Rejected VBECS HL7 Messages Error Code Description of Problem 100 Segment Sequence Error 101 Required Missing 102 Data Type 103 Table Value Not Found 200 Unsupported Message Type 201 Unsupported Event Code 202 Unsupported Processing ID 203 Unsupported Version Id See Table 11: VBECS HL7 Versions. 204 Unknown Key Identifier 205 Duplicate Key Identifier 206 Application Record Locked 207 Application Internal 208 Conflicting Processing Id 11: VBECS HL7 Versions HL7 Interface HL7 Version VistA CPRS- Order Update – CPRS OERR 2.4 VistA PIMS Patient ADT Update – VAFC ADT 2.3 VistA MPI/PD PatientMerge – MPI TRIGGER 2.4 BCE COTS – Patient Blood Product Transfusion Verification 2.5 Automated Instrument 2.4 Table 12: Troubleshooting VBECS Application Interfaces Source Description of Problem Possible Solution VBECS: Order Alerts and Pending Order List New orders or cancellations of existing orders in CPRS are not showing up in The OERR-VBECS Logical Link is not running on the VistA system. the OERR-VBECS Logical Link. The <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. 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.