Loading...
Loading...
The following scenarios explain how NextGen® Enterprise and third-party applications interact with each other during a CCOW session.
Logging onto NextGen while a Third-party Application is Open (No active patient)
When a user logs onto NextGen® Enterprise and CCOW context has already been set by a third-party application, NextGen® Enterprise checks to see if it can set context. For NextGen® Enterprise to set context in this situation, the following conditions must exist:
In this scenario, the user logs onto NextGen® Enterprise and the patient context (no patient selected) has already been set by the third-party application.
| Conditional Message | If Yes | If No |
|---|---|---|
| User Not Found in Default practice, do you want to continue and not participate in CCOW with other applications? | Log on with NextGen® Enterprise logon dialog. | Shutdown NextGen® Enterprise application. |
| User Not Licensed for current application, do you want to continue and not participate in CCOW with other applications? | Log on with NextGen® Enterprise logon dialog. | Shutdown NextGen® Enterprise application. |
Logging onto NextGen® Enterprise while a Third-party Application is Open (Active patient)
In this scenario, the user logs onto NextGen® Enterprise and the patient context (patient selected) has already been set by the third-party application.
| Conditional Message | If Yes | If No |
|---|---|---|
| User Not Found in Default practice, do you want to continue and not participate in CCOW with other applications? | Log on with NextGen® Enterprise logon dialog. | Shutdown NextGen® Enterprise application. |
| User Not Licensed for current application, do you want to continue and not participate in CCOW with other applications? | Log on with NextGen® Enterpriselogon dialog. | Shutdown NextGen® Enterprise application. |
User Context Change While Logged into NextGen® Enterprise and a Third-party Application
When a third-party application switches context, the following conditions must exist for NextGen® Enterprise to be able to change context:
When the user changes in the third-party application and there is nothing in the NextGen® Enterprise application that prevents a user context change, the current user in the NextGen® Enterprise application is automatically logged out. The new user is then automatically logged into the NextGen® Enterprise application (if he/she exists in the practice).
If a message displays that the NextGen® Enterprise application cannot perform the user context change, then select one of the following:
The third-party application Patient Context Change in Third-Party Application While Logged into both NextGen and Third-party Application
When the patient changes in the third-party application and there is nothing in the NextGen® Enterprise application that prevents a patient context change, the current patient in the NextGen® Enterprise application is automatically changed. The new user is then automatically logged into the NextGen® Enterprise application (if he/she exists in the practice).
If a message displays that the NextGen® Enterprise application cannot perform the patient context change, then select one of the following:
User Context Change in NextGen while Logged into both NextGen and Third-Party Application
In this scenario, the user is logged into both NextGen® Enterprise and the third-party application. The user context is then changed (original user logs off, new user logs on) in NextGen® Enterprise.
If a message displays that the third-party application cannot perform the user context change, then select one of the following:
Patient Context Change in NextGen while Logged into both NextGen and Third-Party Application
In this workflow, the user is logged into both NextGen and the third-party application. The patient context is then changed (different patient selected) in NextGen® Enterprise.
If a message displays that the third-party application cannot perform the patient context change, then select one of the following: