How To: Use the Test Tool for Epic EPCS VAM – SecureAuth Support

Version Affected: All

Overview

This article explains how to use the standalone .NET Test Tool that ships with the Epic EPCS VAM (Electronic Prescriptions of Controlled Substances Value-Added Module) to confirm multi-factor authentication (MFA) is working correctly — either to verify it is currently working, or to test it before adding it to the Hyperspace/Hyperdrive configuration. The tool sends a request nearly identical to what a prescriber would trigger when prescribing a restricted medication.

Use the EPCS VAM Test Tool

On the Epic Server, open the SecureAuth folder and find the Test Tool folder.
Run StandAloneNETTester.exe. The MainForm window opens.

MainForm window of the EPCS VAM Test Tool, with a ProgID field, an Object dropdown, Authenticate and Stop Listening buttons, a Results box, and Add Initial Context Data controls.

In the ProgID field, enter SecureAuthLoginDevice.Receiver. Use SecureAuthLoginDevice.Receiver2 instead only if you know the customer is using Hyperdrive.
Click Authenticate. The RequestForm window opens.

RequestForm window of the EPCS VAM Test Tool, listing a requested Key of UserID, with Key and Value fields and Add Data, Return True, and Return False buttons.

In the Key field, enter UserID. In the Value field, enter the username you want to test.
Click Add Data. The Key and Value fields clear — this is expected after adding data.
Click Return True.

The Epic EPCS VAM authentication screen appears, and you can attempt to authenticate through it if troubleshooting. If authentication completes successfully, the Results field on the MainForm window updates to show success; otherwise it displays Perform Action Failed. You can click Authenticate again to retry, though the Results field only ever shows the most recent attempt.

Special Considerations

If you need to gather logs from the Test Tool, set Log Level="2" for the Test Tool in SASettings.xml, located in the SecureAuth folder on the Epic Server.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.