Difference between revisions of "V11 Tasks"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
Line 113: Line 113:
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
| style="border:1px solid gray;"|Patient Arrived
 
| style="border:1px solid gray;"|Base
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|The user specifies this type on the New Task page.
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|User specified on the New Task page
 
| style="border:1px solid gray;"|When the user clicks Done.
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
 
| style="border:1px solid gray;"|Personal
 
| style="border:1px solid gray;"|Personal
 
| style="border:1px solid gray;"|Base
 
| style="border:1px solid gray;"|Base
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|The user specifies this type on the New Task page.
+
| style="border:1px solid gray;"|The user specifies this type on the New Task page
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|User specified on the New Task page
 
| style="border:1px solid gray;"|User specified on the New Task page
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
| style="border:1px solid gray;"|
 
|-
 
| style="border:1px solid gray;"|Medication Renewal
 
| style="border:1px solid gray;"|Base
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|The user specifies this type on the New Task page. This task is intended to be created by those users who do not have access to the patient\'s chart.
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|User specified on the New Task page
 
| style="border:1px solid gray;"|When the user clicks Done.
 
| style="border:1px solid gray;"|Yes
 
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
| style="border:1px solid gray;"|Health Maintenance Alert
 
| style="border:1px solid gray;"|Base
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|When the user wants to notify another user that the patient has an alerted order reminder.
 
| style="border:1px solid gray;"|Notification
 
| style="border:1px solid gray;"|New user
 
| style="border:1px solid gray;"|When the user clicks Done (or Remove).
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
|-
 
 
| style="border:1px solid gray;"|Personal CareGuide Overwritten
 
| style="border:1px solid gray;"|Personal CareGuide Overwritten
 
| style="border:1px solid gray;"|CareGuide Template Management
 
| style="border:1px solid gray;"|CareGuide Template Management
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|An admin user overwrites all personal CareGuide templates with an Enterprise version
+
| style="border:1px solid gray;"|An admin user overwrites all personal CareGuide templates with an Allscripts Enterprise version
 
| style="border:1px solid gray;"|Personal CareGuide Overwritten
 
| style="border:1px solid gray;"|Personal CareGuide Overwritten
 
| style="border:1px solid gray;"|The provider(s) with personal versions of the CareGuide template
 
| style="border:1px solid gray;"|The provider(s) with personal versions of the CareGuide template
| style="border:1px solid gray;"|When the user clicks Done (or Remove).
+
| style="border:1px solid gray;"|When the user clicks Done (or Remove)
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Verify CCR Doc
 
| style="border:1px solid gray;"|Verify CCR Doc
 
| style="border:1px solid gray;"|CED
 
| style="border:1px solid gray;"|CED
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Created upon the receipt of an unsolicited Clinical Exchange Document.
+
| style="border:1px solid gray;"|Created upon the receipt of an unsolicited Clinical Exchange Document
 
| style="border:1px solid gray;"|Verify CCR Doc
 
| style="border:1px solid gray;"|Verify CCR Doc
 
| style="border:1px solid gray;"|Document owner
 
| style="border:1px solid gray;"|Document owner
| style="border:1px solid gray;"|When the document is verified by the user.
+
| style="border:1px solid gray;"|When the document is verified by the user
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Verify CCR Item
 
| style="border:1px solid gray;"|Verify CCR Item
 
| style="border:1px solid gray;"|CED
 
| style="border:1px solid gray;"|CED
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Created upon the receipt of an unsolicited Clinical Exchange Document.
+
| style="border:1px solid gray;"|Created upon the receipt of an unsolicited Clinical Exchange Document
 
| style="border:1px solid gray;"|Verify CCR Item
 
| style="border:1px solid gray;"|Verify CCR Item
 
| style="border:1px solid gray;"|CCR Verify Team
 
| style="border:1px solid gray;"|CCR Verify Team
| style="border:1px solid gray;"|When there are no more unverified items for this document.
+
| style="border:1px solid gray;"|When there are no more unverified items for this document
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|[[ABN Follow-up]]
 
| style="border:1px solid gray;"|[[ABN Follow-up]]
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A procedure charge is deemed medically not necessary and activated when the system preference Hold charges that fail medical necessity checking = No.  System generated if a charge fails medical necessity checking.
+
| style="border:1px solid gray;"|A procedure charge is deemed medically not necessary and activated when the system preference Hold charges that fail medical necessity checking = No.  System generated if a charge fails medical necessity checking
 
| style="border:1px solid gray;"|Process Encounter
 
| style="border:1px solid gray;"|Process Encounter
 
| style="border:1px solid gray;"|Billing provider
 
| style="border:1px solid gray;"|Billing provider
| style="border:1px solid gray;"|Manually completed when charges are edited in the practice manage system, and the user clicks Done.  Auto-completed if charge is edited to pass medical necessity checking.
+
| style="border:1px solid gray;"|Manually completed when charges are edited in the practice manage system, and the user clicks Done.  Auto-completed if charge is edited to pass medical necessity checking
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Go To Enc Form
 
| style="border:1px solid gray;"|Go To Enc Form
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|A user clicks New Task on the Encounter Form page and indicates Go To Enc Form in the Task box or a follow-up task is created on the PDA.
+
| style="border:1px solid gray;"|A user clicks New Task on the Encounter Form page and indicates Go To Enc Form in the Task box or a follow-up task is created on the PDA
 
| style="border:1px solid gray;"|Go To Enc Form
 
| style="border:1px solid gray;"|Go To Enc Form
 
| style="border:1px solid gray;"|User specified on the Encounter Form New Task page
 
| style="border:1px solid gray;"|User specified on the Encounter Form New Task page
| style="border:1px solid gray;"|Manually completed when the user clicks Done.
+
| style="border:1px solid gray;"|Manually completed when the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Adjust Charges
 
| style="border:1px solid gray;"|Adjust Charges
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A user edits or removes charges that have already been sent to billing.
+
| style="border:1px solid gray;"|A user edits or removes charges that are in a Submitted status
 
| style="border:1px solid gray;"|Process Encounter
 
| style="border:1px solid gray;"|Process Encounter
 
| style="border:1px solid gray;"|Billing provider
 
| style="border:1px solid gray;"|Billing provider
| style="border:1px solid gray;"|Manually completed when the charges are edited in the practice management system, and the user clicks Done.
+
| style="border:1px solid gray;"|Manually completed when the charges are edited in the practice management system, and the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Submit Enc Form
 
| style="border:1px solid gray;"|Submit Enc Form
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|An arrived appointment is received by the system or when additional charges added to encounter without resubmitting encounter form.
+
| style="border:1px solid gray;"|An arrived appointment is received by the system or when additional charges added to encounter without resubmitting encounter form. This task is inactive, but still supported for use in Enterprise EHR. To use this task, set it to Active
 
| style="border:1px solid gray;"|Send Charges
 
| style="border:1px solid gray;"|Send Charges
| style="border:1px solid gray;"|Billing provider; if none, then appointment provider; if none, then Encounter Followup Team  
+
| style="border:1px solid gray;"|Billing provider; if none, then appointment provider; if none, then Encounter Follow-up Team  
| style="border:1px solid gray;"|Auto-completed when: 1. User clicks Submit regardless of the status of any change on that encounter. 2. User cancels a charge and the rules for creating a Submit Enc form task fail and there are no charges with a status of Needs Info, Saved, or Ready.
+
| style="border:1px solid gray;"|Auto-completed when: 1. User clicks Submit regardless of the status of any change on that encounter. 2. User cancels a charge and the rules for creating a Submit Enc form task fail and there are no charges with a status of Needs Info, Saved, or Ready
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Review Enc Form
 
| style="border:1px solid gray;"|Review Enc Form
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Created for coders and attending physicians to review the encounter forms submitted by specified providers before charges are submitted to the practice management system for billing. System generated when a user clicks or taps Submit and based on the ChgWorksCreateRevEncFormTasks user preference which is set in Admin (not in the Personalize Charge page).
+
| style="border:1px solid gray;"|Created for coders and attending physicians to review the encounter forms submitted by specified providers before charges are submitted to the practice management system for billing. System generated when a user clicks or taps Submit and has the ChgWorksCreateRevEncFormTasks user preference set to Always or In Patient Only. (Admin not in the Personalize Charge page)
 
| style="border:1px solid gray;"|Review Charges
 
| style="border:1px solid gray;"|Review Charges
 
| style="border:1px solid gray;"|Enc Review team
 
| style="border:1px solid gray;"|Enc Review team
| style="border:1px solid gray;"|Auto-completed when all charges on the encounter are submitted by a user without the ChgWorksCreateRevEncFormTasks user preference.
+
| style="border:1px solid gray;"|Auto-completed when all charges on the encounter are submitted by a user with the
| style="border:1px solid gray;"|No
+
ChgWorksCreateRevEncFormTasks user preference set to Never
| style="border:1px solid gray;"|
 
|-
 
| style="border:1px solid gray;"|Injury/WC F/up
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|Created when injury information is deemed necessary for a selected diagnosis.  Activated when the system preference CWWorksPrefCreateInjTask = Y.  System generated if the system option set to create and special billing condition is entered on the encounter form.
 
| style="border:1px solid gray;"|Process Encounter
 
| style="border:1px solid gray;"|Enc Review team
 
| style="border:1px solid gray;"|Manually completed when charges are edited in the practice management system, and user clicks Done.
 
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 246: Line 207:
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|If there are one or more charges on the encounter with the status of Needs Info.
+
| style="border:1px solid gray;"|If there are one or more charges on the encounter with the status of Needs Info
 
| style="border:1px solid gray;"|Edit Charges
 
| style="border:1px solid gray;"|Edit Charges
 
| style="border:1px solid gray;"|Charge Edits Team
 
| style="border:1px solid gray;"|Charge Edits Team
| style="border:1px solid gray;"|Automatically completed when there are no charges on the encounter with status of Needs Info.
+
| style="border:1px solid gray;"|Automatically completed when there are no charges on the encounter with status of Needs Info
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 256: Line 217:
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|System generated according to the preference on the service list and if an inpatient encounter form has charges on it that are not submitted and there is no Submit IP Enc task.
+
| style="border:1px solid gray;"|System generated according to the preference on the service list and if an inpatient encounter form has charges on it that are not submitted and there is no Submit IP Enc task
 
| style="border:1px solid gray;"|Send Charges
 
| style="border:1px solid gray;"|Send Charges
 
| style="border:1px solid gray;"|Billing provider
 
| style="border:1px solid gray;"|Billing provider
| style="border:1px solid gray;"|Auto-completed when: 1. User clicks Submit regardless of the status of any change on that encounter. 2. User cancels a charge and the rules for creating a Submit IP Enc task fail and there are no charges with a status of Needs Info, Saved, or Ready.
+
| style="border:1px solid gray;"|Auto-completed when: 1. User clicks Submit regardless of the status of any change on that encounter. 2. User cancels a charge and the rules for creating a Submit IP Enc task fail and there are no charges with a status of Needs Info, Saved, or Ready
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 266: Line 227:
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|System generated if a Submit Enc Form task does not exist for that Result Charge encounter.  There cannot be an active Submit Enc Form task and an active Submit Res Enc task on the same encounter.
+
| style="border:1px solid gray;"|System generated if a Submit Enc Form task does not exist for that Result Charge encounter.  There cannot be an active Submit Enc Form task and an active Submit Res Enc task on the same encounter
 
| style="border:1px solid gray;"|Send Charges
 
| style="border:1px solid gray;"|Send Charges
 
| style="border:1px solid gray;"|Lab Charges Team
 
| style="border:1px solid gray;"|Lab Charges Team
Line 276: Line 237:
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|Charge
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Through the encounter form automatic printing set-up, this task is created when all charges are submitted and reach a status of Submitted or Review. System generated if system option is set to create and all charges are either (1) Submitted or (2) Submitted or Review.
+
| style="border:1px solid gray;"|Through the encounter form automatic printing set-up, this task is created when all charges are submitted and reach a status of Submitted or Review. System generated if system option is set to create and all charges are either (1) Submitted or (2) Submitted or Review
 
| style="border:1px solid gray;"|Print Enc Form
 
| style="border:1px solid gray;"|Print Enc Form
 
| style="border:1px solid gray;"|Billing provider
 
| style="border:1px solid gray;"|Billing provider
| style="border:1px solid gray;"|Auto-completed when the encounter form is printed.
+
| style="border:1px solid gray;"|Auto-completed when the encounter form is printed
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
 +
| style="border:1px solid gray;"|Clinical Trial Match
 +
| style="border:1px solid gray;"|Clinical Trial
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|This task is automatically generated via a nightly run to notify providers of possible clinical trials for a patient.
 +
| style="border:1px solid gray;"|Clinical Trial Contact Detail Page
 +
| style="border:1px solid gray;"|Clinical Trial Team
 +
| style="border:1px solid gray;"|When the user clicks Done after following up with the patient regarding the clinical trial
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|
 +
 
| style="border:1px solid gray;"|Sign Letter
 
| style="border:1px solid gray;"|Sign Letter
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A special kind of CC, this task is generated when the CC dialog is used to create a letter and that letter requires electronic signature to be finalized and the owner of the letter has an electronic workflow.
+
| style="border:1px solid gray;"|A special kind of CC, this task is generated when the CC dialog is used to create a letter and that letter requires electronic signature to be finalized and the owner of the letter has an electronic workflow
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Document owner
 
| style="border:1px solid gray;"|Document owner
| style="border:1px solid gray;"|When the user signs the document.
+
| style="border:1px solid gray;"|When the user signs the document
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Verify Doc
 
| style="border:1px solid gray;"|Verify Doc
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A transcription comes over an interface or through TouchWorks Scan.
+
| style="border:1px solid gray;"|A transcription comes over an interface or through Allscripts Enterprise EHR Scan.
 
| style="border:1px solid gray;"|Verify Transcription
 
| style="border:1px solid gray;"|Verify Transcription
 
| style="border:1px solid gray;"|Provider selected in the transcription source file
 
| style="border:1px solid gray;"|Provider selected in the transcription source file
| style="border:1px solid gray;"|Automatically when the user verifies or invalidates the transcription.
+
| style="border:1px solid gray;"|Automatically when the user verifies or invalidates the transcription
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Print Document
 
| style="border:1px solid gray;"|Print Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A user selects the Create Print Doc Task option when signing a Note.
+
| style="border:1px solid gray;"|A user selects the Create Print Doc Task option when signing a Note
 
| style="border:1px solid gray;"|Print Document
 
| style="border:1px solid gray;"|Print Document
 
| style="border:1px solid gray;"|User who signed the Note
 
| style="border:1px solid gray;"|User who signed the Note
| style="border:1px solid gray;"|When the document is queued for printing.
+
| style="border:1px solid gray;"|When the document is queued for printing
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Reconcile Doc
 
| style="border:1px solid gray;"|Reconcile Doc
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|If the inbound document interface is configured to create this task when a patient associated with a document to be filed can not be found in the clinical database.
+
| style="border:1px solid gray;"|If the inbound document interface is configured to create this task when a patient associated with a document to be filed cannot be found in the clinical database
 
| style="border:1px solid gray;"|Document Reconciliation
 
| style="border:1px solid gray;"|Document Reconciliation
 
| style="border:1px solid gray;"|The dictating provider associated with the document to be filed
 
| style="border:1px solid gray;"|The dictating provider associated with the document to be filed
| style="border:1px solid gray;"|By the system when the task is performed and the document is linked to an existing patient.
+
| style="border:1px solid gray;"|By the system when the task is performed and the document is linked to an existing patient
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Doc Update
 
| style="border:1px solid gray;"|Doc Update
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Transcription is verified or invalidated.
+
| style="border:1px solid gray;"|Transcription is verified or invalidated
 
| style="border:1px solid gray;"|Note Update
 
| style="border:1px solid gray;"|Note Update
 
| style="border:1px solid gray;"|Provider selected in the transcription source file
 
| style="border:1px solid gray;"|Provider selected in the transcription source file
| style="border:1px solid gray;"|Automatically completed when transaction is verified or invalidated.
+
| style="border:1px solid gray;"|Automatically completed when transaction is verified or invalidated
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Review Document
 
| style="border:1px solid gray;"|Review Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|A user or the system
 
| style="border:1px solid gray;"|A user or the system
| style="border:1px solid gray;"|When a user is selected to receive a Carbon Copy of the document via a Task (rather than a printed or faxed copy) AND after the document completes a step that triggers its distribution (i.e. if configured to generate on Final, tasks are generated for any CC task recipients when the document is finalized.)
+
| style="border:1px solid gray;"|When an unsolicited transcription document that has been sent through an interface to Allscripts Enterprise EHR
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Process Note
| style="border:1px solid gray;"|The recipient of the CC.
+
| style="border:1px solid gray;"|The owner of the document sent via the interface
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user navigates to the document in Allscripts Enterprise EHR
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|CorrectNote User
 
| style="border:1px solid gray;"|CorrectNote User
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|When a user selects Req Correction for an unstructured document and chooses \'Author\' as the recipient.
+
| style="border:1px solid gray;"|When a user selects Req Correction for an unstructured document and chooses \'Author\' as the recipient
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Sign Note
| style="border:1px solid gray;"|User specified as the Author of the document.
+
| style="border:1px solid gray;"|User specified as the Author of the document
| style="border:1px solid gray;"|When the user signs the document.
+
| style="border:1px solid gray;"|When the user signs the document
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|CorrectNote Admin
 
| style="border:1px solid gray;"|CorrectNote Admin
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|When a user selects Req Correction for an unstructured document and chooses \'Medical Records Team\' as the recipient.
+
| style="border:1px solid gray;"|When a user selects Req Correction for an unstructured document and chooses \'Medical Records Team\' as the recipient
 
| style="border:1px solid gray;"|CorrectNote Admin
 
| style="border:1px solid gray;"|CorrectNote Admin
 
| style="border:1px solid gray;"|Medical Records Team
 
| style="border:1px solid gray;"|Medical Records Team
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|CoSign Note
 
| style="border:1px solid gray;"|CoSign Note
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|Document
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|When he/she needs a medication renewed.
+
| style="border:1px solid gray;"|When he/she needs a medication renewed
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|User specified on the Note New Task page
 
| style="border:1px solid gray;"|User specified on the Note New Task page
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 +
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 +
| style="border:1px solid gray;"|Co-Sign Note
 +
| style="border:1px solid gray;"|Document
 +
| style="border:1px solid gray;"|A user
 +
| style="border:1px solid gray;"|When a V11 note is selected
 +
| style="border:1px solid gray;"|To NoteForm Note Output
 +
| style="border:1px solid gray;"|The user that is specified on the Note New Task page
 +
| style="border:1px solid gray;"|When the user signs the V11 Note
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
 +
| style="border:1px solid gray;"|Overdue Reminders
 +
| style="border:1px solid gray;"|HMP
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|This task is generated by the system when there are overdue Med Admin, Orders, or Reminders
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|Provider in the Planned By Field in HMP
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 +
| style="border:1px solid gray;"|Unlinked Patient
 +
| style="border:1px solid gray;"|Initiate Unlink
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|Unlinked Patient is one of two tasks associated with the Initiate “unlink” functionality. When Allscripts Enterprise EHR™ receives a unlink message from Initiate for a patient, the application automatically creates an Unlinked Patient task in the provider’s Task List. The task is named “Unlinked Patient” and it serves as a notification to the provider to check the patient’s chart and clean it up
 +
| style="border:1px solid gray;"|Review Chart
 +
| style="border:1px solid gray;"|Med Records Team
 +
| style="border:1px solid gray;"|Manual completion
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|
 +
|-
 +
| style="border:1px solid gray;"|Unlinked Patient Reminder
 +
| style="border:1px solid gray;"|Initiate Unlink
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|When Allscripts Enterprise EHR™ receives a unlink message from Initiate for a patient, the application automatically creates an Unlinked Patient Reminder task in the Provider’s Task List. This task is created as inactive with a due date of two weeks in the future. It serves as a second notification to check the patient’s chart and clean up any Data that has been added to the chart since the first notification
 +
| style="border:1px solid gray;"|Review Chart
 +
| style="border:1px solid gray;"|Med Records Team
 +
| style="border:1px solid gray;"|Manual completion
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|ePat Message
 
| style="border:1px solid gray;"|ePat Message
| style="border:1px solid gray;"|iHealth
+
| style="border:1px solid gray;"|Patient Portal
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Patients can send a general message to their physician. This message type is forwarded to TouchWorks, and displays as an ePat Message task with a link to a pre-created structured note which contains the text of the message. The physician can respond to the message using the TouchWorks Note module.
+
| style="border:1px solid gray;"|Patients can send a general message to their physician. This message type is forwarded to Allscripts Enterprise EHR, and displays as an ePat Message task with a link to a pre-created structured note which contains the text of the message. The physician can respond to the message using the Allscripts Enterprise EHR Note module
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Physician the patient sent the message to
 
| style="border:1px solid gray;"|Physician the patient sent the message to
Line 382: Line 393:
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|ePat Registration
 
| style="border:1px solid gray;"|ePat Registration
| style="border:1px solid gray;"|iHealth
+
| style="border:1px solid gray;"|Patient Portal
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Patients can send a request to register for iHealth privileges. The patient registration request is forwarded to the TouchWorks system, and displays as an ePat Registration task in the physician’s task list. Physicians or clinical staff can choose to either accept or deny the request. TouchWorks records the patient’s iHealth information and the response to the request, and then sends the response back to the patient.
+
| style="border:1px solid gray;"|Patients can send a request to register for Patient Portal privileges. The patient registration request is forwarded to the Allscripts Enterprise EHR system, and displays as an ePat Registration task in the physician’s task list. Physicians or clinical staff can choose to either accept or deny the request. Allscripts Enterprise EHR records the patient’s Patient Portal information and the response to the request, and then sends the response back to the patient
| style="border:1px solid gray;"|Process ePatient Registration||Physician the patient is registering with
+
| style="border:1px solid gray;"|Process ePatient Registration
| style="border:1px solid gray;"|When task is performed and user clicks Accept or Deny on iHealth Patient Registration dialog
+
| style="border:1px solid gray;"|Physician the patient is registering with
 +
| style="border:1px solid gray;"|When task is performed and user clicks Accept or Deny on Patient Portal Patient Registration dialog
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|ePat Appt Request
 
| style="border:1px solid gray;"|ePat Appt Request
| style="border:1px solid gray;"|iHealth
+
| style="border:1px solid gray;"|Patient Portal
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Patients can send a request to their physician for a appointment. This message type is forwarded to TouchWorks, and displays as an ePat Appt Request task.  The TouchWorks user can send a response back to the patient with the new appointment information.  This information must be manually reconciled with the practice management system.
+
| style="border:1px solid gray;"|Patients can send a request to their physician for an appointment. This message type is forwarded to Allscripts Enterprise EHR, and displays as an ePat Appt Request task.  The Allscripts Enterprise EHR user can send a response back to the patient with the new appointment information.  This information must be manually reconciled with the practice management system
 
| style="border:1px solid gray;"|Process ePatient Appointment
 
| style="border:1px solid gray;"|Process ePatient Appointment
 
| style="border:1px solid gray;"|Physician the patient sent the message to
 
| style="border:1px solid gray;"|Physician the patient sent the message to
Line 401: Line 413:
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|ePat Med Renew
 
| style="border:1px solid gray;"|ePat Med Renew
| style="border:1px solid gray;"|iHealth
+
| style="border:1px solid gray;"|Patient Portal
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Patients can send a request to their physician for a prescription renewal. This message type is forwarded to TouchWorks, and displays as an ePat Med Renew task with a link to a pre-created structured note which contains the text of the request.
+
| style="border:1px solid gray;"|Patients can send a request to their physician for a prescription renewal. This message type is forwarded to Allscripts Enterprise EHR, and displays as an ePat Med Renew task with a link to a pre-created structured note which contains the text of the request
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Physician the patient sent the message to
 
| style="border:1px solid gray;"|Physician the patient sent the message to
Line 411: Line 423:
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|ePat Visit
 
| style="border:1px solid gray;"|ePat Visit
| style="border:1px solid gray;"|iHealth
+
| style="border:1px solid gray;"|Patient Portal
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Patients can send a request to their physician to provide an online consultation. The online consultation request is forwarded to TouchWorks, and displays as an eVisit task with a link to a pre-created structured note which contains the text of the request. The physician can respond to the request using the TouchWorks Note module.
+
| style="border:1px solid gray;"|Patients can send a request to their physician to provide an online consultation. The online consultation request is forwarded to Allscripts Enterprise EHR, and displays as an eVisit task with a link to a pre-created structured note which contains the text of the request. The physician can respond to the request using the Allscripts Enterprise EHR Note module
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Physician the patient sent the message to
 
| style="border:1px solid gray;"|Physician the patient sent the message to
Line 421: Line 433:
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|ePat Message Failure
 
| style="border:1px solid gray;"|ePat Message Failure
| style="border:1px solid gray;"|iHealth
+
| style="border:1px solid gray;"|Patient Portal
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is generated when a failure occurs with an inbound or outbound message.
+
| style="border:1px solid gray;"|The task is generated when a failure occurs with an inbound or outbound message
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|Provider who received or sent the message
 
| style="border:1px solid gray;"|Provider who received or sent the message
Line 431: Line 443:
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Finish Note
 
| style="border:1px solid gray;"|Finish Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A Note has been saved, and no dictations or transcriptions are outstanding.  The Note has not yet been signed.
+
| style="border:1px solid gray;"|A Note has been saved, and no dictations or transcriptions are outstanding.  The Note has not yet been signed
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|Note owner
 
| style="border:1px solid gray;"|Note owner
| style="border:1px solid gray;"|Signing the Note completes the task; the Note does not have to be finalized.  Regardless of who completes this task, it should disappear from owner’s task list automatically.  If a dictation or transcription related task is created, this task will automatically disappear/complete.  If a returning transcription is reviewed and the note is not signed, a FinishNoteInput task will reappear or be created for the note owner.
+
| style="border:1px solid gray;"|Signing the Note completes the task; the Note does not have to be finalized.  Regardless of who completes this task, it should disappear from owner’s task list automatically.  If a dictation or transcription related task is created, this task will automatically disappear/complete.  If a returning transcription is reviewed and the note is not signed, a FinishNoteInput task will reappear or be created for the note owner
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
| style="border:1px solid gray;"|[http://blog.galenhealthcare.com/2012/01/16/finishnotetasks/ Finish Note Task Blog Article]
+
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Waiting for Transcription
 
| style="border:1px solid gray;"|Waiting for Transcription
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|All dictation(s) have been sent, but the transcription(s) haven’t returned, so the Note is not ready for finishing note input or signature.
+
| style="border:1px solid gray;"|All dictation(s) have been sent, but the transcription(s) haven’t returned, so the Note is not ready for finishing note input or signature
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|Note owner
 
| style="border:1px solid gray;"|Note owner
Line 451: Line 463:
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Review Covered Note
 
| style="border:1px solid gray;"|Review Covered Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Created for the appointment provider once the Note is finalized by a provider not linked to appointment. This task may or may not be linked to a note template.  If not linked to a note template, then the task will not be created for the appointment provider if someone else becomes the owner and finalizes the note. This task can also be manually created.  If manually created and created by system, then only one instance of the task should exist.  If user is flagged to not receive these tasks then no task will be created for that appointment provider regardless of note template setting.
+
| style="border:1px solid gray;"|Created for the appointment provider once the Note is finalized by a provider not linked to appointment. This task may or may not be linked to a note template.  If not linked to a note template, then the task will not be created for the appointment provider if someone else becomes the owner and finalizes the note. This task can also be manually created.  If manually created and created by system, then only one instance of the task should exist.  If user is flagged to not receive these tasks then no task will be created for that appointment provider regardless of note template setting
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|Appointment provider by default or provider manually selected when created ad hoc
 
| style="border:1px solid gray;"|Appointment provider by default or provider manually selected when created ad hoc
| style="border:1px solid gray;"|When the assignee navigates to the Note.
+
| style="border:1px solid gray;"|When the assignee navigates to the Note
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Dictation
 
| style="border:1px solid gray;"|Dictation
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|Dictation marker is placed in the Note, but it has not yet been dictated.
+
| style="border:1px solid gray;"|Dictation marker is placed in the Note, but it has not yet been dictated
 
| style="border:1px solid gray;"|Document Update
 
| style="border:1px solid gray;"|Document Update
| style="border:1px solid gray;"|User who places the dictation marker||Dictating and sending dictations linked to all outstanding dictation markers in Note associated with the single dictating provider: there may be additional incomplete dictations linked to another provider and another task specific to the other provider.  The task can also be completed by deleting the dictation markers from the Note.  Both completions are automatic.
+
| style="border:1px solid gray;"|User who places the dictation marker
 +
| style="border:1px solid gray;"|Dictating and sending dictations linked to all outstanding dictation markers in Note associated with the single dictating provider: there may be additional incomplete dictations linked to another provider and another task specific to the other provider.  The task can also be completed by deleting the dictation markers from the Note.  Both completions are automatic
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
 
| style="border:1px solid gray;"|Ad Hoc Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|Task type for client specific tasks related to note
 
| style="border:1px solid gray;"|Ad Hoc Note
 
| style="border:1px solid gray;"|The user specified on the New Task page
 
| style="border:1px solid gray;"|Select the task, and then click Done.
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|Clients can create custom task names related to note.
 
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Go to Note
 
| style="border:1px solid gray;"|Go to Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|Task type for tasks where a user is expected to go to a note.  This task does not apply to the Version 11.x Note module (see Go To Noteform Note).
+
| style="border:1px solid gray;"|Task type for tasks where a user is expected to go to a note.  This task does not apply to the Version 11.x Note module (see Go To Noteform Note)
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|Process Note
 
| style="border:1px solid gray;"|User specified on the Note New Task page
 
| style="border:1px solid gray;"|User specified on the Note New Task page
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
| style="border:1px solid gray;"|Since task is created manually, multiple GoToNote tasks can be created for same provider/ note combination, because tasks may be generated for different workflow reasons and have unique task comments.
+
| style="border:1px solid gray;"|Since task is created manually, multiple GoToNote tasks can be created for same provider/ note combination, because tasks may be generated for different workflow reasons and have unique task comments
 
|-
 
|-
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The Note has been signed but not finalized because the user doesn’t have ownership authority sufficient for the note nor finalizing authority for the note.  Initial signing indicates note input has been completed or is ready for next clinician.  Task can be manually generated at any time as well.
+
| style="border:1px solid gray;"|The Note has been signed but not finalized because the user doesn’t have ownership authority sufficient for the note nor finalizing authority for the note.  Initial signing indicates note input has been completed or is ready for next clinician.  Task can be manually generated at any time as well
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Sign Note
 
| style="border:1px solid gray;"|Note owner (or a manually linked provider)
 
| style="border:1px solid gray;"|Note owner (or a manually linked provider)
| style="border:1px solid gray;"|When the document is signed by the assignee.
+
| style="border:1px solid gray;"|When the document is signed by the assignee
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|In cases where authorizing provider signature is required, a prompt will force user to route to authorizing provider defaulting to that of the Default Authorizing user for that session – new feature of v11.  If no default authorizing user defined for session, one will have to be chosen
 
| style="border:1px solid gray;"|In cases where authorizing provider signature is required, a prompt will force user to route to authorizing provider defaulting to that of the Default Authorizing user for that session – new feature of v11.  If no default authorizing user defined for session, one will have to be chosen
Line 504: Line 507:
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The Note is amended.  Amending a Note should be based on what is done – explicitly - preserving the snapshot. Once the Note is finalized, an amendment will not happen automatically.  The administrator can decide which event will trigger amendments.
+
| style="border:1px solid gray;"|The Note is amended.  Amending a Note should be based on what is done – explicitly - preserving the snapshot. Once the Note is finalized, an amendment will not happen automatically.  The administrator can decide which event will trigger amendments
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|User who last finalized the Note
 
| style="border:1px solid gray;"|User who last finalized the Note
| style="border:1px solid gray;"|Signing and finalizing the ammended Note.
+
| style="border:1px solid gray;"|Signing and finalizing the amended Note
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 524: Line 527:
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|When a task is desired that takes the user to a note. This is not completed automatically.
+
| style="border:1px solid gray;"| When a user is selected to receive a Carbon Copy of the document via a Task (rather than a printed or faxed copy) AND after the document completes a step that triggers its distribution (i.e. if configured to
 +
generate on Final, tasks are generated for any CC task recipients when the document is finalized)
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|User specified on the Note New Task page
 
| style="border:1px solid gray;"|User specified on the Note New Task page
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 534: Line 538:
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When a task is desired that takes user to Note and completes automatically upon navigation.
+
| style="border:1px solid gray;"|When a task is needed  that takes user to the Note and completes automatically upon navigation
 
| style="border:1px solid gray;"|ViewNote
 
| style="border:1px solid gray;"|ViewNote
 
| style="border:1px solid gray;"|User specified on the Note New Task page
 
| style="border:1px solid gray;"|User specified on the Note New Task page
| style="border:1px solid gray;"|This task is automatically completed when the note is viewed.
+
| style="border:1px solid gray;"|This task is automatically completed when the note is viewed
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 544: Line 548:
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When the appointment is arrived, and the this task type is active.  No Note, document, or dictation has been started.
+
| style="border:1px solid gray;"|When the appointment is arrived, and the task type is active.  No Note, document, or dictation has been started
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|Appointment provider
 
| style="border:1px solid gray;"|Appointment provider
| style="border:1px solid gray;"|When the user creates a Note, document, or dictation linked to the encounter.
+
| style="border:1px solid gray;"|When the user creates a Note, document, or dictation linked to the encounter
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
| style="border:1px solid gray;"|
 
|-
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|Note
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|No
 
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
Line 574: Line 558:
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Created automatically by the system when a user who can sign and finalize the note chooses to sign the note, but not finalize it.
+
| style="border:1px solid gray;"|Created automatically by the system when a user who can sign and finalize the note chooses to sign the note, but not finalize it
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|Note owner
 
| style="border:1px solid gray;"|Note owner
| style="border:1px solid gray;"|When the user signs and finalizes the document.
+
| style="border:1px solid gray;"|When the user signs and finalizes the document
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 584: Line 568:
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Task type replacement for Version 11.x notes for Go To Note tasks.
+
| style="border:1px solid gray;"|Task type replacement for Version 11.x notes for Go To Note tasks
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|User specified on the Note New Task page
 
| style="border:1px solid gray;"|User specified on the Note New Task page
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 594: Line 578:
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This is the Version 11.x task replacement for the Sign Note task.
+
| style="border:1px solid gray;"|This is the Version 11.x task replacement for the Sign Note task
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|Note owner
 
| style="border:1px solid gray;"|Note owner
| style="border:1px solid gray;"|When the note owner signs the note.
+
| style="border:1px solid gray;"|When the note owner signs the note
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 604: Line 588:
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When a task is desired to notify patient upon note finalization independent of a carbon copy.
+
| style="border:1px solid gray;"|When a task is desired to notify patient upon note finalization independent of a carbon copy
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 614: Line 598:
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|Note (Version 11.x, not 10.x)
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When a task is desired to notify the provider upon note finalization independent of a carbon copy.
+
| style="border:1px solid gray;"|When a task is desired to notify the provider upon note finalization independent of a carbon copy
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|To Noteform Note Output
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 627: Line 611:
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|Ad Hoc Noteform Note
 
| style="border:1px solid gray;"|Dictating provider
 
| style="border:1px solid gray;"|Dictating provider
| style="border:1px solid gray;"|When the user submits the dictation.
+
| style="border:1px solid gray;"|When the user submits the dictation
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-
 +
| style="border:1px solid gray;"|Medical Complaint Call Back
 +
| style="border:1px solid gray;"|Note
 +
| style="border:1px solid gray;"|The user
 +
| style="border:1px solid gray;"|The user specifies this task type from any workspace
 +
| style="border:1px solid gray;"|Misc
 +
| style="border:1px solid gray;"|The user specified on the New Task Page
 +
| style="border:1px solid gray;"|When the user clicks Done
 +
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 +
| style="border:1px solid gray;"|Medical Problem or Complaint
 +
| style="border:1px solid gray;"|Note
 +
| style="border:1px solid gray;"|The user
 +
| style="border:1px solid gray;"|The user specifies this task type from any workspace
 +
| style="border:1px solid gray;"|Misc
 +
| style="border:1px solid gray;"|The user specified on the New Task Page
 +
| style="border:1px solid gray;"|When the user clicks Done
 +
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-
 +
| style="border:1px solid gray;"|Nursing Home Call Back
 +
| style="border:1px solid gray;"|Note
 +
| style="border:1px solid gray;"|The user
 +
| style="border:1px solid gray;"|The user specifies this task type from any workspace
 +
| style="border:1px solid gray;"|Misc
 +
| style="border:1px solid gray;"|The user specified on the New Task Page
 +
| style="border:1px solid gray;"|When the user clicks Done
 +
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 +
| style="border:1px solid gray;"|Review Unresolved Transcription
 +
| style="border:1px solid gray;"|Note
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|A dictation marker is returned and is unable to post to the structured note
 +
| style="border:1px solid gray;"|Process Note
 +
| style="border:1px solid gray;"|Dictating Provider
 +
| style="border:1px solid gray;"|The user copy/pastes the dictation into the Note and then clicks the Done button for the task
 +
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
Line 634: Line 658:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A Diagnostic Testing order requires additional order information.
+
| style="border:1px solid gray;"|A Diagnostic Testing order requires additional order information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Automatically when the order information is entered and the Note is saved.
+
| style="border:1px solid gray;"|Automatically when the order information is entered and the Note is saved
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 644: Line 668:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A Findings order requires additional order information.
+
| style="border:1px solid gray;"|A Findings order requires additional order information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Automatically when the order information is entered and the Note is saved.
+
| style="border:1px solid gray;"|Automatically when the order information is entered
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 654: Line 678:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A notification task that informs that the user placing an order has changed the Appointment status within order details to Appointment Needed.
+
| style="border:1px solid gray;"|A notification task generated when the order associated with the task requires a patient
 +
appointment. The appointment status flag is set to Appointment Needed
 
| style="border:1px solid gray;"|Specify Appointment
 
| style="border:1px solid gray;"|Specify Appointment
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The task is automatically completed when the user either (1) edits the appointment attribute of the order to Has Been Scheduled (this assumes that the patient has been scheduled, but their in not integrity check for that event), or (2) edits the Appointment attribute to either Not Needed or Patient Will Schedule, or (3) changes the order status to Completed, D/C, Canceled, or EIE.
+
| style="border:1px solid gray;"|The task is automatically completed when the user either (1) edits the appointment attribute of the order to Has Been Scheduled (this assumes that the patient has been scheduled, but there is not an integrity check for that event), or (2) edits the Appointment attribute to either Not Needed or Patient Will Schedule, or (3) changes the order status to Completed, D/C, Canceled, or EIE
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 664: Line 689:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|An Other order requires additional order information.
+
| style="border:1px solid gray;"|An Other Diagnostic Testing order requires additional order information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Automatically when the order information is entered and the Note is saved.
+
| style="border:1px solid gray;"|Automatically when the order information is entered
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 674: Line 699:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Created by a database job that queries for orders that expiration date has passed.  If query finds an order for which the expiration date has passed and the status of the order is neither Canceled nor D/C, then the task is created.  In creating the task, the order status is changed to Canceled or Discontinued with a Reason of Expired.
+
| style="border:1px solid gray;"|Created by a database job that queries for orders that expiration date has passed.  If query finds an order for which the expiration date has passed and the status of the order is neither Canceled nor D/C, then the task is created.  In creating the task, the order status is changed to Canceled or Discontinued with a Reason of Expired
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
Line 684: Line 709:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Created by a database job which queries for all orders whose overdue date has passed.  If query finds an order for which the overdue date has passed and the status of the order is neither Canceled nor D/C, then the task is created.
+
| style="border:1px solid gray;"|Created by a database job which queries for all orders whose overdue date has passed.  If query finds an order for which the overdue date has passed and the status of the order is neither Canceled nor D/C, then the task is created
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
Line 694: Line 719:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|Created when a Clinical Exchange document is imported and the Clinical Exchange Document Item Verification is Y and the clinical exchange document has at least one non-medication order or result.
+
| style="border:1px solid gray;"|Created when a Clinical Exchange document is imported and the Clinical Exchange Document Item Verification is Y and the Clinical exchange document has at least one non-medication order or result.
 
| style="border:1px solid gray;"|Order Notification
 
| style="border:1px solid gray;"|Order Notification
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|When all the patient\'s unverified non-medication orders have been either verified an added or removed.
+
| style="border:1px solid gray;"|When all the patient's unverified non-medication orders have been either verified and added or removed
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
| style="border:1px solid gray;"|Order Info
+
| style="border:1px solid gray;"|Order Info-Additional Info
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Saving an order that is missing data required to execute the order; in this case the order is placed in a status of Needs Info and this task is created.
+
| style="border:1px solid gray;"|When the order is saved with additional information question that are defined as “missing” answer results in Needs Info status or missing answer results in On Hold status and are unanswered
| style="border:1px solid gray;"|Order Information
+
| style="border:1px solid gray;"|Order Additional Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|When all the necessary information has been specified.
+
| style="border:1px solid gray;"|When the additional information questions have been answered
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 714: Line 739:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|System generated if an order fails medical necessity checking and an ABN disposition is not selected for the order and the system preference \'Hold Orders for ABN \' = No.
+
| style="border:1px solid gray;"|System generated if an order fails medical necessity checking and an ABN disposition is not selected for the order and the system preference \'Hold Orders for ABN \' = No. This task is inactive, but still supported for use in Enterprise EHR. To use this task, set it to Active
 
| style="border:1px solid gray;"|ABN Follow-Up
 
| style="border:1px solid gray;"|ABN Follow-Up
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Automatically completed if the order is edited to pass medical necessity checking.
+
| style="border:1px solid gray;"|Automatically completed if the order is edited to pass medical necessity checking
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Order Notification
 
| style="border:1px solid gray;"|Order Notification
| style="border:1px solid gray;"|Order
+
| style="border:1px solid gray;"|Order/Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The intent of this task is to notify an authorizing provider that an order has been entered in the system by another user that requires their authorization.  The authorizing provider does not need to review and approve the unauthorized order(s) associated with the task for the order(s) to be activated. This task is applicable to medication and non-medication orders.
+
| style="border:1px solid gray;"|The intent of this task is to notify an authorizing provider that an order has been entered in the system by another user that requires their authorization.  The authorizing provider does not need to review and approve the unauthorized order(s) associated with the task for the order(s) to be activated. This task is applicable to medication and non-medication orders
 
| style="border:1px solid gray;"|Notify Order
 
| style="border:1px solid gray;"|Notify Order
| style="border:1px solid gray;"|Supervising Provider for Non-medication and ordering provider for medications.
+
| style="border:1px solid gray;"|Supervising Provider for non-medication and ordering provider for medications
| style="border:1px solid gray;"|When the order is authorized by a user with sufficient authority.
+
| style="border:1px solid gray;"|When the order is authorized by a user with sufficient authority
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
 
| style="border:1px solid gray;"|Authorize Order
 
| style="border:1px solid gray;"|Authorize Order
| style="border:1px solid gray;"|Order
+
| style="border:1px solid gray;"|Order/Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The intent of this task is to notify an authorizing provider that an order has been entered in the system by another user that requires their authorization.  The authorizing provider must review and approve the unauthorized order(s) associated with the task for the order(s) to be activated.  This task is applicable to medication and non-medication orders.
 
| style="border:1px solid gray;"|The intent of this task is to notify an authorizing provider that an order has been entered in the system by another user that requires their authorization.  The authorizing provider must review and approve the unauthorized order(s) associated with the task for the order(s) to be activated.  This task is applicable to medication and non-medication orders.
 
| style="border:1px solid gray;"|Authorize Order
 
| style="border:1px solid gray;"|Authorize Order
| style="border:1px solid gray;"|Supervising Provider for Non-medication and ordering provider for medications
+
| style="border:1px solid gray;"|Supervising Provider for non-medication and ordering provider for medications
| style="border:1px solid gray;"|When the order is authorized by a user with sufficient authority.
+
| style="border:1px solid gray;"|When the order is authorized by a user with sufficient authority
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 744: Line 769:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The order interface authorize mode flag has been set to create a task when a new order is received.
+
| style="border:1px solid gray;"|The order interface authorize mode flag has been set to create a task when a new order is received
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|Miscellaneous
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Manually when the order is created or determined to not be needed.
+
| style="border:1px solid gray;"|Manually when the order is created or determined to not be needed
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 754: Line 779:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The order interface authorize mode flag has been set to create a task when an edited order is received.
+
| style="border:1px solid gray;"|The order interface authorize mode flag has been set to create a task when an edited order is received
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 764: Line 789:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The order interface authorize mode flag has been set to post audit information when a new or edited order is received.
+
| style="border:1px solid gray;"|The order interface authorize mode flag has been set to post audit information when a new or edited order is received
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The user acts upon the order.
+
| style="border:1px solid gray;"|The user acts upon the order
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 774: Line 799:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The order interface creates it based on if the authorize mode flag is set to require authorization when a new or edited order is received in TouchWorks.
+
| style="border:1px solid gray;"|The order interface creates it based on if the authorize mode flag is set to require authorization when a new or edited order is received in Allscripts Enterprise EHR
 
| style="border:1px solid gray;"|Authorize Order
 
| style="border:1px solid gray;"|Authorize Order
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Automatically when the order is authorized or the status is changed to Discontinued, Void, or Entered in Error.
+
| style="border:1px solid gray;"|Automatically when the order is authorized or the status is changed to Discontinued, Void, or Entered in Error
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 784: Line 809:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The ordering provider has the following Auto Print preference selected: Create Print Requisition Task on Order.  A user edits the order such that it enters a state that satisfies the print criteria.
+
| style="border:1px solid gray;"|The ordering provider has the following Auto Print preference selected: Create Print Requisition Task on Order.  A user edits the order such that it enters a state that satisfies the print criteria
 
| style="border:1px solid gray;"|Print Requisition
 
| style="border:1px solid gray;"|Print Requisition
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is automatically completed when the requisition is printed.
+
| style="border:1px solid gray;"|This task is automatically completed when the requisition is printed
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 794: Line 819:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The system creates this task automatically when the Financial Auth Status changes to Denied.
+
| style="border:1px solid gray;"|The system creates this task automatically when the Financial Auth Status changes to Denied
 
| style="border:1px solid gray;"|Authorization
 
| style="border:1px solid gray;"|Authorization
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The task is automatically completed when the Order Status is set to Active (activate the order) or set to Void (void the order).
+
| style="border:1px solid gray;"|The task is automatically completed when the Order Status is set to Active (activate the order) or set to Void (void the order)
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 804: Line 829:
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a prescription is written with an Action of Administer and any of the following fields on the Administration tab on the Medication Detail are blank: Dose, Route, Site, Admin by, and Admin date.
+
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a prescription is written with an action of Administer and any of the following fields on the Administration tab on the Medication Detail are blank: Dose, Route, Site, Admin by and Admin date
 
| style="border:1px solid gray;"|Administer Immunization
 
| style="border:1px solid gray;"|Administer Immunization
| style="border:1px solid gray;"|Ordering provider
+
| style="border:1px solid gray;"|Ordering Provider
| style="border:1px solid gray;"|This task is completed automatically by the system when the requirements for documenting the administration of a medication have been satisfied. The required documentation consists of the following fields on the Administration tab on the Medication Detail: Dose, Route, Site, Admin by, and Admin date.
+
| style="border:1px solid gray;"|This task is completed automatically by the system when the requirements for documenting the administration of a medication have been satisfied. The required documentation consists of the following fields on the Administration tab on the Medication Detail: Dose, Route, Site, Admin by and Admin date
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
 +
| style="border:1px solid gray;"|Immunization Documentation
 +
| style="border:1px solid gray;"|Order
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|The system creates this task when all of the immunization required fields needed to send an immunization to a registry have not been completed
 +
| style="border:1px solid gray;"|Document Immunization
 +
| style="border:1px solid gray;"|Ordering Provider
 +
| style="border:1px solid gray;"|This task is completed automatically by the system when the requirements for documenting the administration of an immunization have been completed. The required documentation consists of any
 +
required fields in the Administration Details section as well as any required questions in the Clinical Questions section of
 +
the Immunization Details Record Administration tab
 +
| style="border:1px solid gray;"|Yes
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Financial Auth
 
| style="border:1px solid gray;"|Financial Auth
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The system creates this task when the order associated with the task requires financial authorization.  Financial Auth is set to Needed.
+
| style="border:1px solid gray;"|The system creates this task when the order associated with the task requires financial authorization.  Financial Auth is set to Needed
 
| style="border:1px solid gray;"|Authorization
 
| style="border:1px solid gray;"|Authorization
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
Line 820: Line 857:
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Order Info-Problem
 
| style="border:1px solid gray;"|Order Info-Problem
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is automatically generated by the system when a non-med order is created without specifying a problem.  A non-med order requires an associated problem when the preference OrderProblemLinkingRequired is set to Needs Info Reason.||Order Information
+
| style="border:1px solid gray;"|The task is automatically generated by the system when a non-med order is created without specifying a problem.  A non-med order requires an associated problem when the preference OrderProblemLinkingRequired is set to Needs Info Reason
 +
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is automatically completed when a problem is associated to the order and commited to the patient record.
+
| style="border:1px solid gray;"|This task is automatically completed when a problem is associated to the order and committed to the patient record
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Order Info – F/up
 
| style="border:1px solid gray;"|Order Info – F/up
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates a follow-up order, but leaves one or more fields blank and the fields are required for the order to be executed and fully documented, but are not required to create the order in the system.
+
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates a follow-up order, but leaves one or more fields blank and the fields are required for the order to be executed and fully documented, but are not required to create the order in the system
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page.  Additionally, the associated task Sign Note must be completed separately.
+
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page.  Additionally, the associated task Sign Note must be completed separately
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Order Info-Lab
 
| style="border:1px solid gray;"|Order Info-Lab
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates a laboratory order, but leaves one or more fields blank.  The fields are required for the order to be executed and fully documented, but are not required to create the order in the system.
+
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates a laboratory order, but leaves one or more fields blank.  The fields are required for the order to be executed and fully documented, but are not required to create the order in the system
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page.  Additionally, the associated task Sign Note must be completed separately.
+
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page.  Additionally, the associated task Sign Note must be completed separately
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Order Info-Refer
 
| style="border:1px solid gray;"|Order Info-Refer
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates a referral order, but leaves one or more fields blank.  The fields are required for the order to be executed and fully documented, but are not required to create the order in the system.
+
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates a referral order, but leaves one or more fields blank.  The fields are required for the order to be executed and fully documented, but are not required to create the order in the system
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page.  Additionally, the associated task Sign Note must be completed separately.
+
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Order Info-Image
 
| style="border:1px solid gray;"|Order Info-Image
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates an image order, but leaves one or more fields blank.  The fields are required for the order to be executed and fully documented, but are not required to create the order in the system.
+
| style="border:1px solid gray;"|The task is automatically generated by the system when a user creates a diagnostic imaging order, but leaves one or more fields blank.  The fields are required for the order to be executed and fully documented, but are not required to create the order in the system
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Order Information
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page.  Additionally, the associated task Sign Note must be completed separately.
+
| style="border:1px solid gray;"|This task is automatically completed when the required order information is entered in the Order Detail page
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Obtain ABN Order
 
| style="border:1px solid gray;"|Obtain ABN Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is created when an order is saved with an ABN Disposition of null and ABN Status of Failed Medical Necessity or Failed MN-Not Holding.  The client may use either Failed Medical Necessity or Failed MN-Not Holding, not both.
+
| style="border:1px solid gray;"|The task is created when an order is saved with an ABN Disposition of null and ABN Status of Failed Medical Necessity or Failed MN-Not Holding.  The client may use either Failed Medical Necessity or Failed MN-Not Holding, not both
 
| style="border:1px solid gray;"|Specify Disposition
 
| style="border:1px solid gray;"|Specify Disposition
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The task is automatically completed when the user either (1) makes a change to the order such that the resulting medical necessity status is no longer Failed Medical Necessity or Failed MN-Not Holding, or (2) edits the ABN Disposition attribute on Order to a non-NULL value, or (3) changes the Order Status to D/C, Canceled, or EIE.
+
| style="border:1px solid gray;"|The task is automatically completed when the user either (1) makes a change to the order such that the resulting medical necessity status is no longer Failed Medical Necessity or Failed MN-Not Holding, or (2) edits the ABN Disposition attribute on Order to a non-NULL value, or (3) changes the Order Status to D/C, Canceled, or EIE
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Authorized Order
 
| style="border:1px solid gray;"|Authorized Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is created when an order requiring approval is activated by a supervising provider.
+
| style="border:1px solid gray;"|The task is created when an order requiring approval is activated by a supervising provider
 
| style="border:1px solid gray;"|Order Notification
 
| style="border:1px solid gray;"|Order Notification
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Select the task, and then click Done.
+
| style="border:1px solid gray;"|Select the task, and then click Done
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Call Order
 
| style="border:1px solid gray;"|Call Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when a Communication Method of Call Order is the chosen for the order.
+
| style="border:1px solid gray;"|This task is created when a Communication Method of Call Order is the chosen for the order
| style="border:1px solid gray;"|Call||Ordering provider
+
| style="border:1px solid gray;"|Call
 +
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Rejected Order
 
| style="border:1px solid gray;"|Rejected Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when an order requiring approval is voided by a supervising provider.
+
| style="border:1px solid gray;"|This task is created when an order requiring approval is voided by a supervising provider
 
| style="border:1px solid gray;"|Order Notification
 
| style="border:1px solid gray;"|Order Notification
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Select the task, and then click Done.
+
| style="border:1px solid gray;"|Select the task, and then click Done
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Dispense Order
 
| style="border:1px solid gray;"|Dispense Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when an ordering action of Dispense is the chosen for the order.
+
| style="border:1px solid gray;"|This task is created when an ordering action of Dispense is chosen for the order
 
| style="border:1px solid gray;"|Dispense
 
| style="border:1px solid gray;"|Dispense
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
Line 918: Line 957:
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Perform Order
 
| style="border:1px solid gray;"|Perform Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when the order’s Communicated By box is set to Perform Order.
+
| style="border:1px solid gray;"|This task is created when the order’s Communicated By box is set to Perform Order
 
| style="border:1px solid gray;"|Perform
 
| style="border:1px solid gray;"|Perform
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|When the status of the order is Completed or Resulted, automatically complete the task. D/C and EIE should not complete the task – those order statuses should remove the task.
+
| style="border:1px solid gray;"|When the status of the order is Completed or Resulted, automatically complete the task. D/C and EIE should not complete the task – those order statuses should remove the task
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Go to Order
 
| style="border:1px solid gray;"|Go to Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|Order
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|User will select an order, and then click New Task, and manually enter the pertinent information into the task form.
+
| style="border:1px solid gray;"|User will select an order, and then click New Task, and manually enter the pertinent information into the task form
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|Process Order
 
| style="border:1px solid gray;"|User specified on the Orders New Task page
 
| style="border:1px solid gray;"|User specified on the Orders New Task page
| style="border:1px solid gray;"|The user completes the task by selecting it, and then clicking Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-
 +
| style="border:1px solid gray;"|Pt Merge-Enc
 +
| style="border:1px solid gray;"|Patient lists
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|This task is created when a patient is added to a service list
 +
| style="border:1px solid gray;"|Patient merge encounter
 +
| style="border:1px solid gray;"|Local Patient Merge Team
 +
| style="border:1px solid gray;"|When the local patient is merged with a valid patient in the database using Merge Patient Encounters workspace
 +
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
| style="border:1px solid gray;"|OrderInfo - Additional Info
+
| style="border:1px solid gray;"|Call Patient Communication
| style="border:1px solid gray;"|Order
+
| style="border:1px solid gray;"|Population Health Mgmt
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When the order is saved with additional information question that are defined as \"missing answer results in Needs Info status\" or \"missing answer results in On Hold status\" and are unanswered.
+
| style="border:1px solid gray;"|This task is generated when the patient’s preferred method of communication is Phone and the patient is on the Pursuit List for a Patient Action Set. The Patient Action Set also includes the action to generate Call Patient Communication tasks
| style="border:1px solid gray;"|Order Additional Information
+
| style="border:1px solid gray;"|Call
| style="border:1px solid gray;"|Ordering provider
+
| style="border:1px solid gray;"|Delegated to a user or team
| style="border:1px solid gray;"|When the additional information questions have been answered.
+
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|No
+
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
| style="border:1px solid gray;"|OrderInfo - Additional Info
+
| style="border:1px solid gray;"|Mail Patient Communication
| style="border:1px solid gray;"|Result
+
| style="border:1px solid gray;"|Population Health Mgmt
| style="border:1px solid gray;"|Ordering provider
+
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|A user verifies one or more results for an encounter, and the Action is Mail or Call and Mail. The results have been cited to a note.
+
| style="border:1px solid gray;"|This task is generated when the patient’s preferred method of communication is Mail and the patient is on the Pursuit List for a Patient Action Set. The Patient Action Set also includes the action to generate Mail Patient Communication tasks
| style="border:1px solid gray;"|Process Note
+
| style="border:1px solid gray;"|Mail
| style="border:1px solid gray;"|Another user
+
| style="border:1px solid gray;"|Delegated to a user or team
| style="border:1px solid gray;"|The user calls the patient with the results and then manually completes the task on the task list.
+
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 962: Line 1,011:
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|If any orders on a requisition have a label, check the auto-print defaults.  If the Create Print Label Task on Order option is checked, then this task is created.
+
| style="border:1px solid gray;"|If any orders on a requisition have a label, check the auto-print defaults.  If the Create Print Label Task on Order option is checked, then this task is created
 
| style="border:1px solid gray;"|Print Label
 
| style="border:1px solid gray;"|Print Label
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The task is automatically completed with the item is queued in the printer queue.
+
| style="border:1px solid gray;"|The task is automatically completed with the item is queued in the printer queue
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
| style="border:1px solid gray;"|This task was renamed to Print Label in v11.  In previous versions, this task was Print Specimen.
+
| style="border:1px solid gray;"|This task was renamed to Print Label in v11.  In previous versions, this task was Print Specimen
 
|-
 
|-
 
| style="border:1px solid gray;"|Go to Result
 
| style="border:1px solid gray;"|Go to Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|In the Results workspace, select a result, click New Task, and complete the Task page.
+
| style="border:1px solid gray;"|In the Results workspace, select a result, click New Task, and complete the Task page
 
| style="border:1px solid gray;"|Process Result
 
| style="border:1px solid gray;"|Process Result
 
| style="border:1px solid gray;"|User specified on the Results New Task page
 
| style="border:1px solid gray;"|User specified on the Results New Task page
| style="border:1px solid gray;"|The user completes the task by selecting it, and then clicking Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 982: Line 1,031:
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Task is indented to facilitate the notification and printing of results that should be mailed to the patient. The system creates this task when verified results are available and the communication method for those results was specified as mail.
+
| style="border:1px solid gray;"|Task is indented to facilitate the notification and printing of results that should be mailed to the patient. The system creates this task when verified results are available and the communication method for those results was specified as mail
 
| style="border:1px solid gray;"|Print Document
 
| style="border:1px solid gray;"|Print Document
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|One of the following: (1) By the system when the document is printed via the task list Go To button. (2) By printing the document from the batch printing page.  (3) Manually.
+
| style="border:1px solid gray;"|One of the following: (1) By the system when the document is printed via the task list Go To button. (2) By printing the document from the batch printing page.  (3) Manually
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
Line 992: Line 1,041:
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The purpose of this task is generate a hardcopy of a patient’s results to be sent to another individual when the verified results become available. The task is generated when another user/provider is designated to be cc’d on the result and that preferred communication method is specified as PRINT.
+
| style="border:1px solid gray;"|The purpose of this task is generate a hardcopy of a patient’s results to be sent to another individual when the verified results become available. The task is generated when another user/provider is designated to be cc’d on the result and that preferred communication method is specified as PRINT
 
| style="border:1px solid gray;"|Print Encounter Results for Distribution
 
| style="border:1px solid gray;"|Print Encounter Results for Distribution
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The task is complete when the item is queued in the print queue.
+
| style="border:1px solid gray;"|The task is complete when the item is queued in the print queue
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
| style="border:1px solid gray;"|Call ResultsR
+
| style="border:1px solid gray;"|Call Patient with Results
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
| style="border:1px solid gray;"|Ordering provider
+
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The user verifies one or more results for an encounter, and the Action is Call or Call and Mail.  The results have not been cited to a note.
+
| style="border:1px solid gray;"|This task is intended to facilitate the notification and processing of results that should be phoned to the patient. The system creates this task when verified results are available and the communication method for those results was specified as phone. This is for V11 Notes
| style="border:1px solid gray;"|Process Encounter Results
+
| style="border:1px solid gray;"|Process Note Results
| style="border:1px solid gray;"|Another user
+
| style="border:1px solid gray;"|Ordering Provider
| style="border:1px solid gray;"|The user calls the patient with results and then manually completes the task on the task list.
+
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
 +
| style="border:1px solid gray;"|Error Results Verification
 +
| style="border:1px solid gray;"|Result
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"| This is a task generated by the system that detects that results were verified but a Note or patient communication does not exist. Only one task per patient and Ordering Provider match can be generated per day
 +
| style="border:1px solid gray;"|Misc
 +
| style="border:1px solid gray;"| Delegated to the Ordering Provider of the order/results that failed to generate the Note and Pt Comm task
 +
| style="border:1px solid gray;"|Done button
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Print Result
 
| style="border:1px solid gray;"|Print Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This is an ad-hoc task that is manually generated to advise a user to print a result.  Select the result, click New Task, and then choose Print Results.
+
| style="border:1px solid gray;"|This is an ad-hoc task that is manually generated to advise a user to print a result.  Select the result, click New Task, and then choose Print Results
 
| style="border:1px solid gray;"|Print Result
 
| style="border:1px solid gray;"|Print Result
 
| style="border:1px solid gray;"|Owner of the document to be printed
 
| style="border:1px solid gray;"|Owner of the document to be printed
| style="border:1px solid gray;"|The task is automatically completed when the result is queued in the printer queue.
+
| style="border:1px solid gray;"|The task is automatically completed when the result is queued in the printer queue
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Result Invalid
 
| style="border:1px solid gray;"|Result Invalid
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when a result is invalidated.
+
| style="border:1px solid gray;"|This task is created when a result is invalidated
 
| style="border:1px solid gray;"|Process Result
 
| style="border:1px solid gray;"|Process Result
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
Line 1,028: Line 1,087:
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Call Pt with Result
 
| style="border:1px solid gray;"|Call Pt with Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is indented to facilitate the notification and processing of results that should be phoned to the patient.  The system creates this task when verified results are available and the communication method for those results was specified as phone.
+
| style="border:1px solid gray;"|This task is indented to facilitate the notification and processing of results that should be phoned to the patient.  The system creates this task when verified results are available and the communication method for those results was specified as phone. This is for V10 notes
 
| style="border:1px solid gray;"|Process Note Results
 
| style="border:1px solid gray;"|Process Note Results
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
Line 1,038: Line 1,097:
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Verify Patient Results
 
| style="border:1px solid gray;"|Verify Patient Results
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task provides notification that a result is available for verification.  The task facilitates the verification of patient results. The task is created when a result is filed that requires verification.  The task priority is dictated by the Result Status.
+
| style="border:1px solid gray;"|This task provides notification that a result is available for verification.  The task facilitates the verification of patient results. The task is created when a result is filed that requires verification.  The task priority is dictated by the Result Status
 
| style="border:1px solid gray;"| Verify Patient Results
 
| style="border:1px solid gray;"| Verify Patient Results
 
| style="border:1px solid gray;"| Ordering provider
 
| style="border:1px solid gray;"| Ordering provider
| style="border:1px solid gray;"|Completed when the all results associated with the encounter and ordering provider combination have either been verified or the ordering provider for the result has been changed another user
+
| style="border:1px solid gray;"|Completed when the all results associated with the encounter and ordering provider combination have either been verified or the ordering provider for the result has been changed to another user
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Schedule Results F/Up
 
| style="border:1px solid gray;"|Schedule Results F/Up
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When a result is verified with a patient communication action of Schedule appointment to discuss results.
+
| style="border:1px solid gray;"|When a result is verified with a patient communication action of Schedule appointment to discuss results
 
| style="border:1px solid gray;"|System Miscellaneous
 
| style="border:1px solid gray;"|System Miscellaneous
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|Manually completed.
+
| style="border:1px solid gray;"|Manually completed
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Print Result for Chart
 
| style="border:1px solid gray;"|Print Result for Chart
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When a results is verified and the applicable auto-print defaults have the “create result update task when verified” or the “create result update task when received” checkbox checked.
+
| style="border:1px solid gray;"|When a result is verified and the applicable auto-print defaults have the “create result update task when verified” or the “create result update task when received” checkbox checked
 
| style="border:1px solid gray;"|Result Update
 
| style="border:1px solid gray;"|Result Update
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|One of the following: (1) By the system when the document is printed via the task list Go To button. (2) By printing the document from the batch printing page.  (3) Manually.
+
| style="border:1px solid gray;"|One of the following: (1) By the system when the document is printed via the task list Go To button. (2) By printing the document from the batch printing page.  (3) Manually
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Review Results
 
| style="border:1px solid gray;"|Review Results
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|Result
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|When a user is CC’d on a result with a notification method of task, a review result is created for them when the result is verified or if it does not need verification, when it is filed.
+
| style="border:1px solid gray;"|When a user is CC’d on a result with a notification method of task, a review result is created for them when the result is verified or if it does not need verification, when it is filed
 
| style="border:1px solid gray;"|Process Result
 
| style="border:1px solid gray;"|Process Result
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Manually completed or completed when the user who was CC’d performs the “Mark as Reviewed” action on the order.
+
| style="border:1px solid gray;"|Manually completed or completed when the user who was CC’d views the result and clicks Review
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Authorized Rx
 
| style="border:1px solid gray;"|Authorized Rx
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|Authorized Rx is a notification task informing a selected user that a prescription has been authorized.  The system generates this task when the Action selected when creating the Rx is any action except Phone (which creates a Call in Rx task).  The task instructs the user to follow-up with the patient, since there is a delay between the writing of the prescription and when it is conveyed to the pharmacy.
+
| style="border:1px solid gray;"|Authorized Rx is a notification task informing a selected user that a prescription has been authorized.  The system generates this task when the Action selected when creating the Rx is any action except Phone (which creates a Call in Rx task).  The task instructs the user to follow-up with the patient, since there is a delay between the writing of the prescription and when it is conveyed to the pharmacy
 
| style="border:1px solid gray;"|Med Notification
 
| style="border:1px solid gray;"|Med Notification
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task.
+
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task
| style="border:1px solid gray;"|The task owner will review the order and click Done to complete the task.
+
| style="border:1px solid gray;"|The task owner will review the order and click Done to complete the task
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Verify Rx
 
| style="border:1px solid gray;"|Verify Rx
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|Created when a Clinical Exchange document is imported and the Clinical Exchange Document Item Verification is Y and the clinical exchange document has at least one medication order.
+
| style="border:1px solid gray;"|Created when a Clinical Exchange document is imported and the Clinical Exchange Document Item Verification is Y and the clinical exchange document has at least one medication order
 
| style="border:1px solid gray;"|Med Notification
 
| style="border:1px solid gray;"|Med Notification
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|When all the patient\'s unverified meds have been either verified an added or removed.
+
| style="border:1px solid gray;"|When all the patient's unverified meds have been either verified and added or removed
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
| style="border:1px solid gray;"|Rx Chg Special
+
| style="border:1px solid gray;"|Medication Admin Documentation
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|In response to a message from PBM.
+
| style="border:1px solid gray;"| The system creates this task when all the indicated required fields to for a medication administration have not been completed
| style="border:1px solid gray;"|Concerning Med
+
| style="border:1px solid gray;"|Document medication administration
| style="border:1px solid gray;"|Ordering provider
+
| style="border:1px solid gray;"|Document medication Admin
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|The task is completed automatically by the system when the requirements for documenting the administration of an medication have been completed. The required documentation consists of any required fields in the Record Administration tab of the Medication details dialog
| style="border:1px solid gray;"|No
+
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
| style="border:1px solid gray;"|Rx Transfer
+
| style="border:1px solid gray;"|Review Cancel Denied
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|In response to a message from PBM.
+
| style="border:1px solid gray;"|This task will be created when the pharmacy is unable to cancel a prescription
| style="border:1px solid gray;"|Concerning Med
+
| style="border:1px solid gray;"|Notification
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|When the user clicks Done.
 
| style="border:1px solid gray;"|When the user clicks Done.
| style="border:1px solid gray;"|No
 
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
| style="border:1px solid gray;"|
 +
|-
 
| style="border:1px solid gray;"|Call in Rx
 
| style="border:1px solid gray;"|Call in Rx
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The system automatically creates this task when the prescriber selects the Action of Phone, when creating a prescription.
+
| style="border:1px solid gray;"|The system automatically creates this task when the prescriber selects the Action of Phone when creating a prescription
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The user may resubmit from the print queue or click Done on task list.
+
| style="border:1px solid gray;"|The user may resubmit from the print queue or click Done on task list
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Med Admin
 
| style="border:1px solid gray;"|Med Admin
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a prescription is written with an action of Administer and any of the following boxes on the Administration tab on the Medication Detail page are blank: Dose, Rroute, Site, Admin By, and Admin Date.
+
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a prescription is written with an action of Administer and any of the following boxes on the Administration tab on the Medication Detail page are blank: Dose, Route, Site, Admin By or Admin Date
 
| style="border:1px solid gray;"|Administer Medication
 
| style="border:1px solid gray;"|Administer Medication
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is completed automatically by the system when the requirements for documenting the administration of a medication have been satisfied. The required documentation consists of the following boxes on the Administration tab on the Medication Detail page: Dose, Route, Site, Admin by, and Admin date.
+
| style="border:1px solid gray;"|This task is completed automatically by the system when the requirements for documenting the administration of a medication have been satisfied. The required documentation consists of the following boxes on the Administration tab on the Medication Detail page: Dose, Route, Site, Admin by or Admin date
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Dispense Sample
 
| style="border:1px solid gray;"|Dispense Sample
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a prescription is written with an action of Dispense Sample and any of the required fields on the Record Sample tab on the Medication Detail are blank:  Quantity, Lot number, Expiration date, Dispensed By, and Dispensed Date.
+
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a prescription is written with an action of Dispense Sample and any of the required fields on the Record Sample tab on the Medication Detail are blank:  Quantity, Lot number, Expiration date, Dispensed By or Dispensed Date
 
| style="border:1px solid gray;"|Dispense Sample
 
| style="border:1px solid gray;"|Dispense Sample
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is completed automatically by the system when all required fields on the Record Sample tab have been populated.
+
| style="border:1px solid gray;"|This task is completed automatically by the system when all required fields on the Record Sample tab have been populated
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Rx Renew Request
 
| style="border:1px solid gray;"|Rx Renew Request
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a REFREQ message is received from a SCRIPT standard enabled pharmacy.
+
| style="border:1px solid gray;"|The system creates this task for the “Rx by” provider when a REFREQ message is received from a SCRIPT standard enabled pharmacy
 
| style="border:1px solid gray;"|Concerning Med
 
| style="border:1px solid gray;"|Concerning Med
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task.
+
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task
| style="border:1px solid gray;"|Selecting one of the Grant/Refuse controls automatically completes the task.
+
| style="border:1px solid gray;"|Selecting one of the Grant/Refuse controls automatically completes the task
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Rx Xmit Fail
 
| style="border:1px solid gray;"|Rx Xmit Fail
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The system creates this task when an error is returned from the CSS Spooler indicating that a SCRIPT transmission of a NEWRX or REFREQ has failed.
+
| style="border:1px solid gray;"|The system creates this task when an error is returned from the CSS Spooler indicating that a SCRIPT transmission of a NEWRX or REFREQ has failed
 
| style="border:1px solid gray;"|Concerning Med
 
| style="border:1px solid gray;"|Concerning Med
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task.
+
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task
| style="border:1px solid gray;"|The task owner will review the order and either remove it from the page or click Done from the task list.
+
| style="border:1px solid gray;"|The task owner will review the order and either remove it from the page or click Done from the task list
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Rx Info-Problem
 
| style="border:1px solid gray;"|Rx Info-Problem
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The task is automatically generated by the system when a med order is created without specifying a problem.  An Rx requires an associated problem when the preference PrescribeProblemLinkingRequired is set to Needs Info Reason.
+
| style="border:1px solid gray;"|The task is automatically generated by the system when a med order is created without specifying a problem.  An Rx requires an associated problem when the preference PrescribeProblemLinkingRequired is set to Needs Info Reason
 
| style="border:1px solid gray;"|Rx Info
 
| style="border:1px solid gray;"|Rx Info
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|This task is automatically completed when a problem is associated to the order and commited to the patient record.
+
| style="border:1px solid gray;"|This task is automatically completed when a problem is associated to the order and committed to the patient record
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Med Renewal
 
| style="border:1px solid gray;"|Med Renewal
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|This is a general-purpose task launched from the Medications page with a medication selected. Since the task is ad hoc, the creator must enter instructions in the Comments box that fully define the task for the recipient.  For example, this task may be created by non-prescribing user who must request a renewal on behalf of a patient or provider.
+
| style="border:1px solid gray;"|This is a general-purpose task launched from the Medications page with a medication selected. Since the task is ad hoc, the creator must enter instructions in the Comments box that fully define the task for the recipient.  For example, this task may be created by non-prescribing user who must request a renewal on behalf of a patient or provider
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|User specified on the New Task page  
 
| style="border:1px solid gray;"|User specified on the New Task page  
| style="border:1px solid gray;"|The task is automatically completed when the medication is renewed.  If the med is not renewed, complete the task by clicking Done from the task list.
+
| style="border:1px solid gray;"|The task is automatically completed when the medication is renewed.  If the med is not renewed, complete the task by clicking Done from the task list
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Go to Med
 
| style="border:1px solid gray;"|Go to Med
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|A user
 
| style="border:1px solid gray;"|A user
| style="border:1px solid gray;"|This is a general-purpose task launched from the medications page with a medication selected. Since the task is ad hoc, the creator must enter instructions in the Comments field that fully define the task for the recipient.  For example, the patient may have called in with a reaction to the medication and is requesting the provider follow up with the patient regarding the med.
+
| style="border:1px solid gray;"|This is a general-purpose task launched from the medications page with a medication selected. Since the task is ad hoc, the creator must enter instructions in the Comments field that fully define the task for the recipient.  For example, the patient may have called in with a reaction to the medication and is requesting the provider follow up with the patient regarding the med
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|User specified on the Medications New Task page
 
| style="border:1px solid gray;"|User specified on the Medications New Task page
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Rx Info-Pharm
 
| style="border:1px solid gray;"|Rx Info-Pharm
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is automatically created when generating a prescription and the destination pharmacy incomplete or unknown.  The applicable Rx actions that will generate this task are: Retail, Mail Order, and Phone.  All other prescribing actions shall not create this task.
+
| style="border:1px solid gray;"|This task is automatically created when generating a prescription and the destination pharmacy is incomplete or unknown.  The applicable Rx actions that will generate this task are: Retail, Mail Order and Phone.  All other prescribing actions shall not create this task
 
| style="border:1px solid gray;"|Rx Info-Pharm
 
| style="border:1px solid gray;"|Rx Info-Pharm
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The task is completed when pharmacy information for all med orders for the patient – provider combination is provided.
+
| style="border:1px solid gray;"|The task is completed when pharmacy information for all med orders for the patient – provider combination is provided
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Rx Info-Address
 
| style="border:1px solid gray;"|Rx Info-Address
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is automatically created when generating a prescription for a mail order pharmacy and the patient’s mailing address is incomplete or unknown.
+
| style="border:1px solid gray;"|This task is automatically created when generating a prescription for a mail order pharmacy and the patient’s mailing address is incomplete or unknown
 
| style="border:1px solid gray;"|Rx Info-Address
 
| style="border:1px solid gray;"|Rx Info-Address
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|Select the task from the task list and click Done.
+
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-style="background:#FAF8CC;"
+
|-
 
| style="border:1px solid gray;"|Rx Info-PBM
 
| style="border:1px solid gray;"|Rx Info-PBM
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is automatically created when generating a prescription that is missing specific benefit information required by the destination pharmacy.  The pharmacies and the information required by these pharmacies is defined in the database table, PHARM_REQ_FLDS.
+
| style="border:1px solid gray;"|This task is automatically created when generating a prescription that is missing specific benefit information required by the destination pharmacy.  The pharmacies and the information required by these pharmacies is defined in the database table, PHARM_REQ_FLDS
 
| style="border:1px solid gray;"|Rx Info-PBM
 
| style="border:1px solid gray;"|Rx Info-PBM
 
| style="border:1px solid gray;"|Ordering provider
 
| style="border:1px solid gray;"|Ordering provider
| style="border:1px solid gray;"|The task is completed when all required Rx benefit fields for the patient are updated.
+
| style="border:1px solid gray;"|The task is completed when all required Rx benefit fields for the patient are updated
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
|-
+
|-style="background:#FAF8CC;"
 
| style="border:1px solid gray;"|Authorize Non-Formulary Medication
 
| style="border:1px solid gray;"|Authorize Non-Formulary Medication
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when a non-formulary medication has been prescribed and the Med preference PrescribeNonFormularyAuthReq = Y.
+
| style="border:1px solid gray;"|This task is created when a non-formulary medication has been prescribed and the Med preference PrescribeNonFormularyAuthReq = Y
 
| style="border:1px solid gray;"|Authorize Medication
 
| style="border:1px solid gray;"|Authorize Medication
 
| style="border:1px solid gray;"|Utilization review physician
 
| style="border:1px solid gray;"|Utilization review physician
| style="border:1px solid gray;"|This task is completed automatically when the user takes an action on the Authorize Orders page.  To authorize: Place a checkmark in the check boxes next to the medication, and then click Authorize.  To reject: Click Edit, select Void from the Status list, and then click Apply & Close.
+
| style="border:1px solid gray;"|This task is completed automatically when the user takes an action on the Authorize Orders page.  To authorize: Place a checkmark in the check boxes next to the medications and then click Authorize.  To reject: Click Edit, select Void from the Status list, and then click Apply & Close
 +
| style="border:1px solid gray;"|No
 +
| style="border:1px solid gray;"|
 +
|-
 +
| style="border:1px solid gray;"|Call in Failed Rx
 +
| style="border:1px solid gray;"|Rx+
 +
| style="border:1px solid gray;"|The system
 +
| style="border:1px solid gray;"|This task is created when an Rx fax job fails in the print queue
 +
| style="border:1px solid gray;"|Call
 +
| style="border:1px solid gray;"|Ordering Provider
 +
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|No
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
| style="border:1px solid gray;"|Call in Failed Rx
+
| style="border:1px solid gray;"|Med Renewal Due
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when an Rx fax job fails in the print queue.
+
| style="border:1px solid gray;"|This task is created when the medication Expected Action is set to Renew and the date associated with that action occurs. It's based on the preference: DaysBeforeRxActionDateToConsiderNearDue. This preference specifies the number of days before the expected action date that the task should be created. This task is not created for Med Admin and Immunization Admin renewals
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|
+
| style="border:1px solid gray;"|Completed when the all medication renewals associated with the patient-ordering provider combination have either been renewed, the expected action trigger has changed, the medication status has changed, or the ordering provider for the medication has been changed another user.  To complete the task do one of the following: (1) Update the therapy end date to a future date (the therapy remains active).  (2)  Renew the therapy (remains active). (3)  Change the medication “expected action” (evaluate or stop).  (4)  Change the medication status (Complete, D/C, EIE)
| style="border:1px solid gray;"|No
+
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
| style="border:1px solid gray;"|Med Renewal Due
+
| style="border:1px solid gray;"|Med Renewal Request
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when the medication Expected Action is set to Renew and the date associated with that action comes to pass. This task is not created for Med Admin and Immunization Admin renewals.
+
| style="border:1px solid gray;"| This task is created when the medication Expected Action is set to Evaluate and the date associated with the action meets the criteria set in the Days Before Rx Action Date to Consider Near Due medication preference
 
| style="border:1px solid gray;"|Process Med
 
| style="border:1px solid gray;"|Process Med
 +
| style="border:1px solid gray;"|Ordering Provider
 +
| style="border:1px solid gray;"|When the user clicks Done
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
| style="border:1px solid gray;"|Completed when the all medication renewals associated with the patient-ordering provider combination have either been renewed, the expected action trigger has changed, the medication status has changed, or the ordering provider for the medication has been changed another user.  To complete the task do one of the following: (1) Update the therapy end date to a future date (the therapy remains active).  (2)  Renew the therapy (remains active). (3)  Change the medication “expected action” (evaluate, or stop).  (4)  Change the medication status (Complete, D/C, EIE).
 
| style="border:1px solid gray;"|Yes
 
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
Line 1,262: Line 1,331:
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|Rx+
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when the status of an unauthorized medication order is set to Void.
+
| style="border:1px solid gray;"|This task is created when the status of an unauthorized medication order is set to Void
 
| style="border:1px solid gray;"|Med Notification
 
| style="border:1px solid gray;"|Med Notification
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task.
+
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task
 
| style="border:1px solid gray;"|The task owner will review the order and click Done to complete the task.
 
| style="border:1px solid gray;"|The task owner will review the order and click Done to complete the task.
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
| style="border:1px solid gray;"|Rx Change Request
+
| style="border:1px solid gray;"|Call in Cancel Rx
| style="border:1px solid gray;"|Rx+
+
| style="border:1px solid gray;"|Rx
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is used to process Change Requests received from a SCRIPT Standard enabled pharmacy.  A change request may take one of three forms: Generic Substitution, Therapeutic Alternative, Prior Authorization Request.  The pharmacist may suggest up to nine alternatives.
+
| style="border:1px solid gray;"|This task is created when an Rx cancellation cannot be sent electronically
| style="border:1px solid gray;"|Concerning Med
+
| style="border:1px solid gray;"|Call
| style="border:1px solid gray;"|The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task.
+
| style="border:1px solid gray;"|Ordering Provider
| style="border:1px solid gray;"|The task owner will review the order and click Done to complete the task.  When the change is granted: Complete the task, add the new therapy to the patient’s active medication list, and void the original prescription.  When the medication is refused: try to match the prescription with the row representing the therapy.
+
| style="border:1px solid gray;"|When the user clicks Done
| style="border:1px solid gray;"|No
+
| style="border:1px solid gray;"|Yes
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-style="background:#FAF8CC;"
 
|-style="background:#FAF8CC;"
| style="border:1px solid gray;"|Review Scan Document
+
| style="border:1px solid gray;"|External Medical Hx Summary
| style="border:1px solid gray;"|Scan
+
| style="border:1px solid gray;"|Rx
| style="border:1px solid gray;"|A user
+
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|The user associates a Review Scan task with a scanned image from the TouchWorks Scan system, or from the TouchWorks Web New Task function.
+
| style="border:1px solid gray;"| This task is created when the application receives an response from the Wellpoint MHp indicating that patient data is available
| style="border:1px solid gray;"|Review Scan Document
+
| style="border:1px solid gray;"|Review Hx Summary
| style="border:1px solid gray;"|The specified users
+
| style="border:1px solid gray;"|Assign the task to the provider who sent the eligibility request for the patient
| style="border:1px solid gray;"|Manually completed.
+
| style="border:1px solid gray;"| Highlight the task from the task list and select Done
| style="border:1px solid gray;"|No
+
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|-
 
|-
| style="border:1px solid gray;"|Call in Cancel Rx
+
| style="border:1px solid gray;"|Chart Release Request
| style="border:1px solid gray;"|Rx
+
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|The user
 +
| style="border:1px solid gray;"|The user specifies this task type from any workspace
 +
| style="border:1px solid gray;"|Mis
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|
 +
| style="border:1px solid gray;"|
 +
|-style="background:#FAF8CC;"
 +
| style="border:1px solid gray;"|HIE CEDExport Fail
 +
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|The system
 
| style="border:1px solid gray;"|The system
| style="border:1px solid gray;"|This task is created when an Rx cancellation cannot be sent electronically.
+
| style="border:1px solid gray;"|This task is created when an automatic CED fails
| style="border:1px solid gray;"|Call
+
| style="border:1px solid gray;"|Mis
| style="border:1px solid gray;"|Ordering Provider
+
| style="border:1px solid gray;"|HIE CEDExport Fail
| style="border:1px solid gray;"|When the user clicks Done.
+
| style="border:1px solid gray;"|When the user clicks Done
| style="border:1px solid gray;"|Yes
+
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
| style="border:1px solid gray;"|
 
|}
 
|}

Revision as of 20:10, 18 May 2012

The following is a complete list of the tasks used in (v11.1.1) as of (06/21/08)

  • The Tasks are sorted by Module by default
  • The Allscripts spreadsheet can also be sorted by module but does not indicate which tasks are new in v11


  • For information on creating and editing task views click HERE
  • For a list of tasks not used in v11 click HERE.
Sortable table
Task Name: Module: Is created by: When: And the Task Action is: And assigned to: And is resolved: Is the task delegated? Additional comments
Call Back Base A user User specifies this type on the New Task page Miscellaneous User specified on the New Task page When the user clicks Done No
Notify Complete Base The system A task is completed that had the Notify when Complete option checked Notify When Complete User specified on the New Task page When the user clicks Done No
Notify Overdue Base The system A task that had the Notify when Overdue option checked is overdue Notify When Overdue User specified on the New Task page When the user clicks Done No
Confirm Patient Address Base A user The user specifies this task type on the New Task page Miscellaneous The user specified on the New Task page When the user clicks Done No
Confirm Patient Cardholder Info Base A user The user specifies this task type on the New Task page Miscellaneous User specified on the New Task page When the user clicks Done No
Confirm Patient Pharmacy Base A user The user specifies this type on the New Task page Miscellaneous User specified on the New Task page When the user clicks Done No
Follow up Base A user The user specifies this type on the New Task page Miscellaneous The user specified on the New Task page When the user clicks Done No
Hospital Call Base A user The user specifies this type on the New Task page Miscellaneous The user specified on the New Task page When the user clicks Done No
Miscellaneous Base A user The user specifies this type from any workspace Miscellaneous The user specified on the New Task page When the user clicks Done No
Personal Base A user The user specifies this type on the New Task page Miscellaneous User specified on the New Task page When the user clicks Done No
Personal CareGuide Overwritten CareGuide Template Management The system An admin user overwrites all personal CareGuide templates with an Allscripts Enterprise version Personal CareGuide Overwritten The provider(s) with personal versions of the CareGuide template When the user clicks Done (or Remove) No
Verify CCR Doc CED The system Created upon the receipt of an unsolicited Clinical Exchange Document Verify CCR Doc Document owner When the document is verified by the user No
Verify CCR Item CED The system Created upon the receipt of an unsolicited Clinical Exchange Document Verify CCR Item CCR Verify Team When there are no more unverified items for this document No
ABN Follow-up Charge The system A procedure charge is deemed medically not necessary and activated when the system preference Hold charges that fail medical necessity checking = No. System generated if a charge fails medical necessity checking Process Encounter Billing provider Manually completed when charges are edited in the practice manage system, and the user clicks Done. Auto-completed if charge is edited to pass medical necessity checking No
Go To Enc Form Charge A user A user clicks New Task on the Encounter Form page and indicates Go To Enc Form in the Task box or a follow-up task is created on the PDA Go To Enc Form User specified on the Encounter Form New Task page Manually completed when the user clicks Done No
Adjust Charges Charge The system A user edits or removes charges that are in a Submitted status Process Encounter Billing provider Manually completed when the charges are edited in the practice management system, and the user clicks Done No
Submit Enc Form Charge The system An arrived appointment is received by the system or when additional charges added to encounter without resubmitting encounter form. This task is inactive, but still supported for use in Enterprise EHR. To use this task, set it to Active Send Charges Billing provider; if none, then appointment provider; if none, then Encounter Follow-up Team Auto-completed when: 1. User clicks Submit regardless of the status of any change on that encounter. 2. User cancels a charge and the rules for creating a Submit Enc form task fail and there are no charges with a status of Needs Info, Saved, or Ready No
Review Enc Form Charge The system Created for coders and attending physicians to review the encounter forms submitted by specified providers before charges are submitted to the practice management system for billing. System generated when a user clicks or taps Submit and has the ChgWorksCreateRevEncFormTasks user preference set to Always or In Patient Only. (Admin not in the Personalize Charge page) Review Charges Enc Review team Auto-completed when all charges on the encounter are submitted by a user with the

ChgWorksCreateRevEncFormTasks user preference set to Never

No
Mng Chg Edits Charge The system If there are one or more charges on the encounter with the status of Needs Info Edit Charges Charge Edits Team Automatically completed when there are no charges on the encounter with status of Needs Info No
Submit IP Enc Charge The system System generated according to the preference on the service list and if an inpatient encounter form has charges on it that are not submitted and there is no Submit IP Enc task Send Charges Billing provider Auto-completed when: 1. User clicks Submit regardless of the status of any change on that encounter. 2. User cancels a charge and the rules for creating a Submit IP Enc task fail and there are no charges with a status of Needs Info, Saved, or Ready No
Submit Res Enc Charge The system System generated if a Submit Enc Form task does not exist for that Result Charge encounter. There cannot be an active Submit Enc Form task and an active Submit Res Enc task on the same encounter Send Charges Lab Charges Team Auto-completed when: 1. User clicks Submit regardless of the status of any change on that encounter. 2. User cancels a charge and the rules for creating a Submit Res Enc task fail and there are no charges with a status of Needs Info, Saved, or Ready. No
Print Enc Form Charge The system Through the encounter form automatic printing set-up, this task is created when all charges are submitted and reach a status of Submitted or Review. System generated if system option is set to create and all charges are either (1) Submitted or (2) Submitted or Review Print Enc Form Billing provider Auto-completed when the encounter form is printed No
Clinical Trial Match Clinical Trial The system This task is automatically generated via a nightly run to notify providers of possible clinical trials for a patient. Clinical Trial Contact Detail Page Clinical Trial Team When the user clicks Done after following up with the patient regarding the clinical trial Sign Letter Document The system A special kind of CC, this task is generated when the CC dialog is used to create a letter and that letter requires electronic signature to be finalized and the owner of the letter has an electronic workflow Sign Note Document owner When the user signs the document No
Verify Doc Document The system A transcription comes over an interface or through Allscripts Enterprise EHR Scan. Verify Transcription Provider selected in the transcription source file Automatically when the user verifies or invalidates the transcription No
Print Document Document The system A user selects the Create Print Doc Task option when signing a Note Print Document User who signed the Note When the document is queued for printing No
Reconcile Doc Document The system If the inbound document interface is configured to create this task when a patient associated with a document to be filed cannot be found in the clinical database Document Reconciliation The dictating provider associated with the document to be filed By the system when the task is performed and the document is linked to an existing patient No
Doc Update Document The system Transcription is verified or invalidated Note Update Provider selected in the transcription source file Automatically completed when transaction is verified or invalidated No
Review Document Document A user or the system When an unsolicited transcription document that has been sent through an interface to Allscripts Enterprise EHR Process Note The owner of the document sent via the interface When the user navigates to the document in Allscripts Enterprise EHR No
CorrectNote User Document A user When a user selects Req Correction for an unstructured document and chooses \'Author\' as the recipient Sign Note User specified as the Author of the document When the user signs the document No
CorrectNote Admin Document A user When a user selects Req Correction for an unstructured document and chooses \'Medical Records Team\' as the recipient CorrectNote Admin Medical Records Team When the user clicks Done No
CoSign Note Document A user When he/she needs a medication renewed Sign Note User specified on the Note New Task page When the user clicks Done No
Co-Sign Note Document A user When a V11 note is selected To NoteForm Note Output The user that is specified on the Note New Task page When the user signs the V11 Note No
Overdue Reminders HMP The system This task is generated by the system when there are overdue Med Admin, Orders, or Reminders Provider in the Planned By Field in HMP No
Unlinked Patient Initiate Unlink The system Unlinked Patient is one of two tasks associated with the Initiate “unlink” functionality. When Allscripts Enterprise EHR™ receives a unlink message from Initiate for a patient, the application automatically creates an Unlinked Patient task in the provider’s Task List. The task is named “Unlinked Patient” and it serves as a notification to the provider to check the patient’s chart and clean it up Review Chart Med Records Team Manual completion
Unlinked Patient Reminder Initiate Unlink The system When Allscripts Enterprise EHR™ receives a unlink message from Initiate for a patient, the application automatically creates an Unlinked Patient Reminder task in the Provider’s Task List. This task is created as inactive with a due date of two weeks in the future. It serves as a second notification to check the patient’s chart and clean up any Data that has been added to the chart since the first notification Review Chart Med Records Team Manual completion
ePat Message Patient Portal The system Patients can send a general message to their physician. This message type is forwarded to Allscripts Enterprise EHR, and displays as an ePat Message task with a link to a pre-created structured note which contains the text of the message. The physician can respond to the message using the Allscripts Enterprise EHR Note module Process Note Physician the patient sent the message to Click eReply on Note workspace No
ePat Registration Patient Portal The system Patients can send a request to register for Patient Portal privileges. The patient registration request is forwarded to the Allscripts Enterprise EHR system, and displays as an ePat Registration task in the physician’s task list. Physicians or clinical staff can choose to either accept or deny the request. Allscripts Enterprise EHR records the patient’s Patient Portal information and the response to the request, and then sends the response back to the patient Process ePatient Registration Physician the patient is registering with When task is performed and user clicks Accept or Deny on Patient Portal Patient Registration dialog No
ePat Appt Request Patient Portal The system Patients can send a request to their physician for an appointment. This message type is forwarded to Allscripts Enterprise EHR, and displays as an ePat Appt Request task. The Allscripts Enterprise EHR user can send a response back to the patient with the new appointment information. This information must be manually reconciled with the practice management system Process ePatient Appointment Physician the patient sent the message to Must be manually completed No
ePat Med Renew Patient Portal The system Patients can send a request to their physician for a prescription renewal. This message type is forwarded to Allscripts Enterprise EHR, and displays as an ePat Med Renew task with a link to a pre-created structured note which contains the text of the request Process Note Physician the patient sent the message to Click eReply on Note workspace No
ePat Visit Patient Portal The system Patients can send a request to their physician to provide an online consultation. The online consultation request is forwarded to Allscripts Enterprise EHR, and displays as an eVisit task with a link to a pre-created structured note which contains the text of the request. The physician can respond to the request using the Allscripts Enterprise EHR Note module Process Note Physician the patient sent the message to Click eReply on Note workspace No
ePat Message Failure Patient Portal The system The task is generated when a failure occurs with an inbound or outbound message Miscellaneous Provider who received or sent the message Must be manually completed No
Finish Note Note The system A Note has been saved, and no dictations or transcriptions are outstanding. The Note has not yet been signed Ad Hoc Noteform Note Note owner Signing the Note completes the task; the Note does not have to be finalized. Regardless of who completes this task, it should disappear from owner’s task list automatically. If a dictation or transcription related task is created, this task will automatically disappear/complete. If a returning transcription is reviewed and the note is not signed, a FinishNoteInput task will reappear or be created for the note owner No
Waiting for Transcription Note The system All dictation(s) have been sent, but the transcription(s) haven’t returned, so the Note is not ready for finishing note input or signature Ad Hoc Noteform Note Note owner The dictation is returned, or the outstanding dictation marker is removed. Yes
Review Covered Note Note The system Created for the appointment provider once the Note is finalized by a provider not linked to appointment. This task may or may not be linked to a note template. If not linked to a note template, then the task will not be created for the appointment provider if someone else becomes the owner and finalizes the note. This task can also be manually created. If manually created and created by system, then only one instance of the task should exist. If user is flagged to not receive these tasks then no task will be created for that appointment provider regardless of note template setting To Noteform Note Output Appointment provider by default or provider manually selected when created ad hoc When the assignee navigates to the Note No
Dictation Note A user Dictation marker is placed in the Note, but it has not yet been dictated Document Update User who places the dictation marker Dictating and sending dictations linked to all outstanding dictation markers in Note associated with the single dictating provider: there may be additional incomplete dictations linked to another provider and another task specific to the other provider. The task can also be completed by deleting the dictation markers from the Note. Both completions are automatic No
Go to Note Note A user Task type for tasks where a user is expected to go to a note. This task does not apply to the Version 11.x Note module (see Go To Noteform Note) Process Note User specified on the Note New Task page When the user clicks Done No Since task is created manually, multiple GoToNote tasks can be created for same provider/ note combination, because tasks may be generated for different workflow reasons and have unique task comments
Sign Note Note The system The Note has been signed but not finalized because the user doesn’t have ownership authority sufficient for the note nor finalizing authority for the note. Initial signing indicates note input has been completed or is ready for next clinician. Task can be manually generated at any time as well Sign Note Note owner (or a manually linked provider) When the document is signed by the assignee No In cases where authorizing provider signature is required, a prompt will force user to route to authorizing provider defaulting to that of the Default Authorizing user for that session – new feature of v11. If no default authorizing user defined for session, one will have to be chosen
Sign Amended Note Note The system The Note is amended. Amending a Note should be based on what is done – explicitly - preserving the snapshot. Once the Note is finalized, an amendment will not happen automatically. The administrator can decide which event will trigger amendments To Noteform Note Output User who last finalized the Note Signing and finalizing the amended Note No
Review Transcription Note A user Transcriptions for all outstanding dictation markers linked to same user and Note have returned and are ready for review by dictating provider. Ad Hoc Noteform Note Dictating provider Saving or signing note. Typically, the user would review, sign and finalize the Notes as part of workflow. Also, in some cases, supporting staff work these tasks and make edits to the returning transcriptions. This task allows this workflow. A Finish Note Input or Sign Note task will be created depending on the state of the Note/ document once ReviewTranscription task is worked. No
Review Note Note A user When a user is selected to receive a Carbon Copy of the document via a Task (rather than a printed or faxed copy) AND after the document completes a step that triggers its distribution (i.e. if configured to

generate on Final, tasks are generated for any CC task recipients when the document is finalized)

To Noteform Note Output User specified on the Note New Task page When the user clicks Done No
View Note Note The system When a task is needed that takes user to the Note and completes automatically upon navigation ViewNote User specified on the Note New Task page This task is automatically completed when the note is viewed No
Document Appointment Note The system When the appointment is arrived, and the task type is active. No Note, document, or dictation has been started Miscellaneous Appointment provider When the user creates a Note, document, or dictation linked to the encounter Yes
Note Signed but not Final Note (Version 11.x, not 10.x) The system Created automatically by the system when a user who can sign and finalize the note chooses to sign the note, but not finalize it To Noteform Note Output Note owner When the user signs and finalizes the document No
Go to Noteform Note Note (Version 11.x, not 10.x) The system Task type replacement for Version 11.x notes for Go To Note tasks Ad Hoc Noteform Note User specified on the Note New Task page When the user clicks Done No
Sign-Note Note (Version 11.x, not 10.x) The system This is the Version 11.x task replacement for the Sign Note task To Noteform Note Output Note owner When the note owner signs the note No
Notify Patient of Note Note (Version 11.x, not 10.x) The system When a task is desired to notify patient upon note finalization independent of a carbon copy To Noteform Note Output When the user clicks Done. Yes
Notify Provider of Note Note (Version 11.x, not 10.x) The system When a task is desired to notify the provider upon note finalization independent of a carbon copy To Noteform Note Output When the user clicks Done Yes
Noteform Dictation Note (Version 11.x, not 10.x) The system When a task is needed to process dictation Ad Hoc Noteform Note Dictating provider When the user submits the dictation No
Medical Complaint Call Back Note The user The user specifies this task type from any workspace Misc The user specified on the New Task Page When the user clicks Done No
Medical Problem or Complaint Note The user The user specifies this task type from any workspace Misc The user specified on the New Task Page When the user clicks Done No
Nursing Home Call Back Note The user The user specifies this task type from any workspace Misc The user specified on the New Task Page When the user clicks Done No
Review Unresolved Transcription Note The system A dictation marker is returned and is unable to post to the structured note Process Note Dictating Provider The user copy/pastes the dictation into the Note and then clicks the Done button for the task
Order Info-Test Order The system A Diagnostic Testing order requires additional order information Order Information Ordering provider Automatically when the order information is entered and the Note is saved Yes
Order Info-Find Order The system A Findings order requires additional order information Order Information Ordering provider Automatically when the order information is entered Yes
Schedule Appointment Order The system A notification task generated when the order associated with the task requires a patient

appointment. The appointment status flag is set to Appointment Needed

Specify Appointment Ordering provider The task is automatically completed when the user either (1) edits the appointment attribute of the order to Has Been Scheduled (this assumes that the patient has been scheduled, but there is not an integrity check for that event), or (2) edits the Appointment attribute to either Not Needed or Patient Will Schedule, or (3) changes the order status to Completed, D/C, Canceled, or EIE Yes
Order Info-Other Order The system An Other Diagnostic Testing order requires additional order information Order Information Ordering provider Automatically when the order information is entered Yes
Expired Order Order The system Created by a database job that queries for orders that expiration date has passed. If query finds an order for which the expiration date has passed and the status of the order is neither Canceled nor D/C, then the task is created. In creating the task, the order status is changed to Canceled or Discontinued with a Reason of Expired Process Order Ordering provider Yes
Overdue Order Order The system Created by a database job which queries for all orders whose overdue date has passed. If query finds an order for which the overdue date has passed and the status of the order is neither Canceled nor D/C, then the task is created Process Order Ordering provider The task is automatically completed when the user either (1) Edits the order due date to a future date, or (2) changes the status of the Order to Completed, D/C, Canceled, or EIE. Yes
Verify Order Order Created when a Clinical Exchange document is imported and the Clinical Exchange Document Item Verification is Y and the Clinical exchange document has at least one non-medication order or result. Order Notification When all the patient's unverified non-medication orders have been either verified and added or removed No
Order Info-Additional Info Order The system When the order is saved with additional information question that are defined as “missing” answer results in Needs Info status or missing answer results in On Hold status and are unanswered Order Additional Information Ordering provider When the additional information questions have been answered No
ABN Order Follow-up Order The system System generated if an order fails medical necessity checking and an ABN disposition is not selected for the order and the system preference \'Hold Orders for ABN \' = No. This task is inactive, but still supported for use in Enterprise EHR. To use this task, set it to Active ABN Follow-Up Ordering provider Automatically completed if the order is edited to pass medical necessity checking No
Order Notification Order/Rx+ The system The intent of this task is to notify an authorizing provider that an order has been entered in the system by another user that requires their authorization. The authorizing provider does not need to review and approve the unauthorized order(s) associated with the task for the order(s) to be activated. This task is applicable to medication and non-medication orders Notify Order Supervising Provider for non-medication and ordering provider for medications When the order is authorized by a user with sufficient authority No
Authorize Order Order/Rx+ The system The intent of this task is to notify an authorizing provider that an order has been entered in the system by another user that requires their authorization. The authorizing provider must review and approve the unauthorized order(s) associated with the task for the order(s) to be activated. This task is applicable to medication and non-medication orders. Authorize Order Supervising Provider for non-medication and ordering provider for medications When the order is authorized by a user with sufficient authority No
Order New Int Order The system The order interface authorize mode flag has been set to create a task when a new order is received Miscellaneous Ordering provider Manually when the order is created or determined to not be needed No
Order Charge Int Order The system The order interface authorize mode flag has been set to create a task when an edited order is received Process Order Ordering provider When the user clicks Done No
Audit Order Int Order The system The order interface authorize mode flag has been set to post audit information when a new or edited order is received Process Order Ordering provider The user acts upon the order No
Auth Order Int Order The system The order interface creates it based on if the authorize mode flag is set to require authorization when a new or edited order is received in Allscripts Enterprise EHR Authorize Order Ordering provider Automatically when the order is authorized or the status is changed to Discontinued, Void, or Entered in Error No
Print Requisition Order The system The ordering provider has the following Auto Print preference selected: Create Print Requisition Task on Order. A user edits the order such that it enters a state that satisfies the print criteria Print Requisition Ordering provider This task is automatically completed when the requisition is printed Yes
Denied Financial Authorization Order The system The system creates this task automatically when the Financial Auth Status changes to Denied Authorization Ordering provider The task is automatically completed when the Order Status is set to Active (activate the order) or set to Void (void the order) Yes
Immunization Admin Order The system The system creates this task for the “Rx by” provider when a prescription is written with an action of Administer and any of the following fields on the Administration tab on the Medication Detail are blank: Dose, Route, Site, Admin by and Admin date Administer Immunization Ordering Provider This task is completed automatically by the system when the requirements for documenting the administration of a medication have been satisfied. The required documentation consists of the following fields on the Administration tab on the Medication Detail: Dose, Route, Site, Admin by and Admin date Yes
Immunization Documentation Order The system The system creates this task when all of the immunization required fields needed to send an immunization to a registry have not been completed Document Immunization Ordering Provider This task is completed automatically by the system when the requirements for documenting the administration of an immunization have been completed. The required documentation consists of any

required fields in the Administration Details section as well as any required questions in the Clinical Questions section of the Immunization Details Record Administration tab

Yes
Financial Auth Order The system The system creates this task when the order associated with the task requires financial authorization. Financial Auth is set to Needed Authorization Ordering provider When the Financial Auth Status is changed to Approved, Denied or Approved Modified. Yes
Order Info-Problem Order The system The task is automatically generated by the system when a non-med order is created without specifying a problem. A non-med order requires an associated problem when the preference OrderProblemLinkingRequired is set to Needs Info Reason Order Information Ordering provider This task is automatically completed when a problem is associated to the order and committed to the patient record Yes
Order Info – F/up Order The system The task is automatically generated by the system when a user creates a follow-up order, but leaves one or more fields blank and the fields are required for the order to be executed and fully documented, but are not required to create the order in the system Order Information Ordering provider This task is automatically completed when the required order information is entered in the Order Detail page. Additionally, the associated task Sign Note must be completed separately Yes
Order Info-Lab Order The system The task is automatically generated by the system when a user creates a laboratory order, but leaves one or more fields blank. The fields are required for the order to be executed and fully documented, but are not required to create the order in the system Order Information Ordering provider This task is automatically completed when the required order information is entered in the Order Detail page. Additionally, the associated task Sign Note must be completed separately Yes
Order Info-Refer Order The system The task is automatically generated by the system when a user creates a referral order, but leaves one or more fields blank. The fields are required for the order to be executed and fully documented, but are not required to create the order in the system Order Information Ordering provider This task is automatically completed when the required order information is entered in the Order Detail page Yes
Order Info-Image Order The system The task is automatically generated by the system when a user creates a diagnostic imaging order, but leaves one or more fields blank. The fields are required for the order to be executed and fully documented, but are not required to create the order in the system Order Information Ordering provider This task is automatically completed when the required order information is entered in the Order Detail page Yes
Obtain ABN Order Order The system The task is created when an order is saved with an ABN Disposition of null and ABN Status of Failed Medical Necessity or Failed MN-Not Holding. The client may use either Failed Medical Necessity or Failed MN-Not Holding, not both Specify Disposition Ordering provider The task is automatically completed when the user either (1) makes a change to the order such that the resulting medical necessity status is no longer Failed Medical Necessity or Failed MN-Not Holding, or (2) edits the ABN Disposition attribute on Order to a non-NULL value, or (3) changes the Order Status to D/C, Canceled, or EIE Yes
Authorized Order Order The system The task is created when an order requiring approval is activated by a supervising provider Order Notification Ordering provider Select the task, and then click Done Yes
Call Order Order The system This task is created when a Communication Method of Call Order is the chosen for the order Call Ordering provider Yes
Rejected Order Order The system This task is created when an order requiring approval is voided by a supervising provider Order Notification Ordering provider Select the task, and then click Done Yes
Dispense Order Order The system This task is created when an ordering action of Dispense is chosen for the order Dispense Ordering provider Yes
Perform Order Order The system This task is created when the order’s Communicated By box is set to Perform Order Perform Ordering provider When the status of the order is Completed or Resulted, automatically complete the task. D/C and EIE should not complete the task – those order statuses should remove the task Yes
Go to Order Order A user User will select an order, and then click New Task, and manually enter the pertinent information into the task form Process Order User specified on the Orders New Task page When the user clicks Done No
Pt Merge-Enc Patient lists The system This task is created when a patient is added to a service list Patient merge encounter Local Patient Merge Team When the local patient is merged with a valid patient in the database using Merge Patient Encounters workspace
Call Patient Communication Population Health Mgmt The system This task is generated when the patient’s preferred method of communication is Phone and the patient is on the Pursuit List for a Patient Action Set. The Patient Action Set also includes the action to generate Call Patient Communication tasks Call Delegated to a user or team Yes
Mail Patient Communication Population Health Mgmt The system This task is generated when the patient’s preferred method of communication is Mail and the patient is on the Pursuit List for a Patient Action Set. The Patient Action Set also includes the action to generate Mail Patient Communication tasks Mail Delegated to a user or team Yes
Print Label Result The system If any orders on a requisition have a label, check the auto-print defaults. If the Create Print Label Task on Order option is checked, then this task is created Print Label Ordering provider The task is automatically completed with the item is queued in the printer queue Yes This task was renamed to Print Label in v11. In previous versions, this task was Print Specimen
Go to Result Result A user In the Results workspace, select a result, click New Task, and complete the Task page Process Result User specified on the Results New Task page When the user clicks Done No
Mail Results to Patient Result The system Task is indented to facilitate the notification and printing of results that should be mailed to the patient. The system creates this task when verified results are available and the communication method for those results was specified as mail Print Document One of the following: (1) By the system when the document is printed via the task list Go To button. (2) By printing the document from the batch printing page. (3) Manually Yes
Print Results for CC Result The system The purpose of this task is generate a hardcopy of a patient’s results to be sent to another individual when the verified results become available. The task is generated when another user/provider is designated to be cc’d on the result and that preferred communication method is specified as PRINT Print Encounter Results for Distribution Ordering provider The task is complete when the item is queued in the print queue Yes
Call Patient with Results Result The system This task is intended to facilitate the notification and processing of results that should be phoned to the patient. The system creates this task when verified results are available and the communication method for those results was specified as phone. This is for V11 Notes Process Note Results Ordering Provider Yes
Error Results Verification Result The system This is a task generated by the system that detects that results were verified but a Note or patient communication does not exist. Only one task per patient and Ordering Provider match can be generated per day Misc Delegated to the Ordering Provider of the order/results that failed to generate the Note and Pt Comm task Done button
Print Result Result The system This is an ad-hoc task that is manually generated to advise a user to print a result. Select the result, click New Task, and then choose Print Results Print Result Owner of the document to be printed The task is automatically completed when the result is queued in the printer queue No
Result Invalid Result The system This task is created when a result is invalidated Process Result Ordering provider Yes
Call Pt with Result Result The system This task is indented to facilitate the notification and processing of results that should be phoned to the patient. The system creates this task when verified results are available and the communication method for those results was specified as phone. This is for V10 notes Process Note Results Ordering provider Yes
Verify Patient Results Result The system This task provides notification that a result is available for verification. The task facilitates the verification of patient results. The task is created when a result is filed that requires verification. The task priority is dictated by the Result Status Verify Patient Results Ordering provider Completed when the all results associated with the encounter and ordering provider combination have either been verified or the ordering provider for the result has been changed to another user No
Schedule Results F/Up Result The system When a result is verified with a patient communication action of Schedule appointment to discuss results System Miscellaneous Manually completed No
Print Result for Chart Result The system When a result is verified and the applicable auto-print defaults have the “create result update task when verified” or the “create result update task when received” checkbox checked Result Update Ordering provider One of the following: (1) By the system when the document is printed via the task list Go To button. (2) By printing the document from the batch printing page. (3) Manually Yes
Review Results Result The system When a user is CC’d on a result with a notification method of task, a review result is created for them when the result is verified or if it does not need verification, when it is filed Process Result Ordering provider Manually completed or completed when the user who was CC’d views the result and clicks Review No
Authorized Rx Rx+ The system Authorized Rx is a notification task informing a selected user that a prescription has been authorized. The system generates this task when the Action selected when creating the Rx is any action except Phone (which creates a Call in Rx task). The task instructs the user to follow-up with the patient, since there is a delay between the writing of the prescription and when it is conveyed to the pharmacy Med Notification The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task The task owner will review the order and click Done to complete the task Yes
Verify Rx Rx+ Created when a Clinical Exchange document is imported and the Clinical Exchange Document Item Verification is Y and the clinical exchange document has at least one medication order Med Notification When all the patient's unverified meds have been either verified and added or removed No
Medication Admin Documentation Rx+ The system The system creates this task when all the indicated required fields to for a medication administration have not been completed Document medication administration Document medication Admin The task is completed automatically by the system when the requirements for documenting the administration of an medication have been completed. The required documentation consists of any required fields in the Record Administration tab of the Medication details dialog Yes
Review Cancel Denied Rx+ The system This task will be created when the pharmacy is unable to cancel a prescription Notification Ordering provider When the user clicks Done.
Call in Rx Rx+ The system The system automatically creates this task when the prescriber selects the Action of Phone when creating a prescription Process Med Ordering provider The user may resubmit from the print queue or click Done on task list Yes
Med Admin Rx+ A user The system creates this task for the “Rx by” provider when a prescription is written with an action of Administer and any of the following boxes on the Administration tab on the Medication Detail page are blank: Dose, Route, Site, Admin By or Admin Date Administer Medication Ordering provider This task is completed automatically by the system when the requirements for documenting the administration of a medication have been satisfied. The required documentation consists of the following boxes on the Administration tab on the Medication Detail page: Dose, Route, Site, Admin by or Admin date Yes
Dispense Sample Rx+ The system The system creates this task for the “Rx by” provider when a prescription is written with an action of Dispense Sample and any of the required fields on the Record Sample tab on the Medication Detail are blank: Quantity, Lot number, Expiration date, Dispensed By or Dispensed Date Dispense Sample Ordering provider This task is completed automatically by the system when all required fields on the Record Sample tab have been populated Yes
Rx Renew Request Rx+ The system The system creates this task for the “Rx by” provider when a REFREQ message is received from a SCRIPT standard enabled pharmacy Concerning Med The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task Selecting one of the Grant/Refuse controls automatically completes the task No
Rx Xmit Fail Rx+ The system The system creates this task when an error is returned from the CSS Spooler indicating that a SCRIPT transmission of a NEWRX or REFREQ has failed Concerning Med The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task The task owner will review the order and either remove it from the page or click Done from the task list Yes
Rx Info-Problem Rx+ The system The task is automatically generated by the system when a med order is created without specifying a problem. An Rx requires an associated problem when the preference PrescribeProblemLinkingRequired is set to Needs Info Reason Rx Info Ordering provider This task is automatically completed when a problem is associated to the order and committed to the patient record Yes
Med Renewal Rx+ A user This is a general-purpose task launched from the Medications page with a medication selected. Since the task is ad hoc, the creator must enter instructions in the Comments box that fully define the task for the recipient. For example, this task may be created by non-prescribing user who must request a renewal on behalf of a patient or provider Process Med User specified on the New Task page The task is automatically completed when the medication is renewed. If the med is not renewed, complete the task by clicking Done from the task list No
Go to Med Rx+ A user This is a general-purpose task launched from the medications page with a medication selected. Since the task is ad hoc, the creator must enter instructions in the Comments field that fully define the task for the recipient. For example, the patient may have called in with a reaction to the medication and is requesting the provider follow up with the patient regarding the med Process Med User specified on the Medications New Task page When the user clicks Done No
Rx Info-Pharm Rx+ The system This task is automatically created when generating a prescription and the destination pharmacy is incomplete or unknown. The applicable Rx actions that will generate this task are: Retail, Mail Order and Phone. All other prescribing actions shall not create this task Rx Info-Pharm Ordering provider The task is completed when pharmacy information for all med orders for the patient – provider combination is provided Yes
Rx Info-Address Rx+ The system This task is automatically created when generating a prescription for a mail order pharmacy and the patient’s mailing address is incomplete or unknown Rx Info-Address Ordering provider When the user clicks Done Yes
Rx Info-PBM Rx+ The system This task is automatically created when generating a prescription that is missing specific benefit information required by the destination pharmacy. The pharmacies and the information required by these pharmacies is defined in the database table, PHARM_REQ_FLDS Rx Info-PBM Ordering provider The task is completed when all required Rx benefit fields for the patient are updated Yes
Authorize Non-Formulary Medication Rx+ The system This task is created when a non-formulary medication has been prescribed and the Med preference PrescribeNonFormularyAuthReq = Y Authorize Medication Utilization review physician This task is completed automatically when the user takes an action on the Authorize Orders page. To authorize: Place a checkmark in the check boxes next to the medications and then click Authorize. To reject: Click Edit, select Void from the Status list, and then click Apply & Close No
Call in Failed Rx Rx+ The system This task is created when an Rx fax job fails in the print queue Call Ordering Provider When the user clicks Done No
Med Renewal Due Rx+ The system This task is created when the medication Expected Action is set to Renew and the date associated with that action occurs. It's based on the preference: DaysBeforeRxActionDateToConsiderNearDue. This preference specifies the number of days before the expected action date that the task should be created. This task is not created for Med Admin and Immunization Admin renewals Process Med Completed when the all medication renewals associated with the patient-ordering provider combination have either been renewed, the expected action trigger has changed, the medication status has changed, or the ordering provider for the medication has been changed another user. To complete the task do one of the following: (1) Update the therapy end date to a future date (the therapy remains active). (2) Renew the therapy (remains active). (3) Change the medication “expected action” (evaluate or stop). (4) Change the medication status (Complete, D/C, EIE) Yes
Med Renewal Request Rx+ The system This task is created when the medication Expected Action is set to Evaluate and the date associated with the action meets the criteria set in the Days Before Rx Action Date to Consider Near Due medication preference Process Med Ordering Provider When the user clicks Done
Rejected Rx Rx+ The system This task is created when the status of an unauthorized medication order is set to Void Med Notification The provider specified in the Rx by box will be assigned this task. It is not expected that this user will actually work the task The task owner will review the order and click Done to complete the task. Yes
Call in Cancel Rx Rx The system This task is created when an Rx cancellation cannot be sent electronically Call Ordering Provider When the user clicks Done Yes
External Medical Hx Summary Rx The system This task is created when the application receives an response from the Wellpoint MHp indicating that patient data is available Review Hx Summary Assign the task to the provider who sent the eligibility request for the patient Highlight the task from the task list and select Done
Chart Release Request The user The user specifies this task type from any workspace Mis
HIE CEDExport Fail The system This task is created when an automatic CED fails Mis HIE CEDExport Fail When the user clicks Done