Skip to main content

Avatar PM Setup

When client records are created in myAvatar PM (Admission form) these records can be accessed by the associated agency in ProviderConnect. 

  • ProviderConnect and myAvatar PM reference the same client IDs.
ProviderConnect System Defaults form
  • This form defines settings that affect interactions between ProviderConnect, Avatar PM and Avatar MSO.
  • Dictionaries must be defined in the Dictionary Update form (Avatar PM) before the dictionary code upload can be performed.

  1. Select ProviderConnect System Defaults from the System Definition menu in myAvatar PM.
  2. Select Yes to enabled ProviderConnect.
  3. Define the number of attempts myAvatar MSO makes when connecting to ProviderConnect.
  4. Associate a ProviderConnect user.
  • Enter the user name, click to select.
  • The user is associated with all data transmitted to ProviderConnect.
  • The user must have been defined in the User Definition form (Avatar PM), and must have access to ProviderConnect forms.
  1. Enter the ProviderConnect WSDL address.

  • This path is used to connect to ProviderConnect Web services. The address is defined by a Netsmart system administrator.
  1. Select whether an email is sent to the ProviderConnect user when the number of connection attempts is exceeded (Number Of Connection Attempts field).

  • If Yes is selected, enter the email address.
  • Click Test Email to test the email. Email is defined in the System Generated Email Settings form (RADplus Utilities, Avatar PM).
  1. If appropriate, click Dictionary Code Upload to load dictionary files that have been defined in the Dictionary Update form in Avatar PM.

  • Clicking Dictionary Code Upload files every dictionary code defined in Avatar PM and Avatar MSO to ProviderConnect.
    Note: Depending on the number of dictionary codes that will be uploaded, the upload process can take several minutes.
  1. If appropriate, click Diagnosis Code Upload to file diagnosis codes defined in the Diagnosis Table Maintenance form to (myAvatar PM, myAvatar MSO) to ProviderConnect.
  2. In the SSL Configuration field, enter the SSL configuration name.
  • The  facility must be running Cache 2008.
  1. If appropriate, click Synchronize ProviderConnect To Avatar.

  • Information in Avatar forms is sent to ProviderConnect.
  • The ProviderConnect Application Build form must be filed for modeled form definitions to be sent to ProviderConnect.
  • All users should be logged out of ProviderConnect.
  • The process may take time to complete.
  1. Select File.

  • Click Update ProviderConnect tables to verify that the Web service WSDL information is synchronized between ProviderConnect and Avatar PM and Avatar MSO. This is recommended when a new form or Web service has been added for ProviderConnect and Avatar interaction.

Transaction Log

Generate a report on transactions between ProviderConnect and Avatar MSO, and resend failed transactions.

  1. Enter the report start and end date.

  • If no dates are entered in the From and Through Date fields, the report displays all transactions.
  1. Click View Transaction Log.

  2. Click View MSO Transaction Log to transactions sent between ProviderConnect and Avatar MSO.

  3. If there were unsuccessful transactions, click Re-Send Failed Transactions to resubmit all transactions that encountered errors.

Client Lookup Configuration Manager Form

Define search parameters that control how client searches are performed in ProviderConnect. Weight different fields in the client lookup used in the Add New Client/Client Search link.

► Registry Settings

 

  • Was this article helpful?