MUC 1 Vbecs 2 3 0 Tech Security Guide
User Manual:
Open the PDF directly: View PDF
Page Count: 119 [warning: Documents this large are best viewed by clicking the View PDF Link!]
- Revision History
- Table of Contents
- Introduction
- How This Technical Manual-Security Guide Is Organized
- Remote Desktop Configuration (Windows)
- Server Hardware and System Configuration
- VistA Maintenance Operations
- Troubleshooting
- Deleting the Remote Desktop Services Licensing Information on a VBECS Workstation
- Identity Verification Warning
- Stopping VBECS Services
- Starting VBECS Services
- VBECS Auditing
- VBECS Exception Logging
- VBECS Application Interfaces
- Zebra Printer Problems
- Scanner Problems
- Archiving and Recovery (Enterprise Operations Only)
- Restore the Databases
- 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 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)
- Failover
- Performance
- Security
- Glossary
- Appendices
- Index