NextGen® Document Management and CCOW

NextGen® Document Management User Guide,

Filing Documents to NextGen® Enterprise EHR Encounters

When you file a NextGen® Document Management document to a clinical encounter that is locked in NextGen® Enterprise EHR, you do not need to create an encounter. You can create an addendum to the locked encounter and attach the document to the addendum in NextGen® Document ManagementBy attaching an addendum, you can view the document along with the encounter it belongs to. Note: If the encounter you selected is locked, the application displays a message to indicate that the encounter is locked. You can select Yes to create an addendum to the locked encounter, and then attach the document to the addendum. Parent topic: Using NextGen Document Management with Other Applications

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

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 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

Using a Typical CCOW Workflow

In the typical CCOW workflow, the user is logged into NextGen® Enterprise (alone or with other parts of NextGen Healthcare) and is viewing an office patient. The user wants to look at the third-party application record and so launches the third-party application. When the third-party application launches, the user is automatically signed into the third-party application. If the Sentillion Context Manager is being used, the patient that is visible in NextGen® Enterprise is automatically selected in the third-party application. If the dbMotion Context Manager is being used, the patient that is visible in NextGen® Enterprise is selected in the third-party application only when the user manually instructs the Context Manager to update the third-party patient context. Users might be asked to identify their relationship with the patient, as they normally are in the third-party application, prior to the patient being visible. Alternate workflow (Sentillion) The user is logged into the third-p

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

NextGen® Document Management and CCOW

Recommendations

Filing Documents to NextGen® Enterprise EHR Encounters

Using NextGen® Document Management with Other Applications

Clinical Context Object Workgroup (CCOW) Setup

CCOW Workflows

Using a Typical CCOW Workflow

Using Single/Multiple/Third-Party Applications Workflows

Filing Documents to NextGen® Enterprise EHR Encounters

Using NextGen® Document Management with Other Applications

Clinical Context Object Workgroup (CCOW) Setup

CCOW Workflows

Using a Typical CCOW Workflow

Using Single/Multiple/Third-Party Applications Workflows