Agent Install

Last Modified on 03/18/2019 10:30 am EDT

CollaborateMD (CMD) requires all computers running the CMD Interface Bridge (CIB) Agent software be updated to use Java 8 or higher. CMD's web services will only accept connections using TLS 1.1 or TLS 1.2 with modern and secure cipher suites to ensure communications to or from are done in the most secure fashion. Regulatory compliance dictates that older protocols such as SSL 3.0 and TLS 1.0 are not used in the environment as they are flawed and contain security vulnerabilities. At some point in the future, TLS 1.1 will also be deprecated as there are known security vulnerabilities in this protocol as well.

Prior to installing the CIB Agent, please ensure the inbound (which is for Patient Demographics via the HL7 Admit, Discharge and Transfer (ADT) Message) and outbound (Charge Data via the Detailed Financial Transactions (DFT) Message) directory paths are properly set up on the computer responsible for hosting the CIB Agent. These file directories should be set up by the EMR / EHR Vendor and properly communicated the responsible individual within the business office responsible for the CMD application. The CIB Agent must be configured with at least one (inbound or outbound) queue in order to work correctly.

Step 1: Install the Agent Service

Partner with your Information Technology (IT) Department to ensure you have the proper permissions to install software on your computer.

Step 3: Verifying the CMD Interface Bridge is Properly Configured

Validation of the Charges Queue (if required and properly configured).

Validation of the Patient Queue (if required and properly configured).

Click the "Close" button to return to the Server Control (main) window.

Start, Stop or Pause the CIB Agent:

Click the "Start" button to start the services.

Click the "Stop" button to stop the services.

Click the "Pause" button to pause the services.

Once the CIB Agent is running, you can test the interface by either saving a patient in CMD and ensure it updates within the EMR/EHR system, or have the client close an encounter within the EMR/EHR and verify the claim is generated within CMD using Interface Tracking.