This article is for administrators troubleshooting issues processing documents from Kno2 to Aprima such as:
Patient Search does not pull up any patients.
Document Types drop-down is not returning Attachment Types.
You receive an Aprima Reference ID when downloading a message to Aprima.
If you are unsure of the following steps, or do not have access to the options, contact your Aprima Support path for assistance.
Check Integration Connection
Navigate to Settings > API > Integrations > Aprima or Aprima V2 and check connection by clicking on the circle with the checkmark.
If the checkmark turns green, but the integration is not working, open a support case with your Aprima Support channel for assistance.
If the checkmark turns red, it will be resolved by either updating the credentials used by the integration or restarting the Aprima Job Service on your Aprima server.
Re-enter Aprima Credentials for Aprima integration in Kno2:
If the Aprima password for the person who configured the Aprima integration has recently changed, or other details used in the integration properties have changed, please update them using the following steps:
Navigate to Settings > API > Integrations > Aprima or Aprima V2
Click Edit (pencil) icon
Click Edit integration properties
Complete the following fields:
Username: <this is an Active Directory username>
Password: <this is an Active Directory password>
ClientId: <Aprima Client ID, obtained within PRM under Aprima – Help – About window>
Click Save and check connection again by clicking on the circle with the check mark.
Optional: Set up a generic 'Kno2 User' Active Directory account so that future password changes do not have affect the integration.
To check the Aprima Job Service:
If the Aprima credentials have been re-entered in Kno2 and you are still receiving a red check mark, your Aprima Job Service may need to be restarted.
If your Aprima server is hosted, please contact your Aprima support path for assistance.
If your Aprima server is on prem, you may need to contact your IT support for assistance with the following steps:
Under the Windows Services on your server. locate PRMAppService2525. If this service, or the server, is restarted, it may re-establish the connection.