Business Units – Settings – Signature – Co-Signature

Enable Co-Signature Option

Allows activation of the Co-Signature functionality for the Business Unit.

Co-Signature Statement

Allows entry of an agency-defined acceptance statement that will be displayed when a user completes the final process in co-signing clinical documentation. The text will be displayed on the Co-Signature wizard before co-signing documentation. This field becomes available after the Enable Co- Signature Option is selected for this Business Unit.

Clinical Items

Displays the list of clinical documents that can be co-signed. Choose the items by selecting the check box opposite the needed clinical item type.

You can select the following clinical documentation types: 

·         Assessment (Patient>Clinical>Assessments)

·         Clinical Note (Patient>Clinical>Clinical Notes) 

·         Medication (Patient>Clinical>Medications)

·         Visit Frequency (Patient>Clinical>Visit Frequency)

If you have not defined any clinical items, when saving the window, the following error message appears: "Select at least one clinical item for enabled co-signature."

Tasks 

Using this tab, you can set up default task configuration for denied clinical documentation. Defining tasks for denied clinical documents occurs on the third step of the Co-Signature wizard. The tasks are generated for the resource responsible for fixing corresponding clinical documents.

Task

Select the default task code for the denied clinical document. Task codes specific to co- signature denial can be defined in Administration>General>Patient Tasks.

Priority 

Priority identifies the urgency with which the task must be completed. Select the appropriate task priority from the drop-down list: Low, Normal, Medium, High, and Urgent.

Due Date

Enter a due date interval for tasks. This interval defines the number of days within which denied clinical documents should be fixed. The day count starts from the date when clinical document was denied. The field is optional. If you do not define the due date interval here, 0 is displayed in the My Task window of the resource for whom the task is assigned and the task becomes active immediately when created.