Using a Typical CCOW Workflow

System Administrator Help

Using Single/Multiple/Third-Party Applications Workflows

Changes that Occur During a CCOW Session Users who only operate a single NextGen Healthcare application Those who only open one part of NextGen Healthcare (such as NextGen® Enterprise EHR, NextGen® Enterprise PM, or NextGen® Document Management) will notice few changes. The most visible changes are: NextGen® Enterprise PM users will no longer be able to right-click on a NextGen® Document Management image in the Clinical History/Notes tab and select Open Image In Doc Mgmt as the choice will be unavailable. NextGen® Enterprise EHR users can no longer open a NextGen® Document Management image in the Category tab and select Open in NextGen Document Management. This option is unavailable during a CCOW session. Users who operate in multiple NextGen® Enterprise applications at the same time, in addition to the changes mentioned above, you will see message pop-ups when changing patients under certain conditions. For example: If a user is working in NextGen® Enterprise EHR or NextGen® Document

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

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

NextGen® Document Management User Guide,

Using NextGen® Document Management with Other Applications

When you open a patient image in NextGen® Document Management while NextGen® Enterprise PM or NextGen® Enterprise EHR is open, the patient chart associated with the NextGen® Document Management image opens in the other application. NextGen® Document Management also displays the image of the active patient. This sequence of actions does not occur when you access NextGen® Document Management with Clinical Context Object Workgroup (CCOW). To synchronize with the active patient, you can select Active Patient from the Tasks menu. From NextGen® Document Management, you can open NextGen® Enterprise EHR demographic and MRN templates. You can access images associated with encounters from the list of encounters that appears in NextGen® Enterprise EHR. You can include images in the workflow. You can right-click a task in the workflow and select the Open Patient's Document option to display the images associated with the task. When you access a patient's chart in NextGen® Enterprise PM, any images

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

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

Using a Typical CCOW Workflow

Recommendations

Using Single/Multiple/Third-Party Applications Workflows

CCOW Workflows

Context Change Scenarios (Sentillion)

Using NextGen® Document Management with Other Applications

Use CCOW to Notify the Context Manager

Clinical Context Object Workgroup (CCOW) Setup

Using Single/Multiple/Third-Party Applications Workflows

CCOW Workflows

Context Change Scenarios (Sentillion)

Using NextGen® Document Management with Other Applications

Use CCOW to Notify the Context Manager

Clinical Context Object Workgroup (CCOW) Setup