clinical procedures (cp) · web viewsection 5.2, creating a flowsheet total, replaced figure 5-10,...

Clinical Procedures (CP)

CLINICAL PROCEDURES (CP) V1.0 FLOWSHEETS MODULE IMPLEMENTATION GUIDE

MD*1.0*26

August 2011

Department of Veterans Affairs Office of Information &Technology (OI&T)Product Development (PD)

(This page intentionally left blank for double-sided printing)

(iv) (Clinical Procedures (CP) Flowsheets Module V1.0 Implementation Guide) (August 2011)

(August 2011) (Clinical Procedures (CP) Flowsheets Module V1.0 Implementation Guide) (iii)

Introduction

Revision History

Date

Description

Authors

April 2011

Patch MD*1*16 Released

REDACTED

April 2011

Added note in section 6.2 regarding legacy devices

REDACTED

July 2011

Added note about TIU Note Title for Reporting field to section 5.1, step 4.

REDACTED

July 2011

Section 5.1, Adding a New Flowsheet: added new step 4 after note, revised step 5.

REDACTED

July 2011

Section 5.3.1, Understanding Totals Display, changed

“median” of all observations to “average “ of all observations.

REDACTED

July 2011

Section 5.2, Creating a Flowsheet Total, replaced figure 5-10, Totals Display from CP Flowsheets. Section 4.1, Importing Views from XML, replaced MD1_0P16_Default_Views.xml with MD1_0P16_Sample_Views.xml. Removed section 5.4.2, Changing the Schedule for a Task.

REDACTED

(This page intentionally left blank for double-sided printing)

(iv) (Clinical Procedures (CP) Flowsheets Module V1.0 Implementation Guide) (August 2011)

(August 2011) (Clinical Procedures (CP) Flowsheets Module V1.0 Implementation Guide) (iii)

Table of Contents

Introduction6Implementation Guide6Product Benefits6CP Gateway Service6CliO Database7Terminology Mapping7CP Flowsheets8CP Console8Intended Audience8CP Console Implementation8Pre-Implementation Planning10General Guidance10Software10Flowsheet Design12Flowsheet Coordinators12Contingency Plans12CP Console Overview14CP Console Menu Bar15File Menu15Tools Menu18Help Menu26CP Console Tree View26CP Console Detail Area27Working with Clinical Flowsheet Views28Importing Views from XML28Customizing Flowsheet Views33Making a Copy34Creating a New Flowsheet View38View Terminology Editor40Adding Terms to a View40Working with Qualifiers43Changing the Display Order of Terms in a View44Modifying Terms in a View44Removing Terms from a View46Creating Flowsheets in CP Console48Adding a new Flowsheet49Adding a View to a Flowsheet50Pages Tab51Editing a View Type in a Flowsheet52Removing a View from a Flowsheet53Changing the Display Order of Views in a Flowsheet53Creating a Flowsheet Total54Editing the Flowsheet Total56Totals Tab57Flowsheet Total58Understanding Totals Display59Setting up Default Shifts60Additional Flowsheet Tasks65Setting up Background Tasks65CliO Cleanup66CP Cleanup66HL7 Cleanup66Adding an Instrument67Modifying an Existing Instrument68Attachment Processing69Adding a Configuration for a Bi-Directional Instrument70Working with Parameters70CP Parameters71Administering Notification Lists72CP ADT Feed Configuration73Current ADT Targets74Adding an ADT Target74CP Gateway Service Configuration75VistA Server Settings76Gateway Server Settings76Working with Procedure Information77Adding a Procedure78Modifying an Existing Procedure79Procedure Definitions80Allowable Instruments81Working with the Procedure Worksheet81Adding Allowable Instruments82Shortcut Keys84Glossary87Index96

1. Introduction

1.1. Implementation Guide

The Implementation Guide provides technical information for the implementation of the Clinical Procedures Flowsheets Module. This document provides guidance for Information Resource Management (IRM) technical personnel, Clinical Application Coordinators (CACs), and Flowsheet Coordinators to implement and operate the software. More information can be found in the Clinical Procedures (CP) V1.0 Flowsheets Module User Manual.

1.2. Product Benefits

The Clinical Flowsheets patch of the Clinical Procedures (CP) package provides an electronic representation of the traditional paper flowsheet maintained during each inpatient stay. Vitals, Intake/Output, and Wound Documentation are examples of data types that can be recorded via Clinical Flowsheets into the Veterans Health Information System and Technology Architecture (VistA) system. Clinical Flowsheets provides a departure from its predecessor applications by storing collected information as discrete data. Some date elements, such as vital signs, are available to the Vitals Package and Computerized Patient Record System (CPRS). Various reports built on the other data elements are available for CPRS in the form of Text Integration Utilities (TIU) Notes. Additionally, flowsheets is a tool that can be used by clinicians to standardize assessment templates.

There are two ways to enter data into Clinical Flowsheets: manually and via Health Level 7 (HL7) messaging. Any instrument or external system capable of sending HL7 messages can be considered a source of data for Clinical Flowsheets (provided that the HL7 messages conform to Clinical Flowsheets requirements).

Clinical Flowsheets uses VistA Data Extraction Framework (VDEF) support, HL7 messaging, and the CP Gateway service to notify the medical device of the patient’s admission, discharge, and transfer.

MD*1.0*16 consists of the following three windows executables components and one Kernel Installation & Distribution System (KIDS) build:

CPConsole.exe

CPFlowsheets.exe

CPGatewayService.exe MD1_0P16.KID

1.2.1. CP Gateway Service

The CP Gateway Service is the component that processes HL7 messages.

The CP Gateway Service is composed of two subsystems, one existing solely within VistA, and the other existing as a Windows service that interacts with VistA via the Remote Procedure Call (RPC) Broker. A vendor device sends an observation to VistA inside an HL7 (ORU^R01) inbound message. The message is received by the VistA HL7 system, the patient and device are validated, and it is then forwarded to the Windows-based CP Gateway Service subsystem.

The VistA CP Gateway Service subsystem parses and validates the patient-identifying information and the device identifier. If the patient information and device identifiers are valid, the Windows service is notified that there is a message waiting to be processed in VistA. The Windows service calls into VistA via the RPC Broker to retrieve the HL7 message. The Windows service then parses and validates the observation data and saves the validated information in the Clinical Observations database (CliO) data store.

A Microsoft Windows service was used so that, in the next iteration of CliO, it will be possible to build in the ability to parse and decode images encoded in HL7 messages. Using a Microsoft Windows service also allows the processing of observational data to be offloaded to a second processor, allowing the primary listening process in the HL7 subsystem in VistA to be more responsive.

(VistAValidates PatientIdentifying Information and determines message sourcedevice IDCliOParsed observational informationNotificationof available dataORU^R01Retrieves data and terminologyHL7 Gateways and 3rd party devicesCP Gateway ServiceVistA HL7 subsystem and CP routines)Parses observational information. Ultimately, will parse and translate images in subsequent iteration.

Figure 1-1 CP Gateway Service

For more information about the CP Gateway Service, refer to the CP V1.0 Flowsheets Module Installation Guide.

1.2.2. CliO Database

The CliO database provides a standardized terminology data store for all clinical observations throughout the Department of Veterans Affairs (VA).

1.2.3. Terminology Mapping

The CP Gateway Service provides extensive terminology mapping which translates proprietary labels so the information is understood to represent the same thing and, thus, be stored appropriately. Devices do not always use the same terms to describe the data they transmit. For example, one device may use the term “heart rate,” while another may transmit the same information as “pulse.” This mapping is more efficient than trying to compel each medical device vendor to conform to using standard terminology.

Similarly, CP Flowsheets can display the data to the user using the terminology that is preferred at a given unit or medical center. A flowsheet used by an MICU unit at one hospital can be customized to display

“Heart Rate,” while a flowsheet used by a step-down unit may display “HR” or “Pulse.”

(Introduction)

(Introduction)

(8) (Clinical Procedures (CP) Flowsheets Module V1.0 Implementation Guide) (August 2011)

(August 2011) (Clinical Procedures (CP) Flowsheets Module V1.0 Implementation Guide) (7)

1.3. CP Flowsheets

CP Flowsheets provides an electronic representation of the traditional paper flowsheet. This user- friendly, customizable Graphical User Interface (GUI) provides functionality for data entry, validation and editing, as well as patient management.

Flowsheets provides electronic flowsheets that can be custom designed for any clinical area of a Medical Center.

Flowsheets is a tool that can be used by clinicians to standardize assessment templates nationwide.

Flowsheets provides the ability to report discreet observations data combined with progress notes. Flowsheets creates a complete audit trail of patient documentation.

1.4. CP Console

CP Console provides the tools to build the flowsheet views and layouts that are used for patient care, for recording vital statistics as necessary. It also provides a means for configuring the CP Gateway Service, assigning permissions to CP Flowsheets users, and system administration.

1.5. Intended Audience

This Implementation Guide is intended for use by Information Resource Support personnel, CACs, and Flowsheet Coordinators. End users should be familiar with the following:

Windows operating systems CPRS functionality

1.6. CP Console Implementation

CP Console is the administration dashboard for implementing and maintaining Clinical Flowsheets and devices for Clinical Procedures. Information Resource Management (IRM) should grant the site ‟s flowsheet coordinator the MD ADMINISTRATOR key. CP Console is then used to set up views, flowsheets, flowsheet totals, instruments, shifts, scheduled cleanup of unused files, and all the other administrative tasks to customize the application for their site.

This page intentionally left blank for double-sided printing



2. Pre-Implementation Planning

2.1. General Guidance

To begin the pre-implementation planning, it is recommended that Medical Center Management support a Clinical Flowsheets Focus Group comprised of representatives from the Chief of Staff’s office, IRM, Nursing, Labor Management, Quality Management, Health Information Management Service (HIMS) and Biomedical Engineering. The focus group would discuss the order of implementation in the facility, new process and procedures for documenting using electronic flowsheets, as well as the third party vendor devices, such as bedside monitors and Clinical Information Systems that may be used in/purchased for Critical Care areas. Additionally, this group would drive the design of the flowsheets as this is site configurable.

This software can be implemented one unit at a time. As with any new software, new processes and procedures are required. For Clinical Flowsheets to be effective and successful, all transactions need to be entered and documented electronically.

2.2. SoftwareThe CP Clinical Flowsheets product, MD*1*16, was released with the following components:

File NameContents

MD1_P16.KIDMD*1.0*16 KIDS Build

MD1_0P16_Sample_Views.xmlSample Views MD1_0P16CPGatewayServiceSetup.exe MD*1.0*16 CP Gateway Service setup file MD1_0P16_EXES_AND_DOC.zip 12 files indented below

-CliO_Terminology.docMD*1.0*16 Clinical Flowsheets Terminology file

-CPConsole.cntMD*1.0*16 CP Console online Help contents file

-CPConsole.exeMD*1.0*16 CP Console Executable

-CPConsole.hlpMD*1.0*16 CP Console online Help file

-CPGatewayService.exeMD*1.0*16 CP Gateway Service Executable

-MD_1_P16.KIDMD*1.0*16 KIDS Build

-MD_1_P16_IG.pdfMD*1.0*16 Clinical Procedures (CP) V1.0 Flowsheets Module

Installation Guide

-MD_1_P16_IMPG.pdfMD*1.0*16 Clinical Procedures (CP) V1.0 Flowsheets Module

Implementation Guide

-MD_1_P16_RN.pdfMD*1.0*16 Clinical Procedures (CP) V1.0 Flowsheets Module

Release Notes

(Pre-Implementation Planning)

Pre-Implementation Planning

-MD_1_P16_TM.pdfMD*1.0*16 Clinical Procedures (CP) Technical Manual and Package Security Guide

-MD_1_P16_UM.pdfMD*1.0*16 Clinical Procedures (CP) V1.0 Flowsheets Module

User Manual

-RoboEx32.dll.DLL file required to access Help files MD1_0P16_Flowsheets.zip(includes the 4 files indented below) Note: This file is available upon request from the implementation team.

-CPFlowsheets.exeMD*1.0*16 CP Flowsheets Executable

-CPFlowsheets.hlpMD*1.0*16 CP Flowsheets online Help file

-CPFlowsheets.cntMD*1.0*16 CP Flowsheets online Help contents file

-RoboEx32.dll.DLL file required to access Help files

Upon release of the CP Clinical Flowsheets product, the sites have three choices:

a. If the site is not currently running Clinical Procedures, only the KIDS build needs to be installed. All other installation instructions and post-installs can be ignored.

b. If the site is running Clinical Procedures and does not plan on implementing Clinical Flowsheets at this time, only the KIDS and CP console (replacement for CP Manager) need to be installed.

Note: Once you install the KIDS and CP console components, CP Manager will not function.

c. If the site is running Clinical Procedures and chooses to begin the implementation of Clinical Flowsheets, then all four components need to be installed: KIDS, CP Console, CP Flowsheets and the new CP Gateway service.

d. Once the decision is reached to begin the implementation of Clinical Flowsheets, the applications coordinator for this product will need to notify their Information Resource Management (IRM) service and verify what level of implementation they are at for Clinical Procedures. IRM will need to apply the CP Console and/or CP Gateway Service as applicable depending on their current status.

The CP Flowsheets.exe is not included within MD*1*16 as this executable is an optional and controlled roll out, managed by the Implementation Manager. A readiness checklist will be provided by the Implementation Manager when the site requests the CP Flowsheets.exe.

To request the CP Flowsheets.exe, contact VA OIT OED ClinProc Implementation Support.

2.3. Flowsheet DesignThe CP Console provides the tool to build the flowsheet views and layouts. In the pre- implementation phase, a copy of the current paper flowsheet should be reviewed. The design of the electronic flowsheets can then be established based on the review.Sample Views are available for import. A copy of these views can be made once imported onto your system, and the copy can then be edited so that it is customized for your facility. You can also create a view from scratch.CP Flowsheets are built from the CP Views. You can apply the same view to many flowsheets. It is important to remember this because if an edit is done on a CP View, that edit will be reflected on all the CP flowsheets that have that CP view assigned.

2.4. Flowsheet CoordinatorsThe facility will need to determine who will have access to build the views and flowsheets. IRM will need to assign permissions as requested. Additional information about permissions is available in Chapter 3: CP Console Overview.The Flowsheet Coordinator should be given the MD ADMINISTRATOR key, which will give them permissions to all needed functions.

The Flowsheet Coordinator has the following key responsibilities: Manages and facilitates installation, implementation, maintenance, enhancements and overall use of CP Flowsheets throughout the medical center through ongoing needs assessments and evaluation processes. Serves as site coordinator for implementation and development teams at the facility level, including communication of issues with the executive stakeholders and program team to achieve resolution Serves as a liaison to the VISN and national level teams for the CP Flowsheet application, to include facility representation at conference callsand/or educational programs. Coordinates and ensures initial and ongoing training for all CP Flowsheet users, including students, and temporary staff. Coordinates and ensures initial and ongoing usability assessments for the CP Flowsheet application and hardware systems. Facilitates initial and ongoing contingency system management.

2.5. Contingency PlansContingency procedures should be developed for scheduled and unscheduled downtime and coordinated with stakeholders prior to the implementation of the software. All applicable staff will need to be trained on the contingency plans.

(Pre-Implementation Planning)



This page intentionally left blank for double-sided printing

3. CP Console Overview

CP Console is a replacement for CP Manager.

The CP Console window contains the following elements: Menu Bar

Button Bar Detail Area Tree View

Figure 3-1, CP Console Window

Note:MD*1.0*16 disables the use of CP Manager. Use CP Console to perform the functions previously provided by CP Manager.

(Customizing Flowsheets)



3.1. CP Console Menu Bar

The CP Console Menu bar appears along the top of the window, under the Windows title bar. It contains three menu options: File, Tools, and Help.

3.1.1. File Menu

Figure 3-2, CP Console Menu Bar

Use the File menu to add new items, rename existing items, delete items, save items, and exit CP Console.

Figure 3-3, File Menu

3.1.1.1. New Menu

The New menu option allows you to create new flowsheets, flowsheet views, flowsheet totals, schedules, and shifts, as well as add instruments and procedures.

Figure 3-4, New Menu




3.1.1.2. Renaming an Item in the Tree View

Use Rename to change the name of an item in the tree view. To rename a flowsheet, a flowsheet total, a flowsheet view, an instrument, a procedure, or a shift, complete the following steps:

1. In the CP Console tree view, select an item. The worksheet for that item appears.

2. Click File and select Rename. The Rename pop-up appears.

Figure 3-5, Rename Flowsheet

3. Type a new name.

4. Click OK. The new name appears in the tree view.

3.1.1.3. Deleting an Item

Use the Delete option to remove an item from the tree view. To delete a flowsheet, a flowsheet total, configuration parameters, or a shift, complete the following steps:

You can also delete items from the CP Console button bar.

Figure 3-6, CP Console Button Bar

Note: Since a Flowsheet is simply a data entity form, deleting a Flowsheet does not give you the ability to delete patient data,. If you remove a term, view, or flowsheet, data still exists but is no longer viewable within Flowsheets.

1. In the CP Console tree view, select an item. The worksheet for that item appears.

2. Click File and select Delete. The Confirm pop-up appears.

Figure 3-7, Confirm Delete

3. Click Yes. The item is removed from the tree view.

Note: From the File menu, you can select Save to retain your additions and changes.

4. Select Exit to close CP Console.

3.1.2. Tools Menu

Use the Tools menu to locate items, assign permissions, refresh user roles, and export and import flowsheet views.

Note: If you make a change in CP Console, you will not see the change until you reload the Flowsheet.




3.1.2.1. Search

Figure 3-8, Tools Menu

On the Tools menu, click Search to look for an item in CP Console, such as a view, instrument, or procedure. Use the Console Find It Utility to perform your search.

Figure 3-9, Console Find It Utility

3.1.2.2. Working with User Permissions

Use the Permissions option to add, remove, and modify users to items in the Tree view (i.e. View, Flowsheet, etc.) of Flowsheets and assign permissions (access) to those items. Any user with the MD ADMINISTRATOR key can assign permissions to any of the items in CP Console. Other users can assign permissions only to the items that they own/control. Security keys assigned to each user determine the overall access they have to CP Console (Refer to the Refresh Roles section for more details).

Assigning permissions is a way of giving access to a user who would otherwise not have access to a specific item in the Tree view.

Note: You need MD ADMINISTRATOR to assign any permission to any object or you need to have full access granted to you for items you are assigning to another person.

Highlight the item in the Tree view that you want to give another user permission to configure.

On the Tools menu, click Permissions or click the Permissions button. The Access Control List Manager appears and displays the users and permissions for the highlighted item.

Figure 3-10, Access Control List Manager

Use the Access Control List Manager to add users and their permissions, to change permissions, and to remove users. The Access Control List Manager offers a choice of four permissions that you can assign to a user:

Read-Only - can only read items (default)

Read-Write - can read, edit, and save items

Read-Write-Delete - can read, edit, and save items, as well as delete some items

Full Control - can do everything, which includes adding and removing users

3.1.2.3. Adding a User and Permissions

Use the Access Control List Manager to add users and permissions. To add users and permissions for an item in the Tree view:

1. Select the item from the Tree view.

2. On the Tools menu, click Permissions or click the Permissions button. The Access Control List Manager appears.

3. Click Add. The Person Lookup pop-up appears.

Use the Person Lookup to locate the user you want to add or remove, or change the user’s permissions.

Figure 3-11, Person Lookup

4. On Person Lookup, type a letter or two in the Name box.

5. Click Search.

6. Select a user from the Select One list.

7. Click OK.

8. Highlight the user in the Users list.

9. Select an option from the Permissions list.

10. Click Update.

11. Click OK.

3.1.2.4. Changing a User Permission

Use the Access Control List Manager to change the permissions of users. To change permissions for an item on the Tree view:



3. Select a user from the Users list.




4. Select an option from the Permissions list.

5. Click Update.

6. Click OK.

3.1.2.5. Removing a User Permission

Use the Access Control List Manager to remove users. To remove a user for an item on the Tree view:



3. Select a user from the Users list.

4. Click Remove.

5. Click OK.

3.1.2.6. Refresh Roles

Refresh Roles retrieves the current role (security key) assignments in VistA for the current user and displays them.

To refresh roles, complete the following steps:

1. From the Tools menu, select Refresh Roles and the Information pop-up appears with the roles assigned to the item selected.

Figure 3-12, User Roles Assigned to Selected Item

MD ADMINISTRATOR – CP Console requires the VistA MD ADMINISTRATOR role to create items in CP Console. The MD ADMINISTRATOR role includes MD MANAGER abilities with additional capabilities. CP Flowsheets requires the VistA MD ADMINISTRATOR role or the MD HL7 MANAGER role to access the HL7 Monitor. This role allows the holder full control of CP Flowsheets. Assign this role to users responsible for setting up and maintaining CP Console and CP Flowsheets.

MD MANAGER – This role allows the holder to edit, audit, or rescind someone else’s data. Assign this role to power users of the CP Flowsheets patch to give them enhanced capabilities over a basic Flowsheets user.

MD HL7 MANAGER - CP Flowsheets requires the VistA MD HL7 MANAGER role or the MD ADMINISTRATOR role to access the HL7 Monitor. Assign this role to a user who will assist with the HL7 messaging component of CP Flowsheets.

MD READ-ONLY – Assign this role to a user to prevent them from entering data in Flowsheets. DO NOT assign MD READ-ONLY to a user concurrently with any role other than MD HL7 MANAGER. Doing so will lead to unpredictable results. A user with the MD READ-ONLY key may NOT log on to CP Console and will have limited functionality in CP Flowsheets.

MD TRAINEE - This role has the same capabilities as a basic user except that all observations are unverified; a user who is not a trainee must verify all trainee observations. Assign this role to trainees.

3.1.2.7. Export to XML

Export to XML allows you to save your Instruments, Procedures, or Views to a disk as a backup of your flowsheet layouts. This allows administrators to share views or Flowsheets with other users or sites. To export to XML, complete the following steps:

Note:You must be assigned the role of MD ADMINISTRATOR to use this function.

1. On the CP Console Tools menu, click Export to XML. The CP Console Export Wizard appears.

Figure 3-13, CP Console Export Wizard

2. Click Next. The CP Console Export Wizard asks you to select the type of items to export.




Figure 3-14, CP Console Export Wizard Select Type

3. Select Instruments, Procedures, or Views and click Next. The CP Console Export Wizard asks you to select the instruments, procedures, or views to export.

Figure 3-15, CP Console Export Wizard

4. Select the instruments, procedures, or views you want to export (in this example, instruments are being exported). You may select as many as you wish. You may press Ctrl-A to select all of the

instruments, procedures, or views. Click Next. The CP Console Export Wizard asks you to enter or select the name of the file to export the selected instruments, procedures, or views.

Figure 3-16, Export Filename and Comments

5. Export Filename and Comments.

e. Enter the name of the export file. To change the location where the file will be saved, click

Browse and select the location. Or:

To replace an existing file with the new export file, or click Browse and select the file to replace. Click Yes when prompted to replace the file.

f. Optionally, you may add comments in the Comments box. Comments submitted in the Export Wizard will appear in the Import Wizard before you finish importing your views. These will be included in the XML export file.

g. Click Next. The CP Console Export Wizard displays a preview of the XML file.




Figure 3-17, CP Console Export Wizard File Preview

6. You can scroll to review the XML file. To export the file, click Next.

Figure 3-18, CP Console Export Wizard Success

7. When the export is complete, click Finish.

3.1.2.8. Import from XML

You can import Sample views such as a method to share between sites.

3.1.3. Help Menu

The Help menu provides information about the application and access to online Help.

Figure 3-19, Help Menu

From the Help menu, select About to display information specific to the CP Console application. Select Contents to display online Help for CP Console.

3.2. CP Console Tree View

In the left-hand panel, the CP Console tree view provides access to the following items: Background Task, Flowsheet, Flowsheet Total, Flowsheet View, Instrument, Parameters, Procedure, Schedule, and Shift.

Figure 3-20, CP Console Tree View




3.3. CP Console Detail Area

When you select an item in the CP Console tree view, details for that item appear in the large panel to the right. This is the worksheet where you create, customize, and fine-tune your flowsheet views, flowsheet layouts, and so on.

Figure 3-21, Item Detail Area

The banner appears at the top of every detail area, indicating the name you assign to the item, the type of item you are creating or modifying (flowsheet, view, total), as well as the access level.

4. Working with Clinical Flowsheet Views

The following section details the basic tasks available within CP Console. To get started, you will need the following:

You must have the MD ADMINISTRATOR key Access to the CP Console executable

Menu Option MD CLIO must be assigned Within CP Console, you can complete the following tasks:

Import Sample Views

Customize Flowsheet Views Create a Flowsheet

Add, Edit, or Remove a view from an existing flowsheet

(IMPORTANT: If you are importing views from a different site, you need to copy and rename them. See Renaming a Copied View for more details.)

See Also – Importing Views from XML, step 6. If you click yes to the CP Console Import Wizard Confirm Warning message, your imported view will be overwritten. Make sure that you make a copy of the existing view to retain its contents.

4.1. Importing Views from XML

Sample Views for Flowsheets are available for download. You can copy sample views as a starting point for creating custom views. They are available on the anonymous FTP site as MD1_0P16_Sample_Views.xml . Contact your local IRM Support to retrieve this file from the designated FTP server.

You can also follow these steps to import custom views.

1. On the CP Console Tools menu, click Import from XML. The CP Console Import Wizard appears.




Figure 4-1, CP Console Import Wizard

2. Click Next. The CP Console Import Wizard asks you to enter or select the name of the file to import.

Figure 4-2, CP Console Import Wizard Import Filename

3. Enter MD1_0P16_Sample_Views.xml, or click Browse and select the file to import. The CP Console Import Wizard displays the file header.

Figure 4-3, CP Console Import Wizard File Header

4. Click Next. The CP Console Import Wizard asks you to select the components to import.

Figure 4-4, CP Console Import Wizard Select Components

5. Press Ctrl-A to select all of the components. Click Next.




6. If you import a view that has a Flowsheets view internal number that is the same as a view that already exists in CP Console, the imported item will overwrite the existing item. The CP Console Import Wizard displays a confirmation box to confirm that you want to overwrite the existing item.

Figure 4-5, CP Console Import Wizard Confirm

WARNING! If you click Yes, it will overwrite the existing item. To import a view and still retain the existing item, before you import the new item, make a copy of the existing item (refer to the Making a Copy section for more details), then import the new item. The import will still overwrite the original item, but it will not overwrite the copy.

Note:Sample Views are read-only and cannot be changed.

To confirm the import of the item, click Yes. To retain the existing item and cancel the import of the new item, click No.

If you are importing more than one item that has a Flowsheets internal ID that is the same as a view that already exists in Flowsheets, the CP Console Import Wizard will display a confirmation box for each item.

7. During the import, the CP Console Import Wizard displays a progress report of the components as they are imported.

Figure 4-6, CP Console Import Wizard Progress Report

8. When the import is complete, click Finish.

Figure 4-7, Close Application Confirmation

9. To apply the changes, you must restart CP Console. To close CP Console, click OK.

After you complete the import and restart CP Console, the views you imported are now available under the Flowsheet View folder as shown below.

Note: the views you import will be in an “Inactive” status. These views will need to be “Active” before they are available for use.




The following figure shows what the imported sample views will look like:

Figure 4-8, Imported Views

4.2. Customizing Flowsheet Views

In order to customize the views for your site, complete the following tasks: Make a copy of a sample view

Rename a copied View

Edit renamed views

Important: When you are editing a Flowsheet view, you should reload a flowsheet if it has been edited in the console, or close the flowsheet if it is currently being edited. Otherwise, editing a view in CP Console can cause other open flowsheets that use that view to show an error.

4.2.1. Making a Copy

Make Copy allows you to copy a flowsheet view. The new view will have a Flowsheets internal ID that is different from the view that you copied. This is especially useful when you are customizing views that you have imported.

Note:If you rename an imported view, it does not change the Flowsheets internal ID and the renamed view could still be overwritten. If you Make a Copy of a view, it is assigned a new Flowsheets internal ID and will not be overwritten later by an imported view.

1. In the CP Console tree view, select a view. The worksheet for that view appears.

2. On the File menu, click Make Copy or click the Make Copy button. The Confirm Copy pop-up appears.

Figure 4-9, Confirm Copy

3. Click Yes. The copied view appears in the tree view.




Figure 4-10, Copied View

4. The view you just created is listed in the tree view with the name of “Copy of” prepended to the name of the view you copied.

4.2.1.1. Renaming a Copied View

After you copy a view, rename the view you just created. To rename a copied view, complete the following steps:

1. From the buttons at top of the CP Console menu, click Rename.

Figure 4-11, Rename Button

2. The Rename Flowsheet window appears.

3. In the New Name field, rename your flowsheet view.

Figure 4-12, Rename Flowsheet

4. Click OK.

5. The renamed Flowsheet View will now appear in the Flowsheet View tree list.




4.2.1.2. Protecting an Imported or Exported View

The following flow diagram illustrates steps you can follow to protect an imported or exported view.

Figure 4-13, Protecting an Imported or Exported View

4.2.2. Creating a New Flowsheet View

If you choose not to copy a view, you can create your own view using the following steps.

You can create views specific to your site to assemble into your customized flowsheets. You can create an unlimited number of views. A flowsheet view is comprised of terms, parameters, and qualifiers. You can assemble one or more flowsheet views into a flowsheet that you use for entering patient data into CP Flowsheets. A customized flowsheet view allows you to add, edit, and remove terms, as well as change the display order of the terms.

To create a flowsheet view:

1. From the File menu, highlight New and select Flowsheet View. The Create New Flowsheet View pop-up appears.

Figure 4-14, Create New Flowsheet View

2. In the Name box, type a name for the new view. The name appears in the tree view and as the Item Name at the top of the CP Console main window.

3. Click OK. The new Flowsheet View worksheet appears.

Figure 4-15 Flowsheet View Worksheet




The name you just added appears in the Display Name box.

4. From the Time Interval list, select a time interval to display across the y-axis (columns).

5. From the X-Axis list, select a list, Terminology or Date/Time, to display across the x-axis (rows).

6. Optional: In the Comment box, type additional information about the view.

7. To make the view available in CP Flowsheets, select the Active check box.

8. To be able to switch axes, the intervals (columns) with the lists (rows), select the Allow Pivot check box.

9. Click Save to save your new Flowsheet View.

Flowsheet View Definitions

The following are definitions specific to Flowsheet Views:

Display Name: Display Name describes the flowsheet view with a unique name, so you can identify it in the list of flowsheet views.

Time Interval: Time Interval sets the default time interval for the view display when accessed through CP Flowsheets. Choices range from one minute to 24 hours.

X-Axis: X-Axis sets the column headers along the top of a view to Date/Time or Terminology selections.

Y-axis represents data type (rows) along the left side of a view.

Comment: Optional – You can provide additional information regarding the flowsheet view.

Active: The flowsheet view is active and available in CP Flowsheets.

Select the Active check box to make the flowsheet view active and available. Clear the Active check box to inactivate the flowsheet view.

Note:If the Active check box is not selected, the view does not load and you cannot enter data.

A pop-up appears to indicate that the view is not active. The inactive view may display in the report.

In the tree view, an active view appears with .

Figure 4-16 - Active View

Allow Pivot: Allow Pivot switches the x-axis (column) selection to present along the y-axis (row) of a view. You can make the switch while using the flowsheet.

Select and clear the check box to change the default view of the flowsheet view.

4.2.3. View Terminology Editor

Display Name: You assign a name to the view that appears in CP Flowsheets on your flowsheet.

Use the View Terminology Editor window to add terms (click Add) and to modify existing terms (click

Edit).

Figure 4-17, View Terminology Editor

4.2.4. Adding Terms to a View

Use the View Terminology Editor window to add terms to a view. To add terms to a view:

1. Click on the view you would like to modify.

2. Click . The View Terminology Editor window appears.





3. From the Term drop-down list, select a term.

Note:The Term list contains terms provided with CP Console. You cannot add terms to the CP Console list. If you need to request or modify a term, refer to the following site for Terminology information:

http://vista.med.va.gov/clinicalspecialties/clinproc/newTerm.asp

4. To set the default unit of measurement, if the selected term requires a default unit, select a unit from the Default Unit drop-down list.

For Example:

Body temperature is always entered in degrees Fahrenheit. Select Degrees F from the drop-down list. The end user does not need to select Degrees F every time they enter a temperature.

5. Optional: Change the display name.

The Display Name automatically populates when you select a term.

6. To set a display width, select a width (in number of characters) from the Display Width drop-down list.

7. To set the display columns, if the selected term requires columns, select the number of columns to display from the Display Columns drop-down list.

8. Select the Use Dropdown check box to display the selections in a flowsheet in a drop-down list rather than as radio buttons.

9. From the Term Display Properties box, select one or more check boxes to provide calculations automatically in the view:

Display Totals Row

Display Average Row Display Count Row Display Min Value Row Display Max Value RowDisplay Subtotals by Time Interval Display Row as Read OnlyInput required for this term

Refer to the following section, Term Definitions for further detail on the above terms.

10. If the term you select has qualifiers associated with it, you need to make additional selections. Not all terms have qualifiers.

a. Select one or more check boxes of the available qualifiers.

b. Select descriptors for the qualifiers from the respective drop-down lists.

c. Select the appropriate Mandatory check boxes to make qualifiers required fields.

For Example:

Weight has three qualifiers available: Method, Location, and/or Position. Define a method for taking the weight, by selecting a descriptor.

11. Click OK.

12. Click Save.

13. To add additional terms to a view, repeat steps 1-11.

4.2.4.1. Term Definitions

The Term section allows you to customize the term parameters and associated qualifiers.

Term: Term is the approved, standardized wording used for the observed clinical procedure/activity.

Default Unit: Default Unit is the unit of measure at which to set the default.

You must select a default unit for a numeric unit.

Example

Body temperature is always entered in degrees Fahrenheit. Select Degrees F from the drop-down list. Then you do not need to select Degrees F every time you enter a temperature.

Display Name: Display Name describes the selected term with a unique name, so you can identify it in the list of terms.

Display Width: Display Width is the maximum number of characters used in the field.

Display Columns: Display Columns is the number of columns to display in the view.

Use Dropdown: Use Dropdown allows you to display selections in a flowsheet in a drop-down list rather than a radio button options.

Display Only: Display Only prevents you from manually adding data for the observations.




Term Display Properties: You can select one or more properties for the selected term to provide calculations automatically for display in the view.

Display Totals Row–provides a totals row for observations for display in the view

Display Average Row–provides an average row for the observations for display in the view Display Count Row–provides a count row for the observations (the number of results in a particular column) for display in the view

Display Min Value Row–provides a minimum value row, a row of the lowest number of observations

Display Max Value Row–provides a maximum value row, a row of the highest number of observations

Display Subtotals by Time Interval–provides subtotals by time intervals (calculations automatically by time intervals) for the observations for display in the view

Display Row as Read Only–allows a row to be labeled read only for display in the view

Input required for this term–indicates whether the term must have observations recorded

4.2.5. Working with Qualifiers

A qualifier is an additional choice you can add to a term, such as the examples below. Not all terms have qualifiers. A term can have several qualifiers as specified in the terminology list. Those that display depend on the term you select. If the term you select has qualifiers associated with it, you can make additional selections.

Identify the type of qualifier by selecting the associated check box, such as: Method–lift scale, monitor

Quality–actual, estimated Location–L arm, right upper lobe Position–sitting, standing Product–platelets, 5 percent albumin

Indicate that a qualifier is a required field by selecting a Mandatory check box.

If a qualifier is set to Mandatory, you cannot clear the qualifier from the flowsheet view data entry form.

Note:You can clear the qualifiers that are not mandatory with the ESC key.

Select a descriptor for the type of qualifier from the respective drop-down list.

When you do not select a qualifier, no default appears in the qualifier drop-down. When you select a qualifier, it appears in the drop-down as an editable default.

When you select a qualifier and select mandatory, the qualifier appears in the drop-down and you cannot change it.

For Example:

Systolic Pressure has three qualifiers available: Method, Quality, and/or Position. Define a method for reading systolic pressure by selecting one or more of the qualifiers with associated parameters.

For information on creating a flowsheet view, refer to the Creating a Flowsheet View section in Chapter 4.

4.2.6. Changing the Display Order of Terms in a View

Use Move Up and Move Down to change the display order of the terms in a view. To change the display order of terms in a view:

1. Highlight the term you want to move in the display order of the view.

2. Click to move the term up in the display order or click to move the term down in the display order.

3. Click Save.

4.2.7. Modifying Terms in a View

Use the View Terminology Editor window to modify the term qualifiers and associated descriptors of the terms of newly created views, as well as existing views. To edit terms in a view:

1. Highlight a term from the Terminology list.

Figure 4-19, Terminology List

2. Click . The View Terminology Editor window appears.





3. Change any or all of the parameters in the Term section.

4. If the term has qualifiers, change any or all of the qualifiers/descriptors in the Qualifiers section.

5. Click OK.

6. Click Save.

7. To edit additional terms in existing views, repeat steps 1-6.

4.2.8. Removing Terms from a View

Use Remove to delete terms from a newly created or existing view. To remove terms from a view:

1. From the Terminology list, highlight a term.

Figure 4-21, Terminology List

2. Click . Confirm pop-up appears.

Figure 4-22, Confirm Pop-up

3. Click Yes.

4. Click Save.

5. To remove additional terms from a view, repeat steps 1-4.




This page intentionally left blank for double-sided printing.

5. Creating Flowsheets in CP Console

CP Console allows you to create flowsheet views and flowsheet totals, which you assemble into your individualized flowsheets to meet your site-specific requirements. Although the order in which you create the parts of a Flowsheet is not critical (you may use some sample flowsheet views and totals supplied with Flowsheets), you must have the following components to create a Flowsheet.

Flowsheet view(s), including sample flowsheet views supplied with Flowsheets, that contain the information you want to include on your Flowsheet. Before publishing a Flowsheet, you must find or create the flowsheet views you wish to include on your Flowsheet.

Flowsheet total(s) including sample flowsheet totals supplied with Flowsheets, that contain the information you want to include on your Flowsheet. Before publishing a Flowsheet, you must find or create the flowsheet totals you wish to include on your Flowsheet.

To create a Flowsheet in CP Console, complete the following steps:

1. From the File menu, highlight New and select Flowsheet. The Create New Flowsheet pop-up appears.

Figure 5-1, Create New Flowsheet

2. In the Name box, type a descriptive name for the new flowsheet, for example ICU_VITALS or NHCU_VITALS. The name appears in the tree view and as the Item Name at the top of the CP Console main window.

3. Click OK. The new Flowsheet worksheet appears.




Figure 5-2, New Flowsheet Worksheet

Note:Not all users have permissions to create or edit Flowsheets. Refer to the Permissions

section for more information.

5.1. Adding a new Flowsheet

To add a new flowsheet:

1. In the Display Name box, type a name for the new flowsheet.

2. To make the flowsheet available in CP Flowsheets, select the Active check box.

3. Optional: In the Comment box, type additional information about the flowsheet.

Note: This comment is only visible in CP Console.

4. Make sure an appropriate TIU title exists and is active in CPRS.

5. From the TIU Note Title for reporting list, select a note title to display in CPRS.

Note: Selection is most accurately done by copying the TIU note title from CPRS or Vista or paste the title onto a text page, for example, Notepad or MSWord. Copy and paste the title name into the General section - "TIU note title for reporting".

You have the option to QUICKLY type the first 3-4 characters of the TIU note title. However, if you have several note titles that start out with the same 3-4 characters such as NURS, this could cause your system to lock up. Therefore, it is recommended that you copy and paste note contents.

6. Click Add. The New Flowsheet Page window appears.

5.1.1. Adding a View to a Flowsheet

Use the New Flowsheet Page window to add a view to a new or existing flowsheet. To add a view to an existing flowsheet:

1. Select the Pages tab and click . The New Flowsheet Page window appears.

Figure 5-3, New Flowsheet Page

2. Select a view from the View drop-down list.

Note:The View list contains the flowsheet views you created under Flowsheet View in CP Console, along with any default flowsheet views created by the development team.

3. The Display Name automatically populates when you select a view. If you change the display name, the view name changes in CP Console, and appears as Page Name in a new session of CP Flowsheets.

4. Select a type from the Page Type options: Mandatory, Optional, or Supplemental (defined below)

Mandatory – mandatory views cannot be closed

Optional – the optional view is not always displayed. Optional views can be added one at a time (for example, ventilator or pacemaker) and can be turned on or off as necessary and continue to be used with no loss of data.

Note: An optional view is configured to document assessments related to singular non-invasive device types where documentation flow is suitable to follow on a continuum with the original entry.

The optional view is added for initial documentation for a number of hours/days. The view can be closed after the device is discontinued. If the device is later placed back into use, adding the optional view again re-activates the original view for continuing documentation.

If you are tracking usage of model numbers, lot numbers, or invasive lines, then configure device assessments in a supplemental view.

Supplemental – you can use the view, but it is not necessary for all flowsheets; a supplemental view does not display initially, you have to add it to the flowsheet. You can use multiple supplemental views (for example IV bags or multiple wounds). If you close a supplemental view and add a new one, the new one will be blank. The data is locked into that view. The closed supplemental view can still be viewed on the flowsheet and report.

5. Click OK.




6. Click Save.

7. To add additional views to a flowsheet, repeat steps 1-6.

Note: There are no restrictions to the number of times a view can be added to a flowsheet.

5.1.2. Pages Tab

Use the Pages tab to add, edit, or remove a view, as well as arrange the display order of the views on a flowsheet.

Figure 5-4, Pages Tab

5.1.3. Editing a View Type in a Flowsheet

Use the Edit Flowsheet Page window to change a view type in a new or existing flowsheet. To edit a view in a flowsheet:

1. Select the Pages tab, highlight a view.

Figure 5-5, Pages Tab

2. Click . The Edit Flowsheet Page window appears.

3. From the View drop-down list, select a view to modify.

4. Optional: Change the display name.

5. From the Page Type options, select a Page Type: Mandatory, Optional, or Supplemental.

6. Click OK.

7. Click Save.

8. To edit the page types of additional views, repeat steps 1-7.




5.1.4. Removing a View from a Flowsheet

You can use Remove to delete a view from a flowsheet. To remove a view from a flowsheet, complete the following steps:

1. Select the Pages tab. Highlight the view to delete.

Figure 5-6, Highlight View to Delete

2. Click .

3. Click Save.

5.1.5. Changing the Display Order of Views in a Flowsheet

Use Move Up and Move Down to change the display order of the views in a flowsheet. To change the display order of views in a flowsheet, complete the following steps:

1. Highlight the view you want to move in the display order of a flowsheet.

Figure 5-7, Highlight View to Move

2. Clickto move the view up in the display order or clickto move the view down in the display order.

3. Click Save.

5.2. Creating a Flowsheet Total

The flowsheet total allows you to display the sum of numeric observations within that flowsheet view.

Note: Totals are based on active date ranges from the displayed flowsheet. The calculation of the totals can include observations which may not be on the displayed flowsheet.

The following screen illustrates the active date ranges from the displayed flowsheet:

Figure 5-8, Active Date Ranges

Additional configuration approaches are addressed in supplemental documentation.




Creating flowsheet totals involves adding and removing terms, as well as changing the display order of the terms.

Figure 5-9, Create a Flowsheet Total

Figure 5-10, Totals Display from CP Flowsheets

To create a flowsheet total:

1. From the File menu, highlight New and select New Flowsheet Total. The Create a New Flowsheet Total pop-up appears.

Figure 5-11, Create a New Flowsheet Total

2. In the Name box, type a name for the new total. The name appears in the tree view and as the Item Name at the top of the CP Console main window.

3. Click OK. The new Flowsheet Total worksheet appears.

5.2.1. Editing the Flowsheet Total

1. In the Display Name box, type a name for the new total.

2. To set the default unit, select a unit from the Default Unit drop-down list.

3. From the Decimals box, select the number of decimals for the default unit, 0-8. Default is 2.

4. Optional: In the Comment box, type additional information about the flowsheet total.

5. To make the total available in CP Flowsheets, select the Active check box.

6. From the Display Properties box, select one or more check boxes to provide calculations automatically on the view:

Display Total (All Terms) Display Count (All Terms) Display Average (All Terms) Display MinimumDisplay Maximum

5.2.1.1. Terminology Section

1. To move a term from the Available Terms list, select the term and click to move it into the

Selected Terms list.

2. To move a term from the Selected Terms list, select the term and click to move it into the

Available Terms list.

3. Repeat steps 1 and 2 as many times as is necessary.

4. To arrange the list of Selected Terms in a specific display order, select a term and click to move the term up the display order or to move the term down the display order.

5. Repeat step 4 until you have the list in specific display order.




6. Click Save.

5.2.2. Totals Tab

From the Flowsheets tree, select the Totals tab to add totals to and remove totals from a flowsheet, as well as, change the display order of totals on a flowsheet.

Figure 5-12, Totals Tab

5.2.2.1. Adding Totals to a Flowsheet

To add a total to a flowsheet:

1. On the Totals tab, highlight the total in the Available Totals list you want to add.

2. Click . The total moves to the Assigned Totals list.

3. Click Save.

5.2.2.2. Removing Totals from a Flowsheet

You can use the left arrow to remove a total from a flowsheet. To remove a total from a flowsheet:

1. On the Totals tab, highlight the total in the Assigned Totals list you want to remove.

2. Click . The total returns to the Available Totals list.

3. Click Save.

5.2.2.3. Changing the Display Order of Totals in a Flowsheet

Use the up arrow and the down arrow to change the display order of the totals in a flowsheet. To change the display order of the totals:

1. Highlight the total you want to move in the display order of a flowsheet.

2. Click to move the total up in the display order or click to move the total down in the display order.

3. Click Save.

5.3. Flowsheet Total

The flowsheet total allows you to display the sum of all observations of a single type within that flowsheet view. Totals use date ranges from the primary flowsheet form as ranges for the totals. The calculation of the totals uses all the intakes (observations) for a specified date/time range, which includes those that display on the flowsheet, as well as the intakes that do not.

1. From the File menu, highlight New and select Flowsheet Total. The Create New Flowsheet Total popup appears.

Figure 5-13, Create New Flowsheet Total

2. In the Name box, type a name for the new Flowsheet Total and click OK


(3. The new Flowsheet Total worksheet appears.)



Figure 5-14, Build a Flowsheet Total

5.3.1. Understanding Totals Display

Display Name: Display Name describes the flowsheet total; it appears as the title of the report.

Default Unit: Unit of measure that the flowsheet total uses as a default.

Decimals: Number of decimal places for the unit, 0-8; default is 2.

Comment: Optional – You can provide additional information regarding the flowsheet total.

Active: The flowsheet total is active and available in CP Flowsheets.

Select the Active check box to make the flowsheet total active and available. Clear the Active check box to inactivate the flowsheet total.

Note:If the Active check box is not selected, the flowsheet total does not load and you cannot enter data. A pop-up appears to indicate that the flowsheet total is not active. The inactive flowsheet total may display in the report.

In the tree view, an active flowsheet total appears .

Figure 5-15, Active Flowsheet

Display Properties: Select one or more properties to display on your flowsheet.

Display Total (All Terms)–sum of all observation amounts

Display Count (All Terms)–number of results of an observation within a flowsheet view

Display Average (All Terms)–average of all observations

Display Minimum–lowest number of observations Display Maximum–highest number of observations Display Ratio (Term 1/Term 2)

Display Difference (Term 1–Term 2)

5.4. Setting up Default Shifts

Flowsheets allows you to set up standard default shifts for your site and departments. Additional configuration approaches are documented in supplemental documentation.

5.4.1.1. Shift Information Definitions

The following are definitions for Shift Information in CP Console:

Display Name: Display Name describes the shift with a unique name, so you can identify it in the list of shifts.

Active: The shift is active and available in CP Flowsheets.

Select the Active check box to make the shift active and available. Clear the Active check box to inactivate the shift.

Note:If the Active check box is not selected, you cannot use the shift in your flowsheets.

In the tree view, an active shift appears .

Figure 5-16, Active Shift

Comment: Optional - You can provide additional information regarding the shift.

Start Time: 12:00 AM through 11:45 PM in 15-minute increments.

Stop Time: 12:00 AM through 11:45 PM in 15-minute increments.

5.4.1.2. Adding a Shift

Use the Shift Information worksheet to create your shifts. To add a shift:

1. From the File menu, highlight New and select Shift. The Create New Shift pop-up appears.

Figure 5-17, Create New Shift

2. In the Name box, type a name for the new shift. The name appears in the tree view and as the Item Name at the top of the CP Console main window.

Figure 5-18, Shift Worksheet

4. In the Display Name box, type a name for the new shift.

5. To make the shift available in CP Flowsheets, select the Active check box.

6. Optional: In the Comment box, type additional information about the shift.

7. From the Start Time drop-down list, select a begin time.

8. From the Stop Time drop-down list, select an end time.

9. Click Save.

5.4.1.3. Modifying an Existing Shift

Use start and stop times to modify your shifts. To modify an existing shift:

1. From the CP Console tree view, highlight Shift and expand the folder.

2. Select a shift from the list. In the following figure, the “Days-2” shift is selected.


(3. Click OK. The new Shift worksheet appears.)



Figure 5-19, Selected Shift

3. Make the necessary changes to one or more fields of the shift worksheet.

4. Click Save.

This page intentionally left blank for double-sided printing.


6. Additional Flowsheet Tasks

6.1. Setting up Background Tasks

CP Console background tasks are system activities (which run in the background) that you can schedule. The three available cleanups address CliO, CP Legacy, and the HL7 Cleanup. These settings are determined according to site policy.

Figure 6-1, Background Tasks

Select one of the background tasks and its properties appear.

Figure 6-2, CliO Cleanup Background Task Properties

Task ID: The identifier assigned to the task.

Name: The name of the background task.

Status: The status of a background task can be Active: Pending or Active: Running.

Scheduled: Scheduled indicates the date and time the background task begins; the Default is Not Scheduled.



6.1.1. CliO Cleanup

CliO is a database that stores patient observations. You can store data in a variety of formats. Old observations that are not in a state of verified or corrected are purged.

Note: If student/trainee documentation is not in a state of verified or corrected, it will also be purged. To change the scheduling of Clio Cleanup:

1. Under Background Task, click CliO Cleanup.

2. Click Change.

3. Schedule the task. Refer to the Changing the Schedule for a Task section for more details.

6.1.2. CP Cleanup

CP Cleanup background task cleans up observations (unencoded or XML data) from instruments (monitors) that are not in a verified state (data that is not clinically relevant). This cleanup is designed to run after data is processed, and deletes the data that is not clinically relevant from both Legacy and CliO. It runs through the UPLOAD ITEM field in the CP RESULT REPORT file (#703.1) and purges unnecessary data from previous uploads.

To change the scheduling of CP Cleanup:

1. Under Background Task, select CP Cleanup.

2. Click Change.

3. Schedule the task. Refer to Changing the Schedule for a Task for more details.

6.1.3. HL7 Cleanup

The HL7 Cleanup purges messages not validated that remain more than a number of days set by you, in the HL7 log file.

To change the scheduling of HL7 Cleanup:

1. Click HL7 Cleanup.

2. Click Change.

Schedule the task. Refer to the Changing the Schedule for a Task section for more details.

(Additional Flowsheet Tasks)

(Additional Flowsheet Tasks)

6.2. Adding an Instrument

Use the new instrument worksheet to add new instruments to Clinical Flowsheets. To add an instrument, complete the following steps:

Note: The instrument worksheet is for legacy CP instrument connections only. For MD*1.0*16 connections, all information required will be exported as part of a centrally maintained mapping file.

1. From the File menu, highlight New and select Instrument. The Create New Instrument pop-up appears.

Figure 6-3, Create New Instrument

2. In the Name box, type a name for the new instrument. The name appears in the tree view and as the Item Name at the top of the CP Console main window.

3. Click OK. The new Instrument worksheet appears.

Figure 6-4, New Instrument Worksheet

4. Optional – In the Comment box, type additional information pertaining to the instrument.

5. In the Print Name box, type the name as you want it to appear on the instrument report.

6. To make the instrument available in CP Flowsheets, select the Active check box.



7. In the Serial Number box, type the serial number of the instrument.

8. From the Notification Mailgroup drop-down list, select a local VistA mailgroup.

Click in the box and type an alpha character, such as b, p, or r, at which you want the list of mailgroups to begin.

6.2.1. Modifying an Existing Instrument

Use the Instrument worksheet to modify the parameters of an existing instrument. To modify an existing instrument, complete the following steps:

1. In the tree view, highlight Instrument and expand the folder.

2. Select an instrument from the list.

In the following example, the Aware instrument is selected.

Figure 6-5, Selected Instrument

3. Make the necessary changes to the fields of the instrument worksheet.

4. Click Save.

Comment: Optional – You can provide additional information regarding the instrument.

Print Name: Name of the instrument to print on the instrument report.

Active: The instrument is active and available in CP Flowsheets.

Select the Active check box to make the instrument active and available to transmit results.

Clear the Active check box to prevent the instrument from transmitting results.

Note:If the Active check box is not selected, you cannot use the instrument in your flowsheets.

In the tree view, an active instrument appears .

Figure 6-6, Active Instrument

Serial Number: Serial number of the instrument is assigned by the manufacturer.

Notification Mailgroup: Identify a local VistA mailgroup to notify when a problem arises with an active instrument.

6.2.2. Attachment Processing

Complete the following steps to select and process an attachment:

1. In the Default Ext box, type the default file extension exported by the vendor.

2. In the M Routine box, type the routine the instrument uses to process HL7 messages.

3. From the Pkg Code drop-down list, select the code of the processing package.

4. Select the Delete when submitted check box if the site does not store a duplicate report or the vendor deletes reports because of storage issues.

5. From the Valid Attachment Types options, select one or more method of attaching patient data.

The following are Attachment Processing definitions:

Default Ext: Default file extension exported by the vendor (.html, .pdf, .jpg).

M Routine: MUMPS routine used to process the HL7 message from the active instrument.

Pkg Code: Code of the package that processes the active instrument results.

Medicine – Medicine package

CP V1.0 – Clinical Procedures v1.0

CliO – Clinical Observation database

Delete when submitted: Select the check box if the site does not want to store a duplicate report outside of Imaging or the vendor wants to delete files because of storage issues.

Valid Attachment Types: The type of patient data expected from the instrument. Data type indicates to CP Console the kind of data output to expect from the instrument.

UUEncode (Unix to Unix Encode)–a set of algorithms for converting files into a set of ASCII characters to transmit over a network

XML (Extensible Markup Language)–a specification for Web documents developed by the World Wide Web Consortium (W3C), the organization that sets standards for the Web; XML is a pared-down version of Standard Generalized Markup Language (SGML)

XMS–XML Style Sheet

DLL (Dynamic Link Library)–a library of executable functions or data used by Windows applications

UNC (Universal/Uniform Naming Convention)–a personal computer (PC) format for specifying the location of resources on a local-area network (LAN)

Text–Text stored as ASCII codes

URL (Uniform Resource Locator)–the global address of documents and other resources on the World Wide Web (www)

6.2.3. Adding a Configuration for a Bi-Directional Instrument

To add a configuration for a bi-directional instrument, complete the following steps:

1. If the instrument is bi-directional, select the Bi-Directional Instrument check box.

d. Type in the IP Address assigned to the instrument, the Port (location) assigned to the instrument, the HL7 Instrument ID for the instrument, and the HL7 UNV SRV ID for the instrument procedure.

e. From the HL7 Link drop-down list, select the unique link for the instrument.

Click in the box and type an alpha character, such as b, p, or r, where you want the list of instrument links to begin.

Note: This area of the screen is for informational purposes only.

2. Click Save.

The following are term definitions for bi-directional instruments:

Bi-Directional Instrument: An instrument that both sends and receives data.

IP Address: Each instrument at your facility must have an IP address. An IP address is a string of four integer numbers between 0 and 255 separated by periods.

Port: The location of the instrument to which you send data and from which you receive data.

HL7 Inst ID: The instrument ID in HL7 messages that identifies the instrument. The ID is provided by the vendor.

HL7 Unv Svc ID: The universal service ID for HL7 messages identifies the type of procedure the instrument performs when the instrument is capable of performing more than one procedure.

HL7 Link: There is one unique HL7 link for each instrument.

6.3. Working with Parameters

Parameters are set with CP Console. You can configure the following items:

CP ADT Feed

CP Gateway Configuration, CP Parameters

6.3.1. CP Parameters

Figure 6-7, CP Console Parameters

Clinical Procedures system parameters affect all the procedures and instruments. You need to set the common parameters.

Figure 6-8, Clinical Procedures Common Parameter Set

6.3.2. Administering Notification Lists

A notification list editor is a tool that is part of the Clinical Procedures Common Parameter Set.

If you experience HL7 errors, the Notification List editor allows you to send a message to the specified member.

To administer notification lists:

1. Click the Notification Lists button.

Figure 6-9, Notification List Editor

2. In the Name list, select the list to edit. The members of the list appear in the Members box.

3. Use the Add, Edit, Remove buttons to edit the list.

4. Use the Save List button to save the list.

5. Use the Test button to send a test message to the members of the list.

The following are some additional terms specific to the Clinical Procedures Common Parameter Set:

Clinical Procedures Home Page: The Clinical Procedures Home page appears and directs the browser to this page when accessed. The data in this field is predefined.

Imaging Network Transfer Directory: This is the path to the Imaging network directory used for transferring data.

Use to browse to the appropriate location in the directory.

Observation Retrieval Batch Size (Records): The number of database (DB) records to pull at one time.

Use the arrows to select a number of DB records to include in the batch.

Unverified Observation Retention (Days): The number of days to keep the unverified observations before purging.

Use the arrows to select the number of days to retain unverified data. This is a CLIO Cleanup task.

Instrument Data Retention (Days): The number of days to keep data from an instrument before purging.

Use the arrows to select the number of days to retain instrument data. This is a CP Cleanup task.

Clinical Procedures System On Line: The Clinical Procedure System On Line check box allows you to restrict access to Clinical Procedures.

Select the check box to indicate Clinical Procedures is offline. Clear the check box to indicate Clinical Procedures is online.

Offline Message: When the Clinical Procedure System On Line check box is not selected, type a note in the Offline Message box to display when Clinical Procedures is offline.

Allow External Attachments: This affects Legacy CP. This allows you to find external attachments.

Select the Allow External Attachments? check box to allow external attachments. Clear the Allow External Attachments? check box to not allow external attachments.

Bypass CRC Check: Bypass the Cyclical Redundancy Check during startup. On the server you can check the checksum of the running application to verify that it is the same as the checksum of the application distributed; the checksum value is associated with the version number of the software.

Select the Bypass CRC Check? check box to perform the verification. Clear the Bypass CRC Check? check box to not perform the verification.

Note:If the checksum values do not match, a message appears indicating the values do not match.

Cache Terminology Files: This is the path to the network directory used for caching terminology files.

Use to browse to the appropriate location.

Notification Lists: Administer the lists used for notification.

6.4. CP ADT Feed Configuration

The ADT (Admission/Discharge/Transfer) system allows VistA to notify third party devices (outgoing data to devices) that a patient was admitted, discharged, or transferred. ADT feed acts as an event handling system. You must configure the dynamic routing system, so that HL7 knows to which system to deliver the ADT messages. Link an ADT target to a protocol. For more information on configuring the CP ADT Feed, refer to the CP Flowsheets Module V1.0 Installation Guide.

Note: The subscriber protocol (MD DGPM PATIENT MOVEMENT) is provided and you must add it to the ITEM multiple of the DGPM MOVEMENT EVENTS entry in the protocol file. This allows the ADT feed to receive notification of patient movement.

Figure 6-10, ADT Feed Configuration

6.4.1. Current ADT Targets

To remove an ADT target, highlight a line and click Delete Selected.

The following are definitions specific to ADT Targets:

Name: Name of the site

Protocol: Name of the subscriber protocol Division: Division location of patient Ward: Ward location of patient

Message Type: ADT

Event Type: ADT outbound (from VistA) message types

A01 Admit/visit notification

A02 Patient transfer

A03 Discharge/end visit

A08 Update patient information

A11 Cancel admission

A12 Cancel transfer

A13 Cancel discharge/end visit

6.4.2. Adding an ADT Target

Use the Add ADT Target window to link an ADT target to a protocol. To add an ADT target:

1. Highlight Parameters in the tree view.

2. Select CP ADT Feed Configuration. The Current ADT Targets window appears.

3. On the Current ADT Targets window, click New. The Add ADT Target window appears.

Figure 6-11, Add ADT Target

4. From the Protocol list, select a protocol by name.

5. From the Division tree view, select an entire division or a ward within a division. (This allows Clinical Flowsheets to filter outbound messages by patient location.)

6. In the Protocol Link Name box, type the protocol link name.

7. In the HL7 Message Type drop-down, ADT is the default.

8. From the HL7 Event Type drop-down list, select an ADT outbound message type.

9. Click OK.

Example

Protocol: MDSPL001

Division: CHEYENNE VAMROC>C MEDICINE

The MDSPL001 protocol receives the ADT A01 message only if the patient is moved, transferred, or discharged from the C MEDICINE location.

10. Repeat steps 4-9 for each HL7 event type you need to link.

6.5. CP Gateway Service Configuration

You must install the CP Gateway Service and configure the VistA server settings and the Gateway server settings for messaging to take place between VistA notification and ICU devices.

The CP Gateway Service exists as two subsystems, one solely within VistA, and the other as a Windows service that interacts with VistA by way of the RPC Broker. For more information on configuring the CP Gateway Service, refer to the CP Flowsheets Module V1.0 Installation Guide.

Use Gateway Server Settings to configure the gateway to restart automatically when the computer goes down.

Figure 6-12, CP Gateway Configuration Settings

6.5.1. VistA Server Settings

These settings allow the Gateway Service to restart automatically:

Access Code: Access code for the VistA service account with RPC Broker Context for CP Gateway (for more details. refer to the CP Flowsheets Module V1.0 Installation Guide)

Verify Code: Verify code for the VistA service account with RPC Broker Context for CP Gateway (for more details, refer to the CP Flowsheets Module V1.0 Installation Guide)

VistA server address settings are stored on the workstation in the system registry. They allow the CP Gateway Service to connect to the appropriate VistA system at startup.

RPC Broker Port: Port on which the CP Gateway Service connects to the broker

IP Address: IP address at which the CP Gateway Service connects to the VistA system

6.5.2. Gateway Server Settings

The following are definitions specific to the Gateway Server:

IP Address: Each server must have an IP address. An IP address is a string of numbers with format: xx.xx.xx.xxx. IP address of the workstation on which the CP Gateway Service is installed.

Notify Port: The listening port of the local machine. The port must be open when sending a message to the workstation. The default is 8888.

Log Level: The level of detail to log in the Windows Event Viewer for the CP Gateway Service.

Critical – severe errors onlyError – critical + errors that cause instability in the operation of the Gateway Service Warning – critical + error + any items captured but allowed the Gateway Service to continue running

Detail – critical + error + warning + detailed execution trail of everything that the Gateway Service does as it processes HL7 messages

Log Directory: The log file tracks all the background operations and any problems that occur during processing. This is the directory in which the CP Gateway Service stores the logs.

Type in the location of the log directory. The default directory for the log file is C:\

Days to Retain Data: The number of days to allow processed messages to remain in the log prior to purging. After the number of days indicated, the data is purged during HL7 Log Cleanup.

Use the arrows to set the number of days to retain messages. Leave the field empty or at 0 to retain the data indefinitely.

CP/Imaging Xfer Directory: This is the directory in which Imaging stores CP transfer data.

Data Retrieval Mechanism: The method to use for data retrieval–your data source: VistA Notification

or Polling.

Set the interval to VistA Notification. In VistA Notification, the VistA server will automatically notify the CP Gateway whenever a message arrives that requires processing. This is the preferred setting. Sometimes, however, local business requirements dictate that the Polling option be used. This option acts like the legacy CP Gateway, in that the CP Gateway will be polled periodically for data to process.

Polling Interval: The CP Gateway Service polls for new instrument data to transmit to VistA. When you select Polling as the data retrieval mechanism, use the arrows to set the number of seconds between polling operations. A new value becomes effective after the next polling operation.

6.6. Working with Procedure Information

Legacy procedure information is populated through the CP DEFINITION file (#702.01), but you need to populate additional fields to complete the process. You can add new procedures and modify existing procedures. In order to use a procedure in a flowsheet, you must select the Active check box to activate it. Also, you need a primary key (MD ADMINISTRATOR or MD MANAGER) to edit and add procedures.

Figure 6-13, Edit Procedure

6.6.1. Adding a Procedure

Use the new procedure worksheet to add new procedures to CP Flowsheets. To add a procedure:

1. From the File menu, highlight New and select Procedure. The Create New Procedure pop-up appears.

Figure 6-14, Create New Procedure

2. In the Name box, type a name for the new procedure.

3. Click OK. The new Procedure worksheet appears.

The name appears in the tree view and as the Item Name at the top of the CP Console main window.

Figure 6-15, Procedure Worksheet

6.6.2. Modifying an Existing Procedure

Use the Procedure worksheet to modify the parameters of an existing procedure. To modify an existing procedure:

1. In the tree view, highlight and expand the Procedure folder.

2. Select a procedure from the list.

3. Make the necessary changes to one or more of the fields of the procedure worksheet.

4. Click Save.

6.6.3. Procedure Definitions

The following are definitions specific to Procedure:

Treating Specialty: This is the specialty under which the procedure falls. The list comes from the TREATING SPECIALTY file (#45.7).

Figure 6-16, Treating Specialty

Hospital Location: The location in the hospital in which the procedure is performed. The list comes from the HOSPITAL LOCATION file (#44); workload credit for the procedure is tracked through hospital location.

TIU Note Title: The title of an appropriate note with which to reference the active procedure. The list comes from the TIU DOCUMENT file (#8925). This must be a Generic TIU Note title.

Description: This is information describing/identifying the procedure.

External Attachment Directory: This is the directory in which you find attachments. If you select the Require External Data check box, type in the path to the location of the data, or browse to locate a directory.

Require External Data: The procedure requires external attachments, such as an independent report from another facility.

Auto Submit to VistA Imaging: Automatically submit to VistA Imaging when the procedure is processed by a bi-directional instrument and addi

clinical procedures (cp) · web viewsection 5.2, creating a flowsheet total, replaced figure 5-10,...

Documents