Primary SQL Server: This server fields all requests. Its data are replicated to the High Availability and Disaster Recovery servers. High Availability (HA) SQL Server: This server provides database backup services through synchronous replication. Its data are guaranteed to be consistent with the Primary. It becomes the Primary should the original Primary server fail or become unreachable. Failover to this server is automatic. Disaster Recovery (DR) SQL Server: This server resides at a remote site and provides database backup services through asynchronous replication. It becomes the Primary server should both the Primary and HA server fail or become unreachable. Failover to this server is a manual process. Windows 7 Workstations: Users continue to access the VBECS application using Remote Desktop Services. Figure 12: System Schematic Required Peripherals Table 1 describes additional required hardware. Table 1: Additional Required Hardware Additional Required Hardware Barcode Scanner Hand-Held 4600 (This is the model distributed with the original VBECS deployment and is now discontinued. The successor is the Honeywell Xenon 1900.) Report Printer HP LaserJet 9040dn (sites may elect to use a different report printer) Label Printer Zebra ZM400, Z4MPlus or ZT410; Must print at 300 DPI and have Ethernet connectivity. Printers Report Printer A laser printer capable of printing 8.5" x 11" sheets may be used. VBECS supports duplex printing, but not all printers are duplex capable. Consult the printer documentation to determine if it has this capability. Installing a Printer (Server Administrators Only) To install a printer, execute the following instructions: Copy the printer driver to the C:\temp directory on the app server. Log into the app server with administrative privileges. Click Start, Devices and Printers. The Device and Printers window is displayed (Figure 13). Click the Add a printer button. Figure 13: Example of Devices and Printers, Add a printer
STARTUP NODE: PERSISTENT: NO RETENTION: UNI-DIRECTIONAL WAIT: ____________________________________________________________________________ COMMAND: Press <PF1>H for help Insert Start VistA HL7 Logical Links Before data can be transmitted over the VBECS logical links, edit the link definitions as described above. To turn on the new VBECS logical links, select Start/Stop Links [HL START]. Start the “OERR-VBECS” logical link. Start the “VBECS-OERR” logical link. Start the “VBECSPTM” logical link. the “VBECSPTU” logical link. Ensure that the VistA HL7 Link Manager is running; VBECS messaging cannot occur without it. To check the status of the Link Manager (and, if necessary, restart it), access the HL START/STOP LINK MANAGER menu option. Monitor VBECS HL7 Logical Links Once two-way communication has been established, you can monitor the links. Use the “System Link Monitor” to view the status of the VBECS Logical Links. From the “HL7 Main Menu”, select System Link Monitor (Figure 53). Figure 53: HL7 System Link Monitor Menu Navigation HL7 Main Menu Event monitoring menu ... Systems Link Monitor and Link Management Options ... Message Management Options ... Interface Developer Options ... Site Parameter Edit Select HL7 Main Menu Option: System Link Monitor When a list of HL7 links defined at your site appears, press V at the “Select a Command:” prompt (Figure 54). At the “Select LINK MONITOR VIEWS:” prompt, enter VBECS (Figure 54). Figure 54: System Link Monitor SYSTEM LINK MONITOR for <your site name> MESSAGES MESSAGES MESSAGES MESSAGES DEVICE NODE RECEIVED PROCESSED TO SEND SENT TYPE STATE LA7V 657 4 4 MM Halting LL15VISN 105 105 394 105 NC Shutdown MPIVA 0 0 322 0 NC Shutdown
Click the Printers tab. Select a Default Report Printer from the list. Clear or click the Division Uses Label Printer check box. Edit the COM port number and/or the TCP port number. Enter the IP address (Figure 69). Capture a screen shot. the user to enter the COM and TCP port numbers and the IP address for the label printer. MBR_2.31Allows the user to select the default printer for the division when more than one printer is installed on the system. NOTES Standard values for COM and TCP ports: COM = 2 TCP = 9100 Click the Time Zone tab. Select a time zone. In the Daylight Savings field, select US Standard DST, Do not observe DST, or Custom DST. Enter start and end dates for custom DST (Figure 70). Capture a screen shot. Click Save. Allows the user to set the time zone and daylight saving parameters. Click Save and OK to commit the changes or add the new division to the VBECS database. Commits changes and additions to the database. NOTES Multidivisional sites must repeat Steps 3 through 11 for each division. DR 2,717The VBECS Administrator/Supervisor who configured the divisions must add himself as a user to all divisions to enable the functionality of canned comments in the VBECS system. To close the VBECS – Configure Divisions dialog, click in the upper-right corner. Figure 64: Example of Configure Divisions Figure 65: Example of Configure Division: Division Identification Figure 66: Example of Select VistA Divisions
NOTES BR_19.03 and MBR_3.06 One role at a time may be assigned to a user at a division. A user may have only one active user role per division. BR_19.05 VBECS allows the assignment of a security level to one or more users at a time. BR_19.06 VBECS warns that there must be at least one level 6 VBECS Administrator/Supervisor in the division and does not allow the user to change the last Administrator/Supervisor. Click Update and Save. Displays a confirmation dialog. Click Yes to commit changes to the database. Click Yes to commit changes to the database. To close the Edit Users dialog box, click in the upper-right corner. Figure 75: Example of Configure Users Figure 76: Example of Edit User Figure 77: Example of Windows Figure 78: Example of VistA Users Figure 79: Example of VistA Divisions Figure 80: Example of Inactive Users Record Workload DataUC_15 VBECS workload data is recorded in VBECS when records that qualify as Workload Events are saved in VBECS. This data is transmitted to the VistA Laboratory workload recording system for national and local workload reporting. Assumptions Workload codes were assigned to VBECS processes using Workload Codes. Healthcare Common Procedure Coding System codes were assigned to blood products using Blood Products. A record was saved or inactivated immediately preceding workload data collection.
10: Troubleshooting Rejected VBECS HL7 Messages Error Code Description of Problem 100 Segment Sequence 101 Required Missing 102 Data Type Error 103 Table Value Not Found 200 Unsupported Message Type 201 Unsupported Event Code 202 Unsupported Processing ID 203 Unsupported Version Id See 11: VBECS HL7 Versions 204 Unknown Key Identifier 205 Duplicate Key Identifier 206 Application Record Locked 207 Application Internal Error 208 Conflicting Processing Id Table 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 Table 12: Troubleshooting VBECS Application Interfaces Source Description of Problem Possible Cause Solution VBECS: Order Alerts and Pending Order List New orders or cancellations of existing orders in CPRS are not showing up in The Logical Link is not running on the VistA system. Start the OERR-VBECS 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. 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.