How to use Test Tool for Epic EPCS VAM

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises

  • Description:

    The Epic EPCS VAM (Electronic Prescriptions of Controlled Substances Value-Added Module) comes with a standalone .NET Test Tool that can be used to determine if there is an issue with using MFA. This can be used to test that it is currently working or will work before adding it to the Hyperspace/Hyperdrive configuration. It will send a request that is nearly identical to what the doctors would be seeing when they are trying to prescribe restricted medication.

    Note: If you are grabbing logs, you will need to turn Log Level="2" for the Test Tool located in the SASettings.xml in the SecureAuth folder on the Epic Server.



    1. Open the SecureAuth folder on the Epic Server.

    2. Find the Test Tool folder.

    3. Run the StandAloneNETTester.exe file. The MainForm window should appear.

    4. In the ProgID field, enter SecureAuthLoginDevice.Receiver.
    Note: This can be SecureAuthLoginDevice.Receiver2 only if you know they are using Hyperdrive.

    5. Hit Authenticate. The RequestForm window should appear.

    6. Enter UserID in the Key field. In the Value field, enter the Username you wish to test.

    7. Hit Add Data.
    Note: The Key and Value fields will disappear but that is to be expected when adding data.

    8. Hit Return True.

    The Epic EPCS VAM appears. You can try to authenticate through if you are troubleshooting. If the authentication completes successfully, the Results field on the MainForm window updates with a success. Otherwise the field displays Perform Action Failed. You can try again by hitting Authenticate if needed, however the results will only show the latest attempt.


    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.

    0 out of 0 found this helpful



    Please sign in to leave a comment.