Set Up CCOW Security

System Administrator Help

Use CCOW to Notify the Context Manager

The following explains how CCOW notifies the Context Manager when a context change occurs. Select a patient. The application notifies the Context Manager to start a context change. The Context Manager notifies the mapping agent that a context change is occurring. The mapping agent supplies the Context Manager with other identifiers known to be linked to a patient. With the Sentillion SDK Context Manager, this happens automatically when the patient context changes in the active application. With the dbMotion NextGen® Enterprise EHR Agent Context Manager, the user must initiate the patient context change by interacting with the dbMotion NextGen® Enterprise EHR. Agent utility application which hovers over the screen of the application. The Context Manager notifies the other applications that a new patient context has been proposed. Each participating application indicates whether or not it can apply the next context. If one or more of the applications cannot apply the new context, a messa

System Administrator Help

Context Change Scenarios (Sentillion)

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: The user exists in default enterprise/practice in the NGConfig.ini file. The user is licensed to use the application in the current enterprise/practice. The user has done a single sign-on to the NextGen® Enterprise applications. The patient that the user accesses in NextGen® Enterprise exists in the NGConfig.ini file. 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

System Administrator Help

Experiencing Loss of Focus with CCOW

You might sometimes experience Loss of Focus with CCOW. Loss of Focus means the application that was in the background comes to the foreground and the application that was in the foreground is forced to the background. This usually occurs when you are changing patients in NextGen® Enterprise while the third-party application is in the background. When this happens, you can toggle back to the NextGen® Enterprise application by using the taskbar at the bottom of the screen. Do one of the following if Loss of Focus interferes with your workflow: Close the third-party application and re-launch it again when needed. - or - Right-click the CCOW icon and then select Break Link. Note: When the CCOW link is broken, the patients no longer synchronize between the applications. Before Breaking the link, ensure that the correct patient is selected. You can reestablish the link by right-clicking on the CCOW icon and selecting Rejoin Link. For more information about CCOW, go to NextGen Healthcare Suc

System Administrator Help

CCOW Workflows

CCOW workflows between NextGen® Enterprise and participating third-party applications operates under the following assumptions: There is no automatic launch into a second application. It is a manual operation. Once a user is logged into an application, the user can manually launch into any other application and will be single signed-on to that application. The setting of patient and user context in the second application follows the CCOW standard and logic. The setting of any patient and user context between NextGen® Enterprise and third-party applications is bi-directional. Using Single/Multiple/Third-Party Applications Workflows Using a Typical CCOW Workflow Parent topic: Clinical Context Object Workgroup (CCOW) Setup

System Administrator Help

Clinical Context Object Workgroup (CCOW) Setup

Clinical Context Object Workgroup (CCOW) is an HL7 standard protocol that enables separate healthcare applications to synchronize in real-time so that each individual application refers to the same patient, encounter or user. This synchronization is called "Context Management." Context Management is a method for making separate clinical applications operate in a unified manner. The CCOW protocol shares the name of the active user between different applications that are operating on the same computer. When CCOW is implemented, a user needs to log onto only one NextGen® Enterprise application. The other NextGen® Enterprise applications functions as if the user is logged onto them as well. NextGen Healthcare supports the receiving and setting of ‘context’ at the following levels: User – Context is defined by mapping user records of perspective NextGen Healthcare and 3rd party applications. Patient – Context is defined by mapping NextGen’s MPI to an EMPI. Note: When CCOW is enabled, a CCOW

System Administrator Help

CCOW Context Management Operation

Subgroup Used in Description Join/Leave Context with Context Manager NextGen® Enterprise PM & NextGen® Enterprise EHR Enables users to break the link or rejoin with the Context Manager. This right does not control breaking the link when the conditional accept message is displayed. For more information about CCOW Context Management, see the NextGen® CCOW white paper. Parent topic: Subgroups of the Operations Permissions Group

Set Up CCOW Security

Recommendations

Use CCOW to Notify the Context Manager

Context Change Scenarios (Sentillion)

Experiencing Loss of Focus with CCOW

CCOW Workflows

Clinical Context Object Workgroup (CCOW) Setup

CCOW Context Management Operation

Use CCOW to Notify the Context Manager

Context Change Scenarios (Sentillion)

Experiencing Loss of Focus with CCOW

CCOW Workflows

Clinical Context Object Workgroup (CCOW) Setup

CCOW Context Management Operation