https://wiki.galenhealthcare.com/api.php?action=feedcontributions&user=Troy.Forcier&feedformat=atomGalen Healthcare Solutions - Allscripts TouchWorks EHR Wiki - User contributions [en]2024-03-29T09:31:04ZUser contributionsMediaWiki 1.35.1https://wiki.galenhealthcare.com/index.php?title=Allscripts_EEHR_Servers_-_DB&diff=16271Allscripts EEHR Servers - DB2013-04-18T19:38:35Z<p>Troy.Forcier: /* Files */</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast Overview==<br />
Let Galen's expert EHR Technicians help you with: Understanding the platforms involved in implementing an Allscripts Enterprise Database Server. Studying the database server as it relates to the other Allscripts Enterprise EHR server roles. Increase knowledge of the key components of the database server role. Tackle Operational Best Practices including the use of SQL Server provided tools.<br />
<br />
==Files==<br />
Delivered 4/17/2013: [[Media:AE-EHR_Database_Server_20130417.pdf|Download slideshow]]<br />
<br />
Delivered 9/5/2012: [[Media:AE-EHR_Database_Server_Summer_2012.pdf|Download slideshow]]<br />
<br />
== Links ==</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=File:AE-EHR_Database_Server_20130417.pdf&diff=16270File:AE-EHR Database Server 20130417.pdf2013-04-18T19:38:08Z<p>Troy.Forcier: </p>
<hr />
<div></div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_EEHR_Servers_-_Scan&diff=15982Allscripts EEHR Servers - Scan2013-03-08T14:01:39Z<p>Troy.Forcier: /* Files */</p>
<hr />
<div>[[Category:Allscripts_Document_Management]][[Category:Webcasts]][[Category:Technical]]<br />
__TOC__<br />
<br />
<br />
==Webcast Overview==<br />
Let Galen's expert EHR Consultants help you with understanding the platforms involved in implementing Allscripts Enterprise Scan. Learn the Scan Server as it relates to the other Allscripts Enterprise EHR server roles. Increase knowledge of the key components of the Scan server role. Tackle Operational Best Practices including the use of Enterprise EHR Configuration tools. Learn about the Scan Warehouse, User setup and security, integration with Touchworks and stand-alone behavior.<br />
<br />
==Files==<br />
Delivered 11/11/2011: [[Media:Scan webcast 11-11-2011.pdf|Download slideshow]]<br />
<br />
Delivered 6/13/2012: [[media: Enterprise_EHR_Scan_Servers_Spring2012.pdf|Download slideshow]]<br />
<br />
Delivered 3/6/2013: [[media: EEHR_Scan_Servers_20130306.pdf|Download slideshow]]<br />
<br />
==Links==</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=File:EEHR_Scan_Servers_20130306.pdf&diff=15981File:EEHR Scan Servers 20130306.pdf2013-03-08T14:01:21Z<p>Troy.Forcier: </p>
<hr />
<div></div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_EEHR_Servers_-_Web&diff=15905Allscripts EEHR Servers - Web2013-02-07T17:32:48Z<p>Troy.Forcier: /* Files */</p>
<hr />
<div>[[Category:Webcasts]]<br />
__TOC__<br />
<br />
==Webcast Overview==<br />
Let Galen's expert EHR Consultants help you with: Understanding the platforms involved in implementing Allscripts Enterprise Web Servers. Studying the web server as it relates to the other Allscripts Enterprise EHR server roles. Increase knowledge of the key components of the web server role. Tackle Operational Best Practices including the use of Enterprise EHR Configuration tools.<br />
<br />
==Files==<br />
Delivered 4/18/2012: [[Media:AE-EHR Web Server Spring 2012.pdf|Download slideshow]]<br />
<br />
Delivered 12/12/2012: [[Media:AE-EHR_Web_Server_Fall_2012.pdf|Download slideshow]]<br />
<br />
== Links ==</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=File:AE-EHR_Web_Server_Fall_2012.pdf&diff=15904File:AE-EHR Web Server Fall 2012.pdf2013-02-07T17:32:21Z<p>Troy.Forcier: </p>
<hr />
<div></div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=How_to_check_what_version_of_medcin%3F&diff=14304How to check what version of medcin?2012-09-12T13:41:32Z<p>Troy.Forcier: </p>
<hr />
<div>'''Database:'''<br />
*Login to the database server<br />
*Open SQL Server Management Studio<br />
*Go to the Works>Database and Select New Query<br />
*Enter- select * from versionnumber<br />
*Execute Query<br />
*A table will be generated listing the Noteform release date and Medcin<br />
See example [[Media:Sample Medcin-Noteform SQL extraction.pdf|Sample Medcin SQL extraction]]<br />
<br />
'''WEB:'''<br />
<br />
Browse to:<br />
<br />
C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\TouchWorks<br />
<br />
Find the Medcin.x files, and check the date on those files.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_EEHR_Servers_-_DB&diff=14297Allscripts EEHR Servers - DB2012-09-05T20:22:28Z<p>Troy.Forcier: Created page with "==Webcast Overview== Let Galen's expert EHR Technicians help you with: Understanding the platforms involved in implementing an Allscripts Enterprise Database Server. Studying t..."</p>
<hr />
<div>==Webcast Overview==<br />
Let Galen's expert EHR Technicians help you with: Understanding the platforms involved in implementing an Allscripts Enterprise Database Server. Studying the database server as it relates to the other Allscripts Enterprise EHR server roles. Increase knowledge of the key components of the database server role. Tackle Operational Best Practices including the use of SQL Server provided tools.<br />
<br />
==Files==<br />
Delivered 9/5/2012: [[Media:AE-EHR_Database_Server_Summer_2012.pdf|Download slideshow]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=File:AE-EHR_Database_Server_Summer_2012.pdf&diff=14296File:AE-EHR Database Server Summer 2012.pdf2012-09-05T20:21:43Z<p>Troy.Forcier: </p>
<hr />
<div></div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Webcasts&diff=14295Webcasts2012-09-05T20:18:41Z<p>Troy.Forcier: </p>
<hr />
<div>'''Galen Healthcare is proud to offer a series of <span style="color:red;">Free Webcasts</span>'''<br />
{| style="background:#fcfcfc; border:1px dashed #ccc; padding:6px; width:100%;" <br />
| <br />
*'''See schedule and register at:''' [http://www.galenhealthcare.com/calendar/ Webinar Calendar]<br />
*[[Register for All or Multiple Galen Public Webcasts at One Time|Register for Multiple Galen Webcasts at One Time]]*<br />
|}<br />
''Any handouts or Q&A can be found on the following links.''<br />
----<br />
September 5, 2012 - [[Allscripts EEHR Servers - DB]] <br />
<br />
August 31, 2012 - [[Advanced End User Tips and Tricks]]<br />
<br />
August 8, 2012 - [[Analytics Access Center]]<br />
<br />
July 25, 2012 - [[Configuration and Deployment of Imagelink]]<br />
<br />
July 11, 2012 - [[Virtualization Technologies]]<br />
<br />
June 27, 2012 - [[Allscripts PM Interface Engine – Basic Setup and Monitoring]]<br />
<br />
June 22, 2012 - [[Advanced Note Build]]<br />
<br />
June 13, 2012 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
June 8, 2012 - [[Tasking Fundamentals]]<br />
<br />
May 25, 2012 - [[Organizational Considerations when Staff Terminate]]<br />
<br />
April 18, 2012 - [[Allscripts EEHR Servers - Web]]<br />
<br />
March 30, 2012 - [[Allscripts Enterprise EHR - OID Pt 2 - Advanced Order Features ]]<br />
<br />
February 22, 2012 - [[Galen Interface Solutions]]<br />
<br />
February 17, 2012 - [[Allscripts Enterprise EHR - OID Pt 1 - Basics of the OID]]<br />
<br />
February 3, 2012 - [[SSMT- CMT]]<br />
<br />
January 25, 2012 - ConnectR - Advanced Troubleshooting<br />
<br />
January 20, 2012 - [[Group to Specialty Mapping]] <br />
<br />
January 12, 2012 - [[VitalCenter Overview & Demo]] <br />
<br />
January 6, 2012 - Top 5 Workflow Challenges Resolved <br />
<br />
December 14, 2011 - [[Allscripts EEHR Servers - Message]] <br />
<br />
December 9, 2011 - [[Health Management Plan]] <br />
<br />
November 30, 2011 - [[ConnectR - Advanced Design]] <br />
<br />
November 16, 2011 -[[Reporting - Minimizing the Requisition]] <br />
<br />
November 11, 2011 - [[Charge Webcast]] <br />
<br />
November 2, 2011 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
October 28, 2011 - Basic Note Build - V11.2 <br />
<br />
October 14,2011 - [[MU Selection and Configuration of Measures]] <br />
<br />
May 2011 - [[CareGuide Webcast]]<br />
<br />
April 1, 2011 -[[Enterprise EHR Tasking]] <br />
<br />
March 18, 2011 - [[Allscripts Enterprise EHR - Order Synchronization]] <br />
<br />
March 04,2011 - [[ePrescribing/Surescripts RxHub]] <br />
<br />
February 18, 2011 - [[Allscripts Enterprise EHR - Advanced OID SSMT]] <br />
<br />
January 18, 2011 - [[Allscripts Enterprise EHR - OID SSMT Fundamentals]] <br />
<br />
November 17, 2010 - [[Reports - Analytics]] <br />
<br />
November 03, 2010 - [[Interfaces - Advanced Design]] <br />
<br />
October 20, 2010 - [[Reports - Order and Results]] <br />
<br />
October 06, 2010 - [[Tech - System Maintenance]] <br />
<br />
September 24, 2010 - [[Allscripts Enterprise EHR - Orders]] <br />
<br />
September 22, 2010 - [[Interfaces - Troubleshooting]] <br />
<br />
September 10, 2010 - [[Allscripts Enterprise EHR - Advanced Notes]] <br />
<br />
September 08, 2010 - [[Reports - Patient]] <br />
<br />
August 27, 2010 - [[Allscripts Enterprise EHR - Building Orders (Basics)]] <br />
<br />
August 25, 2010 - [[Interfaces - Imagelink]] <br />
<br />
August 13, 2010 - [[Allscripts Enterprise EHR - Building Notes (Basics)]] <br />
<br />
August 11, 2010 - [[Allscripts Analytics]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Encounters_per_Year&diff=14294Encounters per Year2012-09-05T20:06:59Z<p>Troy.Forcier: Created page with "Finding the number of annual encounters involves running the following query against the Works DB in SQL: <source lang=TSQL> select count( * ) from encounter where DATEDIFF(day,..."</p>
<hr />
<div>Finding the number of annual encounters involves running the following query against the Works DB in SQL:<br />
<br />
<source lang=TSQL><br />
select count( * ) from encounter where DATEDIFF(day,encounter.dttm, GETDATE()) < 365<br />
</source></div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=SQL_queries&diff=14293SQL queries2012-09-05T20:01:16Z<p>Troy.Forcier: </p>
<hr />
<div>[[Image:Fix_all_users_and_logins_on_SQL_instance.sql]]<br />
<br />
[[Image:Example_SQL_File.sql]]<br />
<br />
[[Encounters per Year]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Webcasts&diff=13886Webcasts2012-06-18T19:58:43Z<p>Troy.Forcier: </p>
<hr />
<div>Galen Healthcare is proud to offer a series of '''Free Webcasts'''. Any handouts or Q&A can be found on the following links.<br />
<br />
June 22, 2012 - [[Advanced Note Build]]<br />
<br />
June 13, 2012 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
May 25, 2012 - [[Organizational Considerations when Staff Terminate]]<br />
<br />
April 18, 2012 - [[Allscripts EEHR Servers - Web]]<br />
<br />
March 30, 2012 - [[Allscripts Enterprise EHR - OID Pt 2 - Advanced Order Features ]]<br />
<br />
February 22, 2012 - [[Galen Interface Solutions]]<br />
<br />
February 17, 2012 - [[Allscripts Enterprise EHR - OID Pt 1 - Basics of the OID]]<br />
<br />
February 3, 2012 - [[SSMT- CMT]]<br />
<br />
January 25, 2012 - ConnectR - Advanced Troubleshooting<br />
<br />
January 20, 2012 - [[Group to Specialty Mapping]] <br />
<br />
January 12, 2012 - [[VitalCenter Overview & Demo]] <br />
<br />
January 6, 2012 - Top 5 Workflow Challenges Resolved <br />
<br />
December 14, 2011 - [[Allscripts EEHR Servers - Message]] <br />
<br />
December 9, 2011 - [[Health Management Plan]] <br />
<br />
November 30, 2011 - [[ConnectR - Advanced Design]] <br />
<br />
November 16, 2011 -[[Reporting - Minimizing the Requisition]] <br />
<br />
November 11, 2011 - [[Charge Webcast]] <br />
<br />
November 2, 2011 - [[Allscripts EEHR Servers - Scan]] <br />
<br />
October 28, 2011 - Basic Note Build - V11.2 <br />
<br />
October 14,2011 - [[MU Selection and Configuration of Measures]] <br />
<br />
April 1, 2011 -[[Enterprise EHR Tasking]] <br />
<br />
March 18, 2011 - [[Allscripts Enterprise EHR - Order Synchronization]] <br />
<br />
March 04,2011 - [[ePrescribing/Surescripts RxHub]] <br />
<br />
February 18, 2011 - [[Allscripts Enterprise EHR - Advanced OID SSMT]] <br />
<br />
January 18, 2011 - [[Allscripts Enterprise EHR - OID SSMT Fundamentals]] <br />
<br />
November 17, 2010 - [[Reports - Analytics]] <br />
<br />
November 03, 2010 - [[Interfaces - Advanced Design]] <br />
<br />
October 20, 2010 - [[Reports - Order and Results]] <br />
<br />
October 06, 2010 - [[Tech - System Maintenance]] <br />
<br />
September 24, 2010 - [[Allscripts Enterprise EHR - Orders]] <br />
<br />
September 22, 2010 - [[Interfaces - Troubleshooting]] <br />
<br />
September 10, 2010 - [[Allscripts Enterprise EHR - Advanced Notes]] <br />
<br />
September 08, 2010 - [[Reports - Patient]] <br />
<br />
August 27, 2010 - [[Allscripts Enterprise EHR - Building Orders (Basics)]] <br />
<br />
August 25, 2010 - [[Interfaces - Imagelink]] <br />
<br />
August 13, 2010 - [[Allscripts Enterprise EHR - Building Notes (Basics)]] <br />
<br />
August 11, 2010 - [[Allscripts Analytics]] <br />
<br />
<br />
'''See schedule and register at:'''<br />
[http://www.galenhealthcare.com/calendar/ Webinar Calendar]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_EEHR_Servers_-_Scan&diff=13885Allscripts EEHR Servers - Scan2012-06-18T19:54:49Z<p>Troy.Forcier: /* Files */</p>
<hr />
<div>==Webcast Overview==<br />
Let Galen's expert EHR Consultants help you with understanding the platforms involved in implementing Allscripts Enterprise Scan. Learn the Scan Server as it relates to the other Allscripts Enterprise EHR server roles. Increase knowledge of the key components of the Scan server role. Tackle Operational Best Practices including the use of Enterprise EHR Configuration tools. Learn about the Scan Warehouse, User setup and security, integration with Touchworks and stand-alone behavior.<br />
<br />
==Files==<br />
Delivered 11/11/2011: [[Media:Scan webcast 11-11-2011.pdf|Download slideshow]]<br />
<br />
Delivered 6/13/2012: [[media: Enterprise_EHR_Scan_Servers_Spring2012.pdf|Download slideshow]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=File:Enterprise_EHR_Scan_Servers_Spring2012.pdf&diff=13884File:Enterprise EHR Scan Servers Spring2012.pdf2012-06-18T19:53:33Z<p>Troy.Forcier: </p>
<hr />
<div></div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Adding_a_Printer_to_the_Allscripts_Enterprise_Print_Server&diff=13629Adding a Printer to the Allscripts Enterprise Print Server2012-05-15T15:12:46Z<p>Troy.Forcier: /* Synching the Print Driver with the Database */</p>
<hr />
<div>__TOC__<br />
<br />
== Define the Printer on the [[TouchWorks]] Print Server (Manual) ==<br />
<br />
# Log on to the TouchWorks Print Server<br />
# Select Start/Printers and Faxes<br />
# Select “Add a Printer”<br />
#: [[Image:Jdb_1.JPG]]<br />
# Select [Next]<br />
#: [[Image:Jdb_2.JPG]]<br />
# Select “Local printer”<br />
# Uncheck the Plug and Play option if it is checked<br />
# Select [Next]<br />
#: [[Image:Jdb_3.JPG]]<br />
# Select Create a new port<br />
# Choose the type of “Standard TCP/IP Port” in the drop down<br />
# Select [Next]<br />
#: [[Image:Jdb_4.JPG]]<br />
# When the above screen appears Select [Next]<br />
#: [[Image:Jdb_5.JPG]]<br />
# Enter the IP address (The Port Name will automatically be filled out)<br />
# Select [Next]<br />
#: [[Image:Jdb_6.JPG]]<br />
# When the screen above appears, Select [Finish]<br />
#: [[Image:Jdb_7.JPG]]<br />
# When the above screen appears, select the proper printer from the list. If it is not there, you may need to install the print driver on the server and the select the “Have Disk” option to load the driver.<br />
# Once the appropriate printer is highlighted Select [Next]<br />
#: [[Image:Jdb_8.JPG]]<br />
# Choose “Keep the existing driver”, unless you have a reason not to<br />
# Select [Next]<br />
#: [[Image:Jdb_9.JPG]]<br />
#Enter a descriptive printer name (This will be the name that appears in TouchWorks)<br />
# Choose “No” for the use as default option, unless that is necessary<br />
# Select [Next]<br />
#: [[Image:Jdb_10.JPG]]<br />
# Select the “Share as:” option<br />
# Enter the exact same name as you entered on the previous screen<br />
# Select [Next]<br />
#: [[Image:Jdb_11.JPG]]<br />
# Enter a descriptive location and comment<br />
# Select [Next]<br />
#: [[Image:Jdb_12.JPG]]<br />
# Choose [No]<br />
# Select [Next]<br />
#: [[Image:Jdb_13.JPG]]<br />
# Select [Finish]<br />
# Repeat process for each printer that needs to be defined<br />
<br />
== Define the Printer on the [[TouchWorks Print Server]] (using Print Migrator) ==<br />
# Visit [http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx Microsoft.com]<br />
# Search for the term 'Print Migrator' -- Current version (as of 01/30/2008): 3.1<br />
# Download and save executable<br />
# Run executable on source server, and select Actions >> Backup on main menu<br />
# Select a destination folder and name your file. ''The application looks like it wants to Open a file, but just assume a Save-as''<br />
# Copy both the Print Migrator executable file as well as the Backup file that you just created (*.cab) to the target server.<br />
# Run executable on target server, and select Actions >> Restore on main menu<br />
# Select the Backup file (*.cab) and hit OK.<br />
# Confirm migration success by going to Control Panel >> Printers & Fax. You should see a list of all servers from the source server on the target server.<br />
<br />
== Activating Printer in TouchWorks ==<br />
<br />
# Log into TouchWorks as a user that has access to TWAdmin Workspace<br />
# Navigate to the Printing/Print Servers menu item<br />
#: [[Image:Jdb_13.JPG]] <br />
# Highlight the print server definition that you need to activate printers for<br />
# Select [Edit]<br />
#: [[Image:Jdb_14.JPG]]<br />
# Find the newly added printer in the list<br />
# Choose the “Active” option next to the name<br />
# Select [OK]<br />
# This will activate the printer in the TouchWorks product<br />
#: [[Image:Jdb_15.JPG]]<br />
<br />
== Synching the Print Driver with the Database ==<br />
<br />
# Log onto the TouchWorks Print Server<br />
# Using File Explorer navigate to the following directory: C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\TouchworksPrint Center<br />
# Find the following executable: CSSPrinterTrays.exe<br />
# Double-click the executable<br />
#: [[Image:Jdb_16.JPG]]<br />
# Enter your Web Server name and select SSL if using that option<br />
# Ensure that the AppGroup is set to “TouchWorks”<br />
# Select [Connect]<br />
#: [[Image:Jdb_17.JPG]]<br />
# The Print Servers List should populate<br />
# Highlight the Print Server that you would like modify<br />
# Select [Edit]<br />
#: [[Image:Jdb_18.JPG]]<br />
# Navigate to the printer that you would like to synch to the database<br />
# Highlight the printer<br />
#: [[Image:Jdb_19.JPG]]<br />
# When highlighted, the product should show the tray information reported from the driver on the right hand side. If the information displayed in the database is missing or different Select [Synch]<br />
#: [[Image:Jdb_20.JPG]]<br />
# When done, both sides should report the same information<br />
# Repeat this process for each printer you are installing<br />
# Select [Close]<br />
# Select [Cancel] to close out of the application</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=User_print_defaults&diff=13552User print defaults2012-05-02T12:55:26Z<p>Troy.Forcier: </p>
<hr />
<div>In order for end users to be able to modify their print defaults, you have to give each user access to a new document on one of their menus. Here is the workflow:<br />
<br />
#From the '''Admin''' workplace, choose '''Users''' in the vertical toolbar<br />
#Search for the appropriate '''username'''<br />
#When the search results appear, click the link for the '''username''' in the ''Username'' column<br />
#When the User Summary window appears, scroll to the bottom of the window, and click the link in the '''WorkPlace''' Menu column<br />
#When the Menu Summary window appears, click the link in the Key column under 'Menu Items' that you are going to use for adding the '''User Print Defaults''' menu item<br />
#Another Menu Summary window will appear<br />
#Click '''Edit''' in the upper-right corner<br />
#When the Edit Menu window appears, click the '''Edit Menu Items''' button in the upper-right corner<br />
#Another Menu Items window will appear<br />
#Click the '''Insert''' button for where you want to insert the menu item for ''User Print Defaults''<br />
#When the blank line appears for the new entry, change the value in the Type column from '''HTB''' to '''Document'''<br />
#Click the '''ellipses''' button in the corresponding ''Key'' field<br />
#When the Select Document window appears, enter "UserPrintDefaults" (without the quotes) in the ID: field, and click the '''Search''' button<br />
#When the ''UserPrintDefaults'' row appears at the bottom of the window, click the '''UserPrintDefaults''' link in the ID column<br />
#When the Menu Items window reappears, click '''Save''' in the upper-right corner<br />
#Keep clicking '''Save''' on the windows as needed as you back out of the menu item setup<br />
#The user that you used for modifying the menu items should now have a menu item called '''User Print Defaults''' in the vertical toolbar<br />
<br />
'''Fixing a suppressed Dialog'''<br />
<br />
You can use the '''User Print Defaults''' menu item to access the particular print area that is currently suppressing the Print Dialog window. When you have identified the print area, click the corresponding line, and then click the '''Details''' button at the bottom of the window as to access the User Print Defaults window, and subsequently un-check the checkbox for '''Suppress print dialog'''.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=User_print_defaults&diff=13551User print defaults2012-05-02T12:53:19Z<p>Troy.Forcier: </p>
<hr />
<div>In order for end users to be able to modify their print defaults, you have to give each user access to a new document on one of their menus. Here is the workflow:<br />
<br />
#From the '''Admin''' workplace, choose '''Users''' in the vertical toolbar<br />
#Search for the appropriate '''username'''<br />
#When the search results appear, click the link for the '''username''' in the ''Username'' column<br />
#When the User Summary window appears, scroll to the bottom of the window, and click the link in the '''WorkPlace''' Menu column<br />
#When the Menu Summary window appears, click the link in the Key column under 'Menu Items' that you are going to use for adding the '''User Print Defaults''' menu item<br />
#Another Menu Summary window will appear<br />
#Click Edit in the upper-right corner<br />
#When the Edit Menu window appears, click the '''Edit Menu Items''' button in the upper-right corner<br />
#Another Menu Items window will appear<br />
#Click the Insert button for where you want to insert the menu item for '''User Print Defaults'''<br />
#When the blank line appears for the new entry, change the value in the Type column from '''HTB''' to '''Document'''<br />
#Click the ellipses button in the corresponding Key field<br />
#When the Select Document window appears, enter "UserPrintDefaults" (without the quotes) in the ID: field, and click the Search button<br />
#When the '''UserPrintDefaults''' row appears at the bottom of the window, click the '''UserPrintDefaults''' link in the ID column<br />
#When the Menu Items window reappears, click '''Save''' in the upper-right corner<br />
#Keep clicking '''Save''' on the windows as needed as you back out of the menu item setup<br />
#The user that you used for modifying the menu items should now have a menu item called '''User Print Defaults''' in the vertical toolbar<br />
<br />
'''Fixing a suppressed Dialog'''<br />
<br />
You can use the '''User Print Defaults''' menu item to access the particular print area that is currently suppressing the Print Dialog window. When you have identified the print area, click the corresponding line, and then click the '''Details''' button at the bottom of the window as to access the User Print Defaults window, and subsequently un-check the checkbox for '''Suppress print dialog'''.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=User_print_defaults&diff=13550User print defaults2012-05-02T12:50:44Z<p>Troy.Forcier: Created page with "I order for end users to be able to modify their print defaults, you have to give each user access to a new document on one of their menus. Here is the workflow: #From the '''A..."</p>
<hr />
<div>I order for end users to be able to modify their print defaults, you have to give each user access to a new document on one of their menus. Here is the workflow:<br />
<br />
#From the '''Admin''' workplace, choose '''Users''' in the vertical toolbar<br />
#Search for the appropriate '''username'''<br />
#When the search results appear, click the link for the '''username''' in the ''Username'' column<br />
#When the User Summary window appears, scroll to the bottom of the window, and click the link in the '''WorkPlace''' Menu column<br />
#When the Menu Summary window appears, click the link in the Key column under 'Menu Items' that you are going to use for adding the '''User Print Defaults''' menu item<br />
#Another Menu Summary window will appear<br />
#Click Edit in the upper-right corner<br />
#When the Edit Menu window appears, click the '''Edit Menu Items''' button in the upper-right corner<br />
#Another Menu Items window will appear<br />
#Click the Insert button for where you want to insert the menu item for '''User Print Defaults'''<br />
#When the blank line appears for the new entry, change the value in the Type column from '''HTB''' to '''Document'''<br />
#Click the ellipses button in the corresponding Key field<br />
#When the Select Document window appears, enter "UserPrintDefaults" (without the quotes) in the ID: field, and click the Search button<br />
#When the '''UserPrintDefaults''' row appears at the bottom of the window, click the '''UserPrintDefaults''' link in the ID column<br />
#When the Menu Items window reappears, click '''Save''' in the upper-right corner<br />
#Keep clicking '''Save''' on the windows as needed as you back out of the menu item setup<br />
#The user that you used for modifying the menu items should now have a menu item called '''User Print Defaults''' in the vertical toolbar<br />
<br />
'''Fixing a suppressed Dialog'''<br />
<br />
You can use the '''User Print Defaults''' menu item to access the particular print area that is currently suppressing the Print Dialog window. When you have identified the print area, click the corresponding line, and then click the '''Details''' button at the bottom of the window as to access the User Print Defaults window, and subsequently un-check the checkbox for '''Suppress print dialog'''.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=13274Acronyms, Abbreviations & Other Definitions2012-03-28T13:18:51Z<p>Troy.Forcier: /* F */</p>
<hr />
<div>__TOC__<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
<br />
*[http://wiki.galenhealthcare.com/Add_Clinical_Item ACI] - Add Clinical Item<br />
<br />
*ACOG - American Congress of Obstetricians and Gynecologists<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - Allscripts Enterprise EHR<br />
<br />
*AHIMA - American Health Information Management Association<br />
<br />
*AHSVOE - AHS Virtual Object Engine (see [[AHSVOEService]])<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
*AOE - Additional Order Entry<br />
<br />
*[http://www.recovery.gov/Pages/default.aspx ARRA] - American Recovery and Reinvestment Act of 2009<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*[[CCI]]- Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*[http://wiki.galenhealthcare.com/Clinical_Desktop CDT] - Clinical Desktop<br />
<br />
*[[CDA]] - Clinical Document Architecture<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*[http://wiki.galenhealthcare.com/Content_Management_Tool_(CMT) CMT] - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*CPOE - Computerized Physician Order Entry, industry term. The electronic entry by a physician of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
[[#top|Top]]<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Providers<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FQDN – Fully Qualified Domain Name, computer/networking term. Used to describe the combination of a device's host-name and domain name (ex. AHSWEB.Example.com).<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===G===<br />
*GUI - Graphic User Interface<br />
<br />
[[#top|Top]]<br />
===H===<br />
*[[HCC]] - Hierarchical Condition Categories<br />
<br />
*[[HCPCS]]- Healthcare procedural coding system.<br />
<br />
*HEDIS - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] Health Information Exchange<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*[[HIT]]- Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information ususally contained in a patients chart on a computer, rather than on paper <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*[[HTB]] – Horizontal Tool Bar the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
<br />
===I===<br />
*ICD-9 - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2013.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] Integrating the Healthcare Enterprise<br />
<br />
*IPA - Independent Practice Association-consists of a network of physicians in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the physicians in the IPA.<br />
<br />
*ISO - International Organization for Standarization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KIL – Known Issues List - furnished by Allscripts and is a comprehensive list of issues that are know to occur as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]]-National Drug Code<br />
<br />
*NPI - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*[http://wiki.galenhealthcare.com/Order_Concept_Dictionary OCD] – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*[[OID]] – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*[[PAT]] – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCMH- Patient Centered Medical Home- NCQA's program for improving primary care<br />
<br />
*PCP- Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*PMH - Past Medical History<br />
<br />
*[[PMS]] - Practice Management System <br />
<br />
*[[PQRI]]- Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*PSH - Past Surgical History<br />
<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List - furnished by Allscripts and is a comprehensive list of issues that are resolved as a result of upgrading to a newer version of Enterprise EHR.<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*[[Requested Performing Location|RPL]] - Requested Performing Location<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - Software Environment Specification<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SQL - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*[[SSMT]] – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN –Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=V11_Web_Controls&diff=12615V11 Web Controls2012-02-03T15:23:06Z<p>Troy.Forcier: /* Pre-installation of Prerequisite Software */</p>
<hr />
<div>==Allscripts Enterprise EHR v11 Web Controls==<br />
===Basics of Web Control Installation===<br />
<br />
'''Ensure previous versions of the TW Web Controls have been removed (via Control Panel BEFORE installing new ones)!'''<br />
<br />
*'''Proper installation order:'''<br />
<br />
'''V11.1.X'''<br />
#Confirm Windows Installer 3.1 is installed (necessary for .Net install) <br />
#Microsoft .Net 2.0 SP1<br />
#Trust.bat <br />
#Visual C++ 2005 Redistributable SP1<br />
#TouchWorksWebControls.msi<br />
#IDXWebFrameworkControls.msi<br />
<br />
'''V11.2.X'''<br />
#Confirm Windows installer 3.1 is installed (necessary for .net install) <br />
#Microsoft .Net 2.0 SP2 and Microsoft .Net 3.5 SP1<br />
#Trust.bat <br />
#Visual C++ 2005 SP1 and C++ 2008<br />
#TouchWorksWebControls.msi<br />
#IDXWebFrameworkControls.msi<br />
<br />
===Troubleshooting:===<br />
Verify that each of the above is installed. If a prerequisite is not installed, uninstall all other software found after that on the list. Then start the process again from that item.<br />
<br />
===Troubleshooting Windows Vista .Net Errors:===<br />
*Vista can present some unique issues in granting "Full Trust" to .Net 2.0 for trusted sites. Here are some steps that have helped clients-<br />
#Login as an Admin<br />
#Verify correct IE settings- [http://wiki.galenhealthcare.com/Suggested_IE_Settings_-_V11 Help]<br />
#Add the TW website to Trusted Sites<br />
#Turn off User Account Control in Control Panels > Users > Turn User Account Control on/off<br />
#Reboot and run "Trust.Bat"<br />
<br />
===Pre-installation of Prerequisite Software===<br />
In an upgrade project Windows Installer 3.1, .Net, Trust.bat, and Visual C++ Redistributable(s) can all be run on live end users machines ahead of your go-live.<br />
<br />
===Push Technology Recommendations===<br />
It is recommended that any push of the Touchworks Web Controls include a step to uninstall the previous version of these controls.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=V11_Web_Controls&diff=12614V11 Web Controls2012-02-03T15:19:07Z<p>Troy.Forcier: /* Basics of Web Control Installation */</p>
<hr />
<div>==Allscripts Enterprise EHR v11 Web Controls==<br />
===Basics of Web Control Installation===<br />
<br />
'''Ensure previous versions of the TW Web Controls have been removed (via Control Panel BEFORE installing new ones)!'''<br />
<br />
*'''Proper installation order:'''<br />
<br />
'''V11.1.X'''<br />
#Confirm Windows Installer 3.1 is installed (necessary for .Net install) <br />
#Microsoft .Net 2.0 SP1<br />
#Trust.bat <br />
#Visual C++ 2005 Redistributable SP1<br />
#TouchWorksWebControls.msi<br />
#IDXWebFrameworkControls.msi<br />
<br />
'''V11.2.X'''<br />
#Confirm Windows installer 3.1 is installed (necessary for .net install) <br />
#Microsoft .Net 2.0 SP2 and Microsoft .Net 3.5 SP1<br />
#Trust.bat <br />
#Visual C++ 2005 SP1 and C++ 2008<br />
#TouchWorksWebControls.msi<br />
#IDXWebFrameworkControls.msi<br />
<br />
===Troubleshooting:===<br />
Verify that each of the above is installed. If a prerequisite is not installed, uninstall all other software found after that on the list. Then start the process again from that item.<br />
<br />
===Troubleshooting Windows Vista .Net Errors:===<br />
*Vista can present some unique issues in granting "Full Trust" to .Net 2.0 for trusted sites. Here are some steps that have helped clients-<br />
#Login as an Admin<br />
#Verify correct IE settings- [http://wiki.galenhealthcare.com/Suggested_IE_Settings_-_V11 Help]<br />
#Add the TW website to Trusted Sites<br />
#Turn off User Account Control in Control Panels > Users > Turn User Account Control on/off<br />
#Reboot and run "Trust.Bat"<br />
<br />
===Pre-installation of Prerequisite Software===<br />
In an upgrade environment Windows Installer 3.1, .Net 2.0, Trust.bat, and Visual C++ 2005 Redistributable can all be run ahead of your go-live.<br />
<br />
===Push Technology Recommendations===<br />
It is recommended that any push of the Touchworks Web Controls include a step to uninstall the previous version of these controls.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=How_to_check_what_version_of_medcin%3F&diff=12040How to check what version of medcin?2011-11-10T16:24:37Z<p>Troy.Forcier: </p>
<hr />
<div>=How to check what version of medcin?=<br />
'''Database:'''<br />
*Login to the database server<br />
*Open SQL Server Management Studio<br />
*Go to the Works>Database and Select New Query<br />
*Enter- select * from versionnumber<br />
*Execute Query<br />
*A table will be generated listing the Noteform release date and Medcin<br />
See example [[Media:Sample Medcin-Noteform SQL extraction.pdf|Sample Medcin SQL extraction]]<br />
<br />
'''WEB:'''<br />
<br />
Browse to:<br />
<br />
C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\TouchWorks<br />
<br />
Find the Medcin.x files, and check the date on those files.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=How_to_check_what_version_of_medcin%3F&diff=12039How to check what version of medcin?2011-11-10T16:14:46Z<p>Troy.Forcier: </p>
<hr />
<div>=How to check what version of medcin?=<br />
'''Database'''<br />
*Login to the database server<br />
*Open SQL Server Management Studio<br />
*Go to the Works>Database and Select New Query<br />
*Enter- select * from versionnumber<br />
*Execute Query<br />
*A table will be generated listing the Noteform release date and Medcin<br />
See example [[Media:Sample Medcin-Noteform SQL extraction.pdf|Sample Medcin SQL extraction]]<br />
<br />
'''WEB'''<br />
<br />
Browse to:<br />
<br />
C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\TouchWorks<br />
<br />
Find the Medcin.x files, and check the date on those files.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=How_to_check_what_version_of_medcin%3F&diff=12038How to check what version of medcin?2011-11-10T16:12:25Z<p>Troy.Forcier: </p>
<hr />
<div>=How to check what version of medcin?=<br />
'''Database'''<br />
*Login to the database server<br />
*Open SQL Server Management Studio<br />
*Go to the Works>Database and Select New Query<br />
*Enter- select * from versionnumber<br />
*Execute Query<br />
*A table will be generated listing the Noteform release date and Medcin<br />
See example [[Media:Sample Medcin-Noteform SQL extraction.pdf|Sample Medcin SQL extraction]]<br />
<br />
'''WEB'''<br />
Browse to:<br />
<br />
C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\TouchWorks<br />
<br />
Find the Medcin.x files, and check the date on those files.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=V11_Web_Controls&diff=11194V11 Web Controls2011-05-17T15:24:29Z<p>Troy.Forcier: /* Basics of Web Control Installation */</p>
<hr />
<div>==Allscripts Enterprise EHR v11 Web Controls==<br />
===Basics of Web Control Installation===<br />
<br />
'''Ensure previous versions of the TW Web Controls have been removed (via Control Panel BEFORE installing new ones)!'''<br />
<br />
*'''Proper installation order:'''<br />
#Confirm Windows Installer 3.1 is installed (necessary for .Net install) <br />
#Microsoft .Net 2.0 SP1<br />
#Trust.bat <br />
#Visual C++ 2005 Redistributable SP1<br />
#TouchWorksWebControls.msi<br />
#IDXWebFrameworkControls.msi<br />
<br />
===Troubleshooting:===<br />
Verify that each of the above is installed. If a prerequisite is not installed, uninstall all other software found after that on the list. Then start the process again from that item.<br />
<br />
===Troubleshooting Windows Vista .Net Errors:===<br />
*Vista can present some unique issues in granting "Full Trust" to .Net 2.0 for trusted sites. Here are some steps that have helped clients-<br />
#Login as an Admin<br />
#Verify correct IE settings- [http://wiki.galenhealthcare.com/Suggested_IE_Settings_-_V11 Help]<br />
#Add the TW website to Trusted Sites<br />
#Turn off User Account Control in Control Panels > Users > Turn User Account Control on/off<br />
#Reboot and run "Trust.Bat"<br />
<br />
===Pre-installation of Prerequisite Software===<br />
In an upgrade environment Windows Installer 3.1, .Net 2.0, Trust.bat, and Visual C++ 2005 Redistributable can all be run ahead of your go-live.<br />
<br />
===Push Technology Recommendations===<br />
It is recommended that any push of the Touchworks Web Controls include a step to uninstall the previous version of these controls.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=11012Acronyms, Abbreviations & Other Definitions2011-04-14T13:46:55Z<p>Troy.Forcier: /* C */</p>
<hr />
<div>__TOC__<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or from the real term to a page with that information.<br />
===A===<br />
*AHIMA - American Health Information Management Association<br />
<br />
*ACI - Add Clinical Item<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - Allscripts Enterprise EHR<br />
<br />
*[[AHSVOEService]]<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BAW - Build Activity Workbook [http://wiki.galenhealthcare.com/Allscripts_Enterprise_Build_Activity_Workbook]. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
*Best Practice - Best practice is a term that refers to a process that, when used, produces optimal results.<br />
<br />
[[#top|Top]]<br />
<br />
===C===<br />
*[[CAH]] - Critical Access Hospital<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*[[CDA]] - Clinical Document Architecture<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*[[CCI]]- Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CPOE - Computerized Physician Order Entry, industry term. The electronic entry by a physician of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*CMT - Content Management Tool. This is a content management tool created by Allscripts and accessed very similarly to [[SSMT]]. Its primary function is to migrate more complex data elements and build items such as Note Forms and resultable items.<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CDT - Clinical Desktop<br />
<br />
[[#top|Top]]<br />
<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
[[#top|Top]]<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*EP - Eligible Providers<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
<br />
===F===<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
<br />
<br />
[[#top|Top]]<br />
===G===<br />
*GUI - Graphic User Interface<br />
<br />
[[#top|Top]]<br />
===H===<br />
*[[HCPCS]]- Healthcare procedural coding system.<br />
<br />
*HEDIS - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] Health Information Exchange<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*[[HIT]]- Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information ususally contained in a patients chart on a computer, rather than on paper <br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HTB]] – Horizontal Tool Bar the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
===I===<br />
*ICD-9 - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*ICD-10 - This code set is scheduled to replace ICD-9-CM, our current U.S. diagnostic code set, on Oct. 1, 2013.<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] Integrating the Healthcare Enterprise<br />
<br />
*IPA - Independent Practice Association-consists of a network of physicians in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the physicians in the IPA.<br />
<br />
*ISO - International Organization for Standarization<br />
<br />
[[#top|Top]]<br />
<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations (In 2007, formally changed their name to JC)<br />
*JC - Joint Commission <br />
<br />
[[#top|Top]]<br />
<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
*KIL – Known Issues List<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*[[LMRP]] - Local Medical Review Policy<br />
<br />
[[#top|Top]]<br />
<br />
===M===<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MU - Meaningful Use [http://wiki.galenhealthcare.com/Meaningful_Use] <br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
[[#top|Top]]<br />
<br />
===N===<br />
*NABP # - National Association of Boards of Pharmacy Number - Each licensed pharmacy in the United States is assigned a unique seven-digit number by the National Council for Prescription Drug Programs (NCPDP), in cooperation with the National Association of Boards of Pharmacy. The purpose of this system is to enable a pharmacy to identify itself to all third-party processors by one standard number.<br />
<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]]-National Drug Code<br />
<br />
*NPI - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*OCD – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*OID – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*PAT – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCP- Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*[[PMS]] - Practice Management System <br />
<br />
*[[PQRI]]- Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIL - Resolved Issues List<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*RTI - Real Time Intervention or can refer to Allscripts' now retired ticket/support management system. It is common for KB articles and documentation to contain references to the RTI ticket numbers.<br />
<br />
*RVU - Relative Value Units<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SES - Software Environment Specification<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SQL - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*SSMT – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN –Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Framework_Preferences&diff=9929Framework Preferences2011-01-13T15:24:57Z<p>Troy.Forcier: /* Preference Information */</p>
<hr />
<div>== Overview ==<br />
GE Framework preferences control both navigation within the Framework itself, as well as some Allscripts EHR functionality.<br />
<br />
<br />
== Preference Information ==<br />
* <b>EnableOrgFilterFlag</b><br />
** Name: Enable Organization Filter<br />
** Values: Y or N<br />
** Description: This applies to multi-org environments only.<br />
*** Y will prevent searching for patients or users across organizations. For example, when creating a task, you would not be able to send it to a user who is not setup in the organization that you are currently logged in to.<br />
*** N will allow you to search for patients and users across organizations. In the example above, you would be able to create tasks for users who are not in your organization. You could also search for patients by their MRNs in other organizations. Note: the patient still must exist in the current org, you'll simply be searching based on their MRN from another.<br />
*** Comments: Which organizations a user is "in" relates to their organization and security classification setup. In v11, under TWUser admin the orgs are defined for each user as you see here:<br />
****[[image:TWUserAdminSecurity.JPG]]<br />
<br />
<br />
<br />
* '''DocumentWriteOutboundEvent'''<br />
** Name: Document Write Outbound Event<br />
** Values: Y or N<br />
*** Y will create events for any documents/notes being added or updated. These events are posted to the Event_Table for [[ConnectR]] to process. An [[Outbound Document Interface]] must be setup to receive and process these events.<br />
*** N will not create the outbound document interface events.<br />
<br />
* '''ChgWorksBillingAreaReq'''<br />
** Name: CW Billing Area Required<br />
*** Indicates whether the Billing Area box is required on the Encounter Form window.<br />
** Values: Y or N<br />
*** The default value is Y.<br />
*** When this preference is set to Y, users cannot save the encounter and its associated information until they indicate a billing area.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Framework_Preferences&diff=9928Framework Preferences2011-01-13T15:24:11Z<p>Troy.Forcier: /* Preference Information */</p>
<hr />
<div>== Overview ==<br />
GE Framework preferences control both navigation within the Framework itself, as well as some Allscripts EHR functionality.<br />
<br />
<br />
== Preference Information ==<br />
* <b>EnableOrgFilterFlag</b><br />
** Name: Enable Organization Filter<br />
** Values: Y or N<br />
** Description: This applies to multi-org environments only.<br />
*** Y will prevent searching for patients or users across organizations. For example, when creating a task, you would not be able to send it to a user who is not setup in the organization that you are currently logged in to.<br />
*** N will allow you to search for patients and users across organizations. In the example above, you would be able to create tasks for users who are not in your organization. You could also search for patients by their MRNs in other organizations. Note: the patient still must exist in the current org, you'll simply be searching based on their MRN from another.<br />
*** Comments: Which organizations a user is "in" relates to their organization and security classification setup. In v11, under TWUser admin the orgs are defined for each user as you see here:<br />
****[[image:TWUserAdminSecurity.JPG]]<br />
<br />
<br />
<br />
* '''DocumentWriteOutboundEvent'''<br />
** Name: Document Write Outbound Event<br />
** Values: Y or N<br />
*** Y will create events for any documents/notes being added or updated. These events are posted to the Event_Table for [[ConnectR]] to process. An [[Outbound Document Interface]] must be setup to receive and process these events.<br />
*** N will not create the outbound document interface events.<br />
<br />
* '''ChgWorksBillingAreaReq'''<br />
** Name: CW Billing Area Required<br />
***Indicates whether the Billing Area box is required on the Encounter Form window.<br />
** Values: Y or N, the defauly value is Y.<br />
*** When this preference is set to Y, users cannot save the encounter and its associated information until they indicate a billing area.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Framework_Preferences&diff=9927Framework Preferences2011-01-13T15:23:44Z<p>Troy.Forcier: /* Preference Information */</p>
<hr />
<div>== Overview ==<br />
GE Framework preferences control both navigation within the Framework itself, as well as some Allscripts EHR functionality.<br />
<br />
<br />
== Preference Information ==<br />
* <b>EnableOrgFilterFlag</b><br />
** Name: Enable Organization Filter<br />
** Values: Y or N<br />
** Description: This applies to multi-org environments only.<br />
*** Y will prevent searching for patients or users across organizations. For example, when creating a task, you would not be able to send it to a user who is not setup in the organization that you are currently logged in to.<br />
*** N will allow you to search for patients and users across organizations. In the example above, you would be able to create tasks for users who are not in your organization. You could also search for patients by their MRNs in other organizations. Note: the patient still must exist in the current org, you'll simply be searching based on their MRN from another.<br />
*** Comments: Which organizations a user is "in" relates to their organization and security classification setup. In v11, under TWUser admin the orgs are defined for each user as you see here:<br />
****[[image:TWUserAdminSecurity.JPG]]<br />
<br />
<br />
<br />
* '''DocumentWriteOutboundEvent'''<br />
** Name: Document Write Outbound Event<br />
** Values: Y or N<br />
*** Y will create events for any documents/notes being added or updated. These events are posted to the Event_Table for [[ConnectR]] to process. An [[Outbound Document Interface]] must be setup to receive and process these events.<br />
*** N will not create the outbound document interface events.<br />
<br />
* '''ChgWorksBillingAreaReq'''<br />
** Name: CW Billing Area Required: Indicates whether the Billing Area box is required on the Encounter Form window.<br />
** Values: Y or N, the defauly value is Y.<br />
*** When this preference is set to Y, users cannot save the encounter and its associated information until they indicate a billing area.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Framework_Preferences&diff=9926Framework Preferences2011-01-13T15:23:08Z<p>Troy.Forcier: /* Preference Information */</p>
<hr />
<div>== Overview ==<br />
GE Framework preferences control both navigation within the Framework itself, as well as some Allscripts EHR functionality.<br />
<br />
<br />
== Preference Information ==<br />
* <b>EnableOrgFilterFlag</b><br />
** Name: Enable Organization Filter<br />
** Values: Y or N<br />
** Description: This applies to multi-org environments only.<br />
*** Y will prevent searching for patients or users across organizations. For example, when creating a task, you would not be able to send it to a user who is not setup in the organization that you are currently logged in to.<br />
*** N will allow you to search for patients and users across organizations. In the example above, you would be able to create tasks for users who are not in your organization. You could also search for patients by their MRNs in other organizations. Note: the patient still must exist in the current org, you'll simply be searching based on their MRN from another.<br />
*** Comments: Which organizations a user is "in" relates to their organization and security classification setup. In v11, under TWUser admin the orgs are defined for each user as you see here:<br />
****[[image:TWUserAdminSecurity.JPG]]<br />
<br />
<br />
<br />
* '''DocumentWriteOutboundEvent'''<br />
** Name: Document Write Outbound Event<br />
** Values: Y or N<br />
*** Y will create events for any documents/notes being added or updated. These events are posted to the Event_Table for [[ConnectR]] to process. An [[Outbound Document Interface]] must be setup to receive and process these events.<br />
*** N will not create the outbound document interface events.<br />
<br />
* '''ChgWorksBillingAreaReq'''<br />
** Name: CW Billing Area Required: Indicates whether the Billing Area box is required on the Encounter Form<br />
window.<br />
** Values: Y or N, the defauly value is Y.<br />
*** When this preference is set to Y, users cannot save the encounter and its associated information until they indicate a billing area.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Framework_Preferences&diff=9925Framework Preferences2011-01-13T15:22:43Z<p>Troy.Forcier: /* Preference Information */</p>
<hr />
<div>== Overview ==<br />
GE Framework preferences control both navigation within the Framework itself, as well as some Allscripts EHR functionality.<br />
<br />
<br />
== Preference Information ==<br />
* <b>EnableOrgFilterFlag</b><br />
** Name: Enable Organization Filter<br />
** Values: Y or N<br />
** Description: This applies to multi-org environments only.<br />
*** Y will prevent searching for patients or users across organizations. For example, when creating a task, you would not be able to send it to a user who is not setup in the organization that you are currently logged in to.<br />
*** N will allow you to search for patients and users across organizations. In the example above, you would be able to create tasks for users who are not in your organization. You could also search for patients by their MRNs in other organizations. Note: the patient still must exist in the current org, you'll simply be searching based on their MRN from another.<br />
*** Comments: Which organizations a user is "in" relates to their organization and security classification setup. In v11, under TWUser admin the orgs are defined for each user as you see here:<br />
****[[image:TWUserAdminSecurity.JPG]]<br />
<br />
<br />
<br />
* '''DocumentWriteOutboundEvent'''<br />
** Name: Document Write Outbound Event<br />
** Values: Y or N<br />
*** Y will create events for any documents/notes being added or updated. These events are posted to the Event_Table for [[ConnectR]] to process. An [[Outbound Document Interface]] must be setup to receive and process these events.<br />
*** N will not create the outbound document interface events.<br />
<br />
* '''ChgWorksBillingAreaReq'''<br />
** Name: CW Billing Area Required: Indicates whether the Billing Area box is required on the Encounter Form<br />
window.<br />
** Values: Y or N, the defauly value is Y.<br />
*** When this preference is set to Y, users cannot save the encounter and its<br />
associated information until they indicate a billing area.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=V11_Order_and_Result_Dictionary_Build_and_Synchronization&diff=9609V11 Order and Result Dictionary Build and Synchronization2010-11-18T13:37:46Z<p>Troy.Forcier: /* Step 1: Request the Order/Result Compendium from the various vendors */</p>
<hr />
<div>__TOC__<br />
==Description==<br />
This page is designed to walk someone through the build process for the TouchWorks v11 Order and Results dictionary build. In TouchWorks v11 you have to synchronize your orderable items with the Touchworks [[Order Concept Dictionary]] (OCD) in order for things such as care plans and AHS defined specialty favorites to work correctly with orders. If you are using multiple vendors, you also must go through the process of synchronizing the multiple vendors together. Once you have the order side complete, you can go through the process of synchronizing results to the [[Results Concept Dictionary]] (RCD). Currently this does not do anything, but future functionality will utilize this feature. <br />
<br />
==Step 1: Request the Order/Result Compendium from the various vendors==<br />
The first step is to gather the order/result compendiums from the various lab vendors. In most cases people will ask for a utilization report and only focus their effort on the top 80% of labs ordered for their locations. There are a bunch of possible orders that aren't used often or at all, so it can cut down on the effort and future maintenance if you focus your efforts. If you do use this approach, you will need to have a process for ordering labs not found in the system, which will most likely be the current paper process. When the results are returned through the interface the dictionary values may need to be entered for the results to file. There is also a dictionary loader interface that can be utilized with results interfaces. This can be requested from your AHS interface analyst. It will file missing items on the fly. This is much better than manually working one error at a time. <br />
<br />
When requesting the compendium from the vendor, be sure to ask for CPT4 and LOINC codes as well. This helps dramatically when going through the synchronization process. This will allow you to group the various vendors by CPT4 and/or LOINC and help determine which orders and results are indeed the same. It is not always one for one, but it usually narrows it quite a bit.<br />
<br />
(Supplies uses HCPCS codes. how does this fit into the paragraph above?)<br />
<br />
The compendium should also contain Additional Information Questions as well as reflex codes.<br />
<br />
==Step 2: Pick a Master Vendor==<br />
The next step is probably the easiest, pick your master vendor. In most cases a medical group has a lab that they utilize the most and that is typically the best choice. Overall you want to choose the Lab vendor that has the most codes and preferably the cleanest compendium. This vendor that you choose will be loaded as the primary lab vendor and will be the vendor that gets loaded into the [[Order Item Dictionary]] OID. It is ok if the primary vendor doesn't have every single item that your other vendors will need, but it should be more than 50% of the distinct tests.<br />
<br />
==Step 3: Build the OID dictionary for the primary vendor==<br />
To begin building the OID dictionary for TouchWorks you should begin by getting the unique list of Order codes from your primary Lab vendors compendium. This does not include any of the resultables that are tied to the Orderable, just the actual test name and it's underlying information. <br />
<br />
Once you have the unique list of Orderables, you must insert the data into the corresponding [[SSMT]] spreadsheet. For this dictionary, you want the [[SSMT]] spreadsheet named "OID - Orderable Item". To get the Headers for this spreadsheet, I would recommend extracting the spreadsheet from the TouchWorks Database using [[SSMT]] and ensuring that the "Show Headers in Extracted Data?" option is selected. There have been many times where the headers at the bottom of the screen have differed from the actual needed headers. Returning them during the extraction seems to be more reliable. <br />
<br />
For additional information concerning [[SSMT]] OID extraction see: [[OID SSMT Extraction]]<br />
<br />
If you are unfamiliar with the [[SSMT]] columns for the OID spreadsheet please refer to [[SSMT: OID - Orderable Item Dictionary]]<br />
<br />
==Step 4: Build the RID Dictionary for the primary vendor==<br />
The [[Results Item Dictionary]] (RID) is the dictionary that houses the actual dictionary items for the returned result data. These are the place holders for the numeric or text values that are returned by the vendor. For example if you order a CBC that would include resultable such as White Blood Count (WBC), Red Blood count (RBC), or Hemoglobin counts. <br />
<br />
This exercise requires you to link the resultables to the parent order for the primary results only.<br />
<br />
If you are unfamiliar with the [[SSMT]] columns for the RID spreadsheet please refer to [[SSMT: RID - Resultable Item Dictionary]]<br />
<br />
==Step 5: Link the secondary vendor to the primary==<br />
This step is the first part of the synchronization process. This will allow you to enter identical labs from multiple vendors but only presents the user with one option. For example if you are loading LabCorp and Quest Orders, they would both have a CBC. If you don't sync the Orders, the user would have two CBC's to choose from and it would be confusing. When the two have been linked, the user will simply choose the requested performing location and it would then be routed appropriately with the correct codes. The requested performing location can be defaulted in many ways in v11. You can set them based on site, insurance, or a combination of the two. This allows you to define the most likely choice, but also allows the user to change it if they have feel it needs to go elsewhere. <br />
<br />
In this exercise you need to tell the system which secondary labs are equivalent to the primary labs. Start by choosing a primary lab (whichever one best describes the lab) and map the primary lab to itself. In some cases, the primary vendor may have multiple codes for the same Orderable as well. In that case, you would treat the duplicate orderable as if it were a secondary lab also. The primary value should be the active Order code. As each secondary lab item is mapped to the the primary, inactivate the secondary. This is done in the order Performing Facility Identifiers spreadsheet. <br />
<br />
If you are unfamiliar with this spreadsheet, please refer to [[SSMT: Order Performing Facility Identifiers]]<br />
<br />
If your secondary lab has orders that do not match your primary vendors entries, you would enter that order as if it were the primary lab and complete Steps 3 and 4 for that Order.<br />
<br />
==Step 6: Link your secondary lab results to the primary==<br />
This step is optional, but recommended. This wasn't available in v10, but the advantage of synchronizing resultables for multiple vendors is that it allows the user to flow common results from multiple vendors on one line. This is a huge benefit to the providers if they want to track the trend of a results ordered from multiple places. <br />
<br />
This step is very similar to the Order synchronization process. You will fill out the Results Where Performed Identifiers spreadsheet to complete this process. <br />
<br />
If you are unfamiliar with this spreadsheet, please refer to [[SSMT: Results Where Performed Identifiers]]<br />
<br />
If your secondary vendor has items that can't be matched to the primary vendor, you should load the item into the RID dictionary by following step 4. This is a little trickier than the first pass because you may have to place the secondary labs result items under the primary labs order code. If the secondary labs order is tied to a primary lab in the Order Performing Facility Identifier spreadsheet, you must load the unlink-able secondary resultables under the primary labs order code in the RID.<br />
<br />
Let's continue the example using LabCorp as your primary and Quest as your secondary. Imagine that the LabCorp CBC included only WBC and RBC, but the Quest CBC had WBC, RBC, and MCH. You wouldn't be able to synchronize MCH because it doesn't exist in the Primary lab, but the result is under an Order Code (CBC) that is synchronized. In that case you would need to load the Quest MCH resultable code into the RID spreadsheet tied to the LabCorp CBC Order code.<br />
<br />
==Step 7: Optional - Highly recommended: Link the OID dictionary to the TouchWorks OCD Dictionary ==<br />
Once you have completed loading the OID and RID entries into the system it is time to synchronize the OID dictionary to the [[Order Concept Dictionary]] (OCD) dictionary. The main purpose of this is for users to have the ability to use [[CareGuides]]. This is for the most part a manual process that a lab expert would need to complete for the client. This is completed within TWAdmin. Please see [[OID OCD Mapping]] for further details regarding this process.<br />
<br />
==Step 8: Optional - Not Recommended: Link the RID dictionary to the TouchWorks RCD Dictionary ==<br />
Once the RID dictionary has been built you can synchronize those items to the Allscripts [[Results Concept Dictionary]] (RCD). This currently doesn't provide any benefit, although it is supposed to be beneficial in the future. I would recommend doing this if you have the time and expertise available, but it is a low priority item that can be done in the future when the functionality is there to utilize the effort. Please see [[RCD Mapping]] for further details.<br />
<br />
==Step 9: Optional - Highly Recommended: Define your Requested Performing Location Picklists ==<br />
When a user is ordering a test or any non-medication item, they have the ability to select the [[Requested Performing Location]]. This enables them to determine where the order will be sent whether it is electronic or on a printed requisition. In most cases a particular order should only have a few viable choices. For example, you wouldn't want a user to be able to select a radiology center for a laboratory test. In order to set this up properly you must use the [[SSMT]] spreadsheet named [[SSMT: OID - Order Defaults - Insurance/PatientLocation/Site]].<br />
<br />
==Step 10: Optional - Highly Recommended: Define your Communication Method Picklists ==<br />
<br />
==Step 11: Optional: Define Orderable behavior on the Site or Req Perf Loc level ==<br />
In many circumstances it is necessary for a separate [[site]] or [[Requested Performing Location]] to have differing defaults for orderable item behaviors. This is especially true if some location bill for certain procedures while others do not. This can't be set in the [[Order Item Dictionary|OID]] dictionary because it would set the behavior on a global level. In that case, you would need to use the [[SSMT: OID - Order Defaults - Req Perf Location / Site]] to define these defaults. This spreadsheet can also set patient instruction behavior, order instruction behavior, order detail behavior, hold for reason behavior, needs info behavior and overdue requirement behavior.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Electronic_Health_Record&diff=9389Electronic Health Record2010-09-23T18:24:04Z<p>Troy.Forcier: /* Examples of Electronic Health Records */</p>
<hr />
<div>An Electronic Health Record holds patients' medical and health information digitally. Also known as an EHR. An EHR can replace all or part of a patient's paper medical chart and is typically accessed via computer, PDA, or smartphone.<br />
<br />
The advantage to using an EHR over a traditional paper medical chart lies in provider decision support. Due to the digital nature of the the record, information about the patient can be organized in a way that allows immediate access to relevent information pertaining to that specific encounter. Immediate access to information provides for better decisions by the provider and therefore contributes to better outcomes. Further, decisions are supported by instant access to current information relative to the patient's condition. Whereas providers used to have to research problems via paper medical journals or the internet, EHRs grant insight into a wealth of specific information that is kept current through a constant stream of digital updates.<br />
<br />
Electronic Health Records are used, in part or in whole, for [[e-prescribing]], electronic [[charge capture]], staff [[tasking]], [[note]] creation, [[dictation]], [[transcription]] or [[transcribe]], and the storage of digitized copies of paper records ([[document imaging]]).<br />
<br />
The by product of the move to EHRs is the data. [[Regional Health Information Organization]]s ([[RHIO]]) are organizations forming with the sole intent to integrate information about a region's patient population. [[Personal Health Record]]s ([[PHR]]) are online-accessable medical charts which are controlled by the patient, rather than the provider. <br />
<br />
<br />
== Examples of Electronic Health Records ==<br />
[http://www.allscripts.com/products/electronic-health-record/allscripts-enterprise/default.asp Allscripts Enterprise EHR]<br />
<br />
[http://www.cerner.com/public/Cerner_3.asp?id=24443 Cerner PowerWorks]<br />
<br />
[http://www.allscripts.com/products/physicians-practice/ehr-solutions/healthmatics/healthmatics-ehr/default.asp Allscripts HealthMatics]<br />
<br />
[http://www.nextgen.com/pro_emr.asp NextGen EMR]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=.NET_Preferences&diff=9388.NET Preferences2010-09-23T18:17:17Z<p>Troy.Forcier: /* Meds Preferences */</p>
<hr />
<div>=How to set .NET Preferences=<br />
<br />
In the TWAdmin workspace, navigate to Preferences on the [[VTB]]. From this location you are able to edit preferences at the [[Enterprise]], [[Organizational]] or [[User]] level and determine if users will be able to override certain preferences on the front end.<br />
<br />
:[[Image:Pref_Nav_75_Bold.jpg]]<br />
<br />
==Choosing Preferences Before Test Upgrade==<br />
An Excel workbook is available to record preference decisions before the system is available.<br />
Preferences drive much of the system behavior so it is easier to complete the other build tasks if preferences are set first. Preference decisions often require input from multiple representatives of the clinical staff and can therefore be time consuming. For these two reasons it is sometimes helpful to start this decision process before the test upgrade. The preferences can always be altered after the clinical team sees the test system. The worksheet also provides a record of your settings in the event a Hotfix or staff member changes them. We recommend only one person be allowed to change preferences and that same person maintain the worksheet for change control.<br />
<br />
First review the following articles to understand how each level is set, then review each preference description and record the organization's decisions in the workbook available via download below.<br />
<br />
Pay special attention to article: [[TW .NET Preferences#Setting .NET Preferences at the User Level for Multiple Users via SSMT|Setting .NET Preferences at the User Level for Multiple Users via SSMT]]. This article explains how to use the last column of the workbook.<br />
<br />
This workbook is also useful for organizations who wish to keep track of the preferences independent of the system in case they are altered by accident or for setting up new users.<br />
<br />
[http://wiki.galenhealthcare.com/images/c/c0/TW_.NET_Preferences_Workbook.xls .NET Preferences Workbook]<br />
<br />
==Setting Preferences at an Enterprise or Org Level==<br />
To set preferences for all users in a system, and to establish which preferences users have the ability to personalize (set themselves), the administrator will set these preferences at an Enterprise level.<br />
The ability of users to personalize can only be set at the enterprise level i.e. all users can personalize or no users can personalize. The ability of users to personalize cannot be set at the user level i.e. it is not possible for one user to personalize and another not. <br />
<br />
For this Example we are going to set how a user’s favorites are populated.<br />
<br />
# To set preferences at the Enterprise level, select Enterprise from the Ent/Org/User Settings dropdown.<br />
#:[[Image:Select_Enterprise.jpg]]<br />
# The preferences for populating favorites are located under the preferences category General so select General from the Preferences: dropdown.<br />
#:[[Image:Pref_Nav to General.jpg]]<br />
# Highlight the “Add Favorites Automatically” line <br />
# Click on the cell under the header “Value”<br />
# Setting the value to Y or N. Y = when providers make selections those selections will automatically be added to their favorites list, N = when providers make selections those selections will not automatically be added to their favorites list.<br />
# To allow the user to change this preference, keep the Can Override box checked.<br />
#: [[Image:Set_Add_Fav_75.jpg]]<br />
# Click save in the lower right hand corner of the screen<br />
# Login as a user and test to see if the interface acts as expected<br />
<br />
==Setting .NET Preferences at the User Level via TW Admin > Preferences==<br />
For this Example, the user level preference will be set to display the site selector when a user logs in<br />
<br />
# Select 'User' from the Ent/Org/User dropdown to edit settings at the user level<br />
# Select the organization the user belongs to<br />
# Click the binoculars to seach for the user. The Select a User dialog will open<br />
#:[[Image:LevelReplacement.jpg]]<br />
# Set the search criteria. In this case: UserName - Starting With - Test<br />
# Click binoculars to search<br />
# All users fitting the search criteria will be displayed. Highlight the user to be edited<br />
# Click OK<br />
#:[[Image:UserReplacement.jpg]]<br />
#:<br>The user level preferences will be displayed. Note that the User Can Override column is not available at this level. Only preferences with a value of user can override = Y will be visible.<br />
# Preferences are grouped into categories. Select the preference category from the Preference dropdown. For this example choose the preference category General<br />
# Select the preference row “Always Present Site Selector for User”<br />
# Click on the cell under the header “Value” and select a value from the dropdown. For a description of each preference and what the values will do see [[TW .NET Preferences#TW .NET Preferences|TW .NET Preferences]]<br />
# Click Save in the lower right hand corner of the screen<br />
#:[[Image:PrefReplacement.jpg]]<br />
# Login as a user and test to see if the interface acts as expected<br />
<br />
==Setting .NET Preferences at the User Level for Multiple Users via SSMT==<br />
In some cases an organization may want to set a preference differently for different users within the same organization. In this situation the best practice is to set the preference of the smaller group of users at the user level and leave the larger group of users at the org or enterprise level preference. These instructions use the example of setting the site selector to appear at login for floating nurses but not for anyone else.<br />
# Determine which group of users is smaller and create a list of their usernames. Of all the organization's users the floating nurses are the only users who prefer to have the site selector appear at login so they are the smaller group.<br />
# [[TW .NET Preferences#Setting Preferences at an Enterprise Level|Set the Enterprise or Org level preference]] based on what the majority of users prefers. Most users prefer the site selector not to appear at login so set the Enterprise or Org level preference to N<br />
# Choose a member of the smaller group and [[TW .NET Preferences#Setting .NET Preferences at the User Level via TW Admin > Preferences|set their preference at the user level in TW Admin]]. Test User is a floating nurse and wants the site selector to appear at login so set her user level preference to Y<br />
# Log out and extract the category '''TW .NET Preferences''' using SSMT<br />
# Use Excel to delete all rows except the one with 'Test User' under '''*HDRUserName'''<br />
#:[[Image:Excel1Replacement.jpg]]<br />
# Copy the setting to create as many rows as there are users in the smaller group<br />
#:[[Image:Excel2Replacement.jpg]]<br />
# Replace the '''*HDRUserName''' with the usernames of the smaller group<br />
#:[[Image:Excel3Replacement.jpg]]<br />
# Reload the table<br />
<br />
For more details about the SSMT category '''TW .NET Preferences''' see [[SSMT: TW .NET Preferences]]<br />
<br />
==How a User can set their own Personal Preferences==<br />
A provider can personalize their preferences from the clinical toolbar. For this example we are going to say that this user wants to include active problems in past medical history and automatically post those problems to the encounter summary.<br />
<br />
*Login as a provider<br />
*Navigate to Chart on the vertical toolbar<br />
*Select the arrow on the far right hand side of the Clinical Toolbar<br />
<br />
[[Image:Ppref1.jpg]]<br />
<br />
*From the dropdown menu, select personalize.<br />
<br />
[[Image:Ppref2.jpg]]<br />
<br />
This opens the Personalize dialog box. From here a provider has the ability to change many individualized settings to suit their personal preferences. <br />
<br />
*Navigate to the Problem Tab <br />
*Select “Problem include in PMH” and change the value to “checked for all”<br />
<br />
[[Image:Ppref3.jpg]]<br />
<br />
*select “post problem to encounter” and change the value to Y<br />
*click on Save<br />
<br />
=.NET Preferences=<br />
V11 Preferences can be set in the TWAdmin workplace, by entering the value that corresponds to the Preference.<br />
<br />
'''Categories'''<br />
Preferences are grouped into categories. The categories are General, Meds, Meds/Orders, Note, Orders, Problems and Results. Specific information about each preference is listed below.<br />
<br />
'''Recommended Setting''' - Recommended settings are based on certified workflows and the most common setting. Each of them must be reviewed with your organizations workflows in mind.<br />
<br />
===Clinical Trial Preferences===<br />
'''Works Time Batch Match Starting Time''' Added in v11.1.7<br />
<br />
Indicates the time that the night job runs. The night job reviews the next day's appointment list and compares the patients to the patients to the available clinical trial definitions. <br />
Available Options: 12:00 am; 1:00 am; 2:00 am; 3:00 am; 11:00 pm<br />
Default Value: 12:00 am<br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: N/A<br />
<br />
'''Clinical Trial Maximum Patient Drive Miles''' Added in v11.1.7<br />
<br />
The maximum number of miles the client would have a patient drive to participate in a trial. <br />
Available Options: 5, 10, 25, 50, 100<br />
Default Value: 5<br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: N/A<br />
<br />
==General Preferences==<br />
'''Add Favorites Lists Automatically'''<br />
*When set to 'Y', this preference causes items to get automatically assigned to a users favorites list as they use them. This includes meds, allergies, orders, and problems.<br />
*When set to 'N', items will not be added to a users favorite list unless they manually add it.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Allergy list Review'''<br />
Per Allscripts July, 2008 this preference is currently not used. It does not matter how it is set, but it is best to leave blank and revisited when the preference becomes active.<br />
Recommended Setting: Leave Blank<br />
<br />
'''Allow Advanced Personal Editing of Careguide templates'''<br />
* When set to 'Y' providers have the ability to edit many aspects of CareGuide Templates at a personal level, including adding new orderable items, deleting items, editing headers and rearranging items or headers. <br />
* When set to 'N', the provider has only the ability to save some preferences within the CareGuide Template. They may select their preferred medications, SIGs or labs, but the structure of the CareGuide is based on Enterprise settings.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Always Present Dialog When Printing Rx'''<br />
* When set to 'Y' the "Use Default Rx Printer" option on the commit screen will not be selected and the default behavior will be to show the Print Dialogue box when a medication is committed and activated. This forces the user to review the print dialogue before sending the print request.<br />
* When set to 'N' the "Use Default Rx Printer" option on the commit screen will be selected and the default behavior will be to suppress the Print Dialogue box when a medication is committed and activated. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Always Present Site Selector for User'''<br />
*When set to 'Y' the Site Selector will appear every time a user logs into AE-EHR. This is a great option for floating staff, but can become a nuisance.<br />
*When set to 'N' the Site Selector would only appear if a user hasn't previously set a default. In this case it will default to their default site. The user can change their site in AE-EHR if the menu item has been given to them. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is off by default, but can be allowed.<br />
<br />
'''Audit level''' - Allows administrators to capture and track the following information about users’ activity in the AE-EHR application including: User name, Patient name,Patient MRN, Access date, Access time, Device used (Web, PDA), Action time, Action taken (viewed, printed,created, and/or faxed), WebFramework Page accessed This setting determines the amount of information contained in the Audit Log Report. Please be aware that increasing the level of auditing increases the amount of data that is tracked and stored. Due to the nature of this, it can cause performance issues, so please be sure to test this before implementing in production. This is not seen often, but should be considered. These settings do not change the level of auditing on particular items such as notes. This simply changes what is written to the Audit log report. <br />
* When set to 'High' the audit trail will capture viewing, editing, creating, printing, and faxing of clinical items.<br />
* When set to 'Medium' the audit trail will capture editing, creating, and viewing of clinical items.<br />
* When set to 'Low' the audit trail will capture editing and creating of clinical items. <br />
<br />
Available Options: 'High', 'Medium', 'Low'<br />
Recommended Setting: 'Low' unless your Enterprise requires higher levels of auditing<br />
Can be set on these levels: Enterprise<br />
User Can Override: No, this is off and enforced<br />
<br />
'''CareGuide Default Opening Section''' Added in v11.1.7<br />
<br />
Allows users to choose the default opening section of CareGuides.<br />
* When set to 'All' the display opens all sections of the CareGuide selected<br />
* When set to 'Follow-Ups and Referrals' the display opens to the Follow-Ups and Referrals section of the CareGuide selected<br />
* When set to 'Instructions' the display opens to the Instructions section of the CareGuide selected<br />
* When set to 'Medications' the display opens to the Medications section of the CareGuide selected<br />
* When set to 'Orders' the display opens to the Orders section of the CareGuide selected<br />
<br />
Available Options: All, Follow-Ups and Referrals, Instructions, Medications, Orders<br />
Default Setting: All<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes<br />
<br />
'''Clinical Exchange Documents Verification'''<br />
* When set to 'Y' this will require verification when CED documents are imported. This means that a provider will be tasked with verifying the document before it becomes a true addition to the patient's chart. The task routing is based on the 'Clinical Exchange Documents Verification Routing' preference setting.<br />
* When set to 'N', the CED document would be imported and would not require verification prior to being added to the patient's chart.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Clinical Exchange Documents Verification Routing''' - If you have turned on "Clinical Exchange Document Verification" or "Clinical Exchange Documents Item Verification" this specifies the tasking behavior. <br />
* If set to 'Recipient then PCP then Clinical Exchange Document Team' the system will attempt to assign the task to the defined recipient first, if the system can't make a match or if the recipient isn't defined as a user, it will attempt to assign the task the the PCP defined for the patient. If the PCP isn't defined or is not setup as a AE-EHR user, the task would then be assigned to the Clinical Exchange Document Team. <br />
* If set to 'Recipient then Clinical Exchange Document Team' the system will attempt to assign the task to the defined recipient. IF the system can't make a match or the recipient isn't setup as a user, the task will get assigned to the Clinical Exchange Document Team.<br />
* If set to 'PCP then Clinical Exchange Document Team' the system will attempt to assign the task to the PCP first. If the patient does not have a PCP defined or the PCP is not setup as a user, the system will assign the task to the Clinical Exchange Document Team.<br />
* If set to 'Clinical Exchange Document Team' the task will be assigned to the Clinical Exchange Document Team.<br />
<br />
Available Options: 'Recipient then PCP then Clinical Exchange Document Team', 'Recipient then Clinical Exchange Document Team', <br />
'PCP then Clinical Exchange Document Team', 'Clinical Exchange Document Team' <br />
Recommended Setting: 'Clinical Exchange Document Team'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''ClinEGuide Credentials (User|Pwd)'''<br />
* This is a free text field which would hold your username and password for integration with the [http://www.clineguide.com/marketing/ContentPage.aspx Wolters Kluwer Clin-Eguide]. If a value is provided, an icon will apear on the v11 toolbar that looks like an open book. if a user selects the book, it will launch an Internet Explorer session which brings the user to the Clin-eguide home page. The credentials are passed with the action and will log them into the site if valid. <br />
<br />
Available Options: Free Text <br />
Recommended Setting: Blank<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Clinical Exchange Documents Item Verification'''<br />
* When set to 'Y' this will require verificaiton when CED items (meds, allergies, problems, etc.) are imported. This means that a provider will be tasked with verifying the clinical items before it becomes a true addition to the patient's chart. The task routing is based on the 'Clinical Exchange Documents Verification Routing' preference setting.<br />
* When set to 'N', the CED items would be imported and would not require verification prior to being added to the patient's chart.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Create Future Encounter''' Added in v11.1.7<br />
Allows the creation of future encounters<br />
* When set to 'Y' this will allow users to create documentation on a future encounter<br />
* When set to 'N' this will not allow users to create documentation on a future encounter<br />
<br />
Available Options: 'Y' or 'N'<br />
Defaulted Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Days Before Instruction Expiration Date To Consider Near Due'''<br />
* This Value is a number representing number of days. This tells the system when incomplete instructions should show as near due on the patient's chart. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Days Before Scheduled Order Expiration Date to Consider Near Due'''<br />
* This Value is a number representing number of days. This tells the system when incomplete or scheduled Orders should show as near due on the patient's chart. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Entering For Provider ID'''<br />
* This value specifies the default provider ID that should default into fields such as the Ordering Provider on medications or Orders within the system. This is primarily used for non-provider users that support a specific physician. For example, if an MA always works for Dr. Smith, they would want to set this within their personalize options so it would pre-populate and default properly. This is typically a setting that should be shown to users during training.<br />
<br />
Available Options: Any entry in the Provider Dictionary<br />
Recommended Setting: Blank Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default Specialty ID'''<br />
* This value specifies a non-provider's default specialty. This is best used as a personal setting from within the UI and should be shown to end users during training. This setting will default the specialty for a user in certain areas of the product that are driven by specialty such as the note selector, ACI specialty favorites, and flowsheets. Providers usually have their specialty specified in the provider dictionary and do not need to utilize this preference. <br />
<br />
Available Options: Any entry in the Specialty Dictionary<br />
Recommended Setting: Caution -Blank for user/providers (adverse affect of their favorites if not left blank),<br />
Users can populate as needed, but the recommended setign is still "Blank"<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default Supervising Provider ID'''<br />
* This value specifies the default supervising physician for users that require supervision with Orders. This should be shown during training and is best when set on a personal level. <br />
<br />
Available Options: Any entry in the Provider Dictionary<br />
Recommended Setting: Blank<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default to QuickList Favorites'''<br />
*When set to 'Y', this preference causes items to get automatically assigned to a users QuickList as they use them. This includes meds, allergies, orders, and problems.<br />
*When set to 'N', items will not be added to a users QuickList unless they manually add it.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Dictionary Cache'''<br />
* This setting is looking for a numeric value, but should be left alone. This is a development setting and is not intended to be used unless instructed otherwise. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: Do not change<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Dictionary Edit Max Count'''<br />
* This setting should be a value between 100 and 1000. This determines how many rows will be visible in a dictionary grid before the dictionary automatically goes into search mode.<br />
<br />
Available Options: Numeric Value between 100 and 1000<br />
Recommended Setting: 1000<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''DirectivesEditable'''<br />
* If set to 'Y' the Patient Directives on the Patient Profile Dialog or "i" screen will be editable. This would be set to 'Y' if you want users to document patient directives in the UI.<br />
* If set to 'N' the Patient Directives on the Patient Profile Dialog or "i" screen will be viewable only. This would be set to 'N' if you do not want users to document or edit this or if this value is populated through the registration interface. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Display <R> in Patient Banner for Restricted Documents''' Added in v11.1.7<br />
* If set to 'Y' the system will display the <R> in the patient banner when they have a restricted document. <br />
* If set to 'N' the system will not display the <R> in the patient banner when they have a restricted document. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise,Organization<br />
User Can Override: N/A <br />
<br />
'''Display Future Encounters in selector X days in the future'''<br />
* This is a numeric value which specifies how far in the future pending appointments are shown in the encounter selector. In most workflows, users will be working on an arrived appointment for the current day. If there are workflows that require people to prepare for a future appointment and begin documenting on encounters before the arrival occurs, this setting would allow those encounters to display and be selectable. It is advised that this be set to 1 to avoid any issues if the scheduling interface was to go down. If appointments can't be arrived in the system due to interface issue, this would allow end users the ability to complete their work on pending appointments until the issues are resolved. <br />
<br />
Available Options: Numeric Value between 0-99<br />
Recommended Setting: 1<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''DisplayPatientPicture'''<br />
* If set to 'Y', this would display the patient picture on the Patient Profile Page or "i" screen. This also allows the ability to upload pictures. <br />
* If set to 'N', this would hide the patient picture on the Patient Profile Page or "i" screen and would disable the ability to upload pictures.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Double Click Action'''<br />
* If set to "View" this would specify that double-clicking an item from the clinical desktop would open it in view mode.<br />
* If set to "Edit" this would specify that double-clicking an item from the clinical desktop would open it in edit mode.<br />
<br />
Available Options: 'View' or 'Edit'<br />
Recommended Setting: 'View'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Due Date or Start Date for Newly Added Bulk Enrollment'''<br />
* Bulk Enrollment is currently not available. Leave this as is for now.<br />
<br />
<br />
'''Enable Allergy Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' the system would generate verification tasks for providers when allergies are entered by non-provider users. In this setting a newly entered allergy will remain in a unverified mode until verified by a provider. This is important for JCAHO accreditation. <br />
* If set to 'N' the system will add allergies to the patient's allergy list in a completed status without verification from a provider.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Enable E-Prescribe G Code Alert''' Added in v11.1.7<br />
For 2009, to be a "successful e-prescriber", a provider must report the e-prescribing quality measure through their Medicare Part B claims on at least 50% of applicable cases during the reporting year. <br />
<br />
* If set to 'Y' a reminder will be added to the Encounter Summary for all Medicare patients that an e-Prescribing G-Code may be appropriate for this encounter. This is a reminder to the facility that they need to manually add the G-Code to their Encounter Form. This ensures all prescriptions should count towards the qualifications necessary to be seen as a "successful e-prescriber."<br />
* If set to 'N' no reminder will appear.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Enable MSHV''' Added in v11.1.7<br />
Determines whether or not the HealthVault specific settings should be available on the patient profile dialog. <br />
* If set to 'Y' the Health specific settings shodul display on the patient profile dialog and allow for a patient to be linked to their HealthVault account. <br />
* If set to 'N' then patient accounts cannot be linked to HealthVault.<br />
Note: Enterprise EHR usres should also not have the ability to import or export CEDs from MS HealthVault if this preference is set to N<br />
<br />
Available Options: 'Y' or 'N'<br />
Default Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Encounter Selection from Worklist'''<br />
* When set to 'Encounter Selector'<br />
* When set to 'Create New Encounter'<br />
<br />
Available Options: 'Encounter Selector' or 'Create New Encounter'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Summary Always Print Medication Profile''' Added in v11.1.7<br />
Encounter Summary: Always print medication profile<br />
* <br />
<br />
Available Options: 'Y' or 'N'<br />
Default Seting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Type for Worklist'''<br />
This preference previously only applied to results. Effective in v11.1.7, this preference is applied to all work done on Worklist. The intent is to reduce the instances when a use is presented with an encounter selector without increasing the number of times work done during an appointment is documented against a non-appointment encounter.<br />
<br />
Available Options: Active entries in the Encounter Type dictionary<br />
Recommended Setting: Chart Update<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Summary Default View'''<br />
* When set to 'Type' the encounter summary or commit screen will default to display items grouped by type (orders, problems, etc.)<br />
* When set to 'Problem' the encounter summary or commit screen will default to display items grouped by their associated problem. <br />
<br />
Available Options: 'Type' or 'Problem'<br />
Recommended Setting: 'Problem'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Encounter Summary Password Required on Save'''<br />
* If set to 'Y' the user must enter their password when saving the Encounter Summary <br />
* If set to 'N' the user does not need to enter their password when saving the encounter summary.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Encounter Summary Review Before Save'''<br />
*If set to 'Y', the encounter summary will appear when a user hits the commit button or leaves the patient's chart. This acts as a review process prior to committing the data. <br />
* If set to 'N', the Encounter Summary will not appear when a user hits the commit button or leaves the patient's chart. This will commit the data without the chance to review it. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is selected by default and should be shown in training<br />
<br />
'''Enterprise Emergency Telephone Number'''<br />
* This is a free text value designed to house the emergency telephone number for an Enterprise. This is displayed when printing patient instructions. <br />
<br />
Available Options: Free Text<br />
Recommended Setting: '911'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Fax Maximum Pages''' Added in v11.1.7<br />
Maximum number of pages (estimated)allowed in a chart fax<br />
* This is a numeric field<br />
<br />
Available Options: Free Text Numeric Field<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Fax Warning Type''' Added in v11.1.7<br />
Determines the type of warning users receive when exceeding the maximum number of pages to be faxed.<br />
<br />
Available Options: Block Fax, Disabled, Warn User<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''LanguageEditable'''<br />
* When set to 'Y', this allows users to edit the patient language on the Patient Profile Dialog or "i" screen. This allows users to specify the patient's primary language within AE-EHR.<br />
* When set to 'N', this will only allow users to view the patient's primary language on the Patient Profile Dialog or "i" screen. This is usually the preferred setting when this value is populated by the registration interface or if an organization prefers not to capture this information.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Mask SSN in Reports, Patient Search, & Patient Profile'''<br />
* When set to 'Y', this will hide the Social Security Number in the standard delivered reports, the patient search screen and the patient profile or "i" screen.<br />
* When set to 'N', this will allow users to see the Social Security Number in the standard delivered reports, the patient search screen and the patient profile or "i" screen.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Max # of Providers for All Provider View'''<br />
* This is a numeric value between 0-99. This specifies the maximum number of providers a user can add to the All Provider view. This is defined on the Daily Schedule within the personalize options. The recommendation is 20 and any more than that should be tested prior to implementing. This could introduce a performance issue or become unusable if too many schedules are merged together. <br />
<br />
Available Options: Numeric Value between 0-99<br />
Recommended Setting: 20<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Maximum Number of Seconds to allow for Worklist Load'''<br />
* This is a numeric value that represents the maximum number of seconds that the WorkList is allowed to consume before timing out. This setting is put into place to prevent any long term lock ups for a WorkList view that are improperly defined and potentially hindering system performance. In most cases, if the view is defined properly, this setting should have no merit. <br />
<br />
<br />
Available Options: Numeric Value <br />
Recommended Setting: 30<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Minimum # of Hours to Keep Patient Site Location and Encounter Status'''<br />
* This is a numeric value that establishes the length of time that the patient location and encounter status will be stored. This timeframe is based on the last update of either of the fields. For example, if this is set to 1 hour, this information would be cleared 1 hour after the last update to the patient location or encounter status. This is cleared out to ensure it is reset for the patients next visit. <br />
<br />
Available Options: Numeric value between 1-99<br />
Recommended Value: 2<br />
Available on these levels: Enterprise, Organization<br />
User Can Override? No, This is off and enforced<br />
<br />
'''Normative Growth Chart in Units'''<br />
* If set to ‘Us Units’ the Normative Growth chart will be displayed using US Units.<br />
* If set to ‘Metric Units’ the Normative Growth Chart will be displayed using Metric Units.<br />
<br />
Available Options: ‘Us Units’, ‘Metric Units’<br />
Recommended Value: ‘Us Units’<br />
Available on these levels: Enterprise, Organization, User<br />
User Can Override? Yes, This is on by default and should be shown during training. <br />
<br />
'''Authentication Time-Out'''<br />
* This is a numeric value that determines the number of minutes before the system requires authentication since the last time they authenticated. The system can be configured to ask for passwords when signing notes, prescribing medications, or committing the encounter summary. If a user has entered their password within the allowed timeframe defined by the setting, the user will not be required to enter their password. Once the time period has passed, the user will need to enter their password to verify their access. Setting this to 0 means that a user will need to enter their password once and their authentication session will not expire again during the session. <br />
Available Options: Numeric value from 0 – 99<br />
Recommended Setting: 5<br />
Available on these levels: Enterprise, Organization<br />
User can override? No, this is off an enforced<br />
<br />
'''Patient Tracking-Use Patient Encounter Status'''<br />
* If set to 'Y', this will enable this drop down and the values available for the assigned site will apear in the drop down for an arrived patient. <br />
* If set to 'N', the drop down box on the patient toolbar will be disabled, but still visible. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Patient Tracking-Use Patient Site Location'''<br />
* If set to 'Y', this will enable this drop down and the values available for the assigned site will appear in the drop down for an arrived patient. <br />
* If set to 'N', the drop down box on the patient toolbar will be disabled, but still visible. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Previously Discontinued Patient'''<br />
* If set to 'Immediate' the user will be prompted with a warning if an order being added has been discontinued for that patient in the past. <br />
* If set to 'Never' the user will not be warned of this condition.<br />
<br />
Available Options: 'Immediate' or 'Never' <br />
Recommended Setting: 'Never' <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Print Patient Education'''<br />
* If set to 'Always' the indicator on the encounter summary screen will be selected and printed anytime patient edcuation is available whether it is part of a CareGuide or custom education materials added by the client. This setting can be overridden on the encounter summary if the user doesn't want them for a specific encounter.<br />
* If set to 'CareGuide Only', the indicator on the encounter summary screen will be selected and printed anytime patient education is available if included with the CareGuide. This setting can be overridden on the Encounter Summary if the user doesn't want them for a specific encounter.<br />
<br />
Available Options: 'Always' or 'CareGuide Only'<br />
Recommended Setting: 'Always' <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option, but not selected by default<br />
<br />
'''Provider Selection limited to Favorites'''<br />
* If set to 'Y' the user or provider is limited to selecting a provider from their favorites list in the drop down. The search field will be hidden and they are prevented from selecting other providers. This is typically only used in a multi-org situation when it is not viable for users to see the entire list of providers. <br />
* If set to 'N' the user or provider has the ability to do a lookup against the entire provider dictionary. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Toolbar Default for Clinician Choice Button''' Added in v11.1.7<br />
Default for Clinical Choice Button to direct user to a specific tab in ACI<br />
<br />
Available Options: 'Active', 'Past Medical History', 'Past Surgical History', 'Family History', 'Social History'<br />
'Allergies', 'Medication History', 'Immunization History', 'Chief Complaint', 'Rx'<br />
'Medication Administration', 'Lab/Procedures', 'Imaging', 'Follow Up/Referral', 'Instructions'<br />
'Immunizations', 'Supplies', 'CareGuides', or 'QSets'<br />
Default Setting: 'Chief Complaint'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for History Builder Button''' Added in v11.1.7<br />
Default for History Builder Button to direct user to a specific History Builder tab in ACI<br />
<br />
Available Options: 'Active', 'Past Medical History', 'Past Surgical History', 'Family History', 'Social History'<br />
'Allergies', 'Medication History', 'Immunization History', or 'Chief Complaint'<br />
Default Setting: 'Active'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for Problem-Based Order Button''' Added in v11.1.7<br />
Default for Problem-Based Order Button to direct user to a specific Problem-Based Order tab in ACI<br />
<br />
Available Options: 'CareGuide' or 'QSets'<br />
Default Setting: 'QSets'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
<br />
'''Toolbar Default for Rx/Orders Button - Lab Icon''' Added in v11.1.7<br />
Default for Rx/Orders Button - Lab Icon to direct user to a specific Rx/Orders tab in ACI<br />
<br />
Available Options: 'Lab/Procedures', 'Imaging', 'Follow Up/Referral', 'Instructions'<br />
'Immunizations', or 'Supplies'<br />
Default Setting: 'Lab/Procedures'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for Rx/Orders Button - Rx Icon''' Added in v11.1.7<br />
Default for Rx/Orders Button - Rx Icon to direct user to a specific Rx/Orders tab in ACI<br />
<br />
Available Options: 'Rx' or 'Medication Administration'<br />
Default Setting: 'Rx'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''UA Install Location''' This preference is no longer used. <br />
<br />
'''Use Clinical Desktop Default View When Switching Patients''' Added in v11.1.7<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Use Organization or Site Address for Patient Ed Print Out''' Added in v11.1.7<br />
Determines which address to display on the patient education print out. <br />
<br />
Available Options: 'Site' or 'Organization'<br />
Default Setting: 'Organization'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''URL to find the UAI DesktopAgent install (optional)'''<br />
* This setting is to be used by clients using the UAI application only. If this is to be used, the technical resource installing the UAI tool would provide the appropriate setting for this field. <br />
<br />
Available Options: Free Text - provided by technical representative<br />
Recommended Setting: Blank unless using UAI<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Works 0 FingerPrintAuthEnc'''<br />
* This is disabled and not used at this time. Do not modify. <br />
<br />
'''Workspace view for tasks that navigate to worklist'''<br />
* This setting determines the default clinical desktop view to use when working an worklist related item from the task list. When a worklist task is double-clicked from the task list, it will navigate the user to the clinical desktop and use the defined view. This should be set to a Clinical Desktop View that is designed to efficiently complete worklist items. <br />
<br />
Available Options: Drop down list of available clinical desktop views<br />
Recommended Setting: Worklist view designed to efficiently complete worklist items<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this should be explained in training.<br />
<br />
==Meds Preferences==<br />
'''Apply to All checkbox on the Print Dialog presented for Prescriptions'''<br />
* If set to 'Y' the 'apply to all' checkbox will be selected by default on the Prescription Print Dialog.<br />
* If set to 'N' the 'apply to all' check box will not be selected by default on the Prescription Print Dialog.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Auto Dispense Inventory Medications''' Added in v11.1.7<br />
Set prescribe action to dispense for in-inventory medications<br />
<br />
Available Options: 'Y' or 'N'<br />
Default Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Days Before RxAction Date To Consider Near Due'''<br />
* This is a numeric value between 0-99. This represents the number of days prior to a Prescription Action being due to consider it near due and a reminder is created. <br />
<br />
Available Options: Numeric value between 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Rx Action for a renewal from'''<br />
* If set to 'previous action' the renewed prescription will default to the Rx action used during for the original version of the prescription.<br />
* If set to 'User Default' the renewed prescription will default to the users default Rx action. <br />
<br />
Available Options: 'previous action', 'user default'<br />
Recommended Setting: 'previous action'<br />
Can be set on these levels: Enterprise, Organization, user<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Default Rx Action'''<br />
* If set to 'Call Rx' the Rx action will default to Call Rx.<br />
* If set to 'Dispense Sample', the Rx action will default to Dispense sample.<br />
* If set to 'Print Rx' the Rx action will default to Print Rx.<br />
* If set to 'Record' the Rx action will default to Record.<br />
* If set to 'Send To Mail Order' the Rx action will default to Send To Mail Order.<br />
* If set to 'Send to Retail' the Rx action will default to Send to Retail.<br />
<br />
Available Options: 'CallRx', 'Dispense Sample', 'Print Rx', 'Record', 'Send To Mail Order', 'Send to Retail'<br />
Recommended Setting: 'Send to Retail'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Default Admin By'''<br />
* If set to 'Y' the Default Admin By for a Medication Administration and Immunizations will default based on the previously used value. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin By for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
<br />
'''Default Admin Date'''<br />
* If set to 'Y' the Default Admin Date for a Medication Administration and Immunizations will default based on the previously used value. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Date for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Dose'''<br />
* If set to 'Y' the Default Admin Dose for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Dose for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Lot'''<br />
* If set to 'Y' the Default Admin Lot for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Lot for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Manufacturer'''<br />
* If set to 'Y' the Default Admin Manufacturer for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Manufacturer for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Route'''<br />
* If set to 'Y' the Default Admin Route for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Route for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Site'''<br />
* If set to 'Y' the Default Admin Site for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Site for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Disp Save Default'''<br />
* If set to 'Y', this defaults the 'save as default for selected SIG' option to be selected on the medication screen. If this information is saved, the next time a provider selects that SIG, the Days, Quantity, Units, Refill, and DAW option will fill in based on the previously saved values. <br />
* If set to 'N', the 'save as default for selected SIG' will not be selected by default, but the provider can select this option if they prefer to save a default from time to time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
<br />
'''DUR Acknowledge Reason''' <br />
* If set to 'Y' the user must provide a reason when ignoring a DUR Warning. <br />
* If set to 'N' the user will not be required to provide a reason for ignoring the warning. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Dose Check Interrupt Timing''' <br />
* If set to 'Immediate' the user will be prompted with a dose check DUR warning immediately after selecting the medication. For this setting to work, the Enterprise DUR settings for dosage must also be on.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Alcohol Check Interrupt Timing''' [DUR Preferences are no longer set per severity levels. They can only be set to "Immediate" or "Never".]<br />
* If set to 'Immediate' the user will be prompted with an alcohol check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Alcohol screening must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Drug Check Interrupt Timing''' [DUR Preferences are no longer set per severity levels. They can only be set to "Immediate'or Never".]<br />
<br />
* If set to 'Immediate' the user will be prompted with a drug-drug check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Drug-Drug interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Food Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a food check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for food screening interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning.<br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Healthstate Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Drug-Health State check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Drug-Health State interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Duplicate Therapy Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Duplicate Therapy DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Duplicate Therapy interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning.<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise''' <br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Immunization - Expiration Date''' Added in v11.1.7<br />
Determines whether or not an expiration date is required to complete an immunization administration. <br />
* If set to 'Y' this will require the user to enter an expiration date<br />
* If set to 'N' this will not require the user to enter an expiration date<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Lot Required''' Added in v11.1.7<br />
Determines whether or not a lot is required to complete an immunization administration.<br />
* If set to 'Y' this will require the user to enter a lot number<br />
* If set to 'N' this will not require the user to enter a lot number<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Manufacturer''' Added in v11.1.7<br />
Determines whether or not a manufacturer is required to complete an immunization administration.<br />
* If set to 'Y' this will require the user to enter a manufacturer number<br />
* If set to 'N' this will not require the user to enter a manufacturer number<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - NDC''' Added in v11.1.7<br />
Determines whether or not an NDC number is required to complete an immunization administration. If Chargeable, is required only when value is configured in Charge Code field in OID.<br />
* If set to 'Y'<br />
* If set to 'N'<br />
* If set to 'Chargeable'<br />
<br />
Available Options: 'Y', 'N' or 'Chargeable'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Requiredness''' Added in v11.1.7<br />
Required field behavior.<br />
* If set to Required to Complete<br />
* If set to Required to Save<br />
<br />
Available Options: 'Required to Complete' or 'Required to Save'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Expiration Date ''' Added in v11.1.7<br />
Determines whether or not an expiration date is required to complete a medication administration. <br />
* If set to 'Y' an expiration date is required to complete a medication administration<br />
* If set to 'N' an expiration date is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Lot Required ''' Added in v11.1.7<br />
Determines whether or not a lot is required to complete a medication administration. <br />
* If set to 'Y' a lot is required to complete a medication administration<br />
* If set to 'N' a lot is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Manufacturer''' Added in v11.1.7<br />
Determines whether or not a manufacturer is required to complete a medication administration. <br />
* If set to 'Y' a manufacturer is required to complete a medication administration<br />
* If set to 'N' a manufacturer is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A <br />
<br />
'''Med Admin - NDC''' Added in v11.1.7<br />
Determines whether or not an NDC number is required to complete an medication administration. If Chargeable, is required only when value is configured in Charge Code field in OID.<br />
* If set to 'Y'<br />
* If set to 'N'<br />
* If set to 'Chargeable'<br />
<br />
Available Options: 'Y', 'N' or 'Chargeable'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Requiredness''' Added in v11.1.7<br />
Required field behavior.<br />
* If set to Required to Complete<br />
* If set to Required to Save<br />
<br />
Available Options: 'Required to Complete' or 'Required to Save'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''PAR Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Prior Adverse Reaction (PAR) warning immediately after selecting the medication. For this to work the Enterprise settings for PAR interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable Rx Hub Medication History'''<br />
* If set to 'Y' the application will allow patient history to be loaded from Rx Hub. This requires that the patient's medication benefits information is added to the application and a match can be made with the Rx Hub Warehouse. If these items are both true, a patients historical medications will be loaded into the system. <br />
* If set to 'N' the system will not attempt to load the patient's historical medications. <br />
* New in v11.1.6 and newer this can be disabled for individual patients to meet HIPPA -see [[Med History Patient Disable]] <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable SCRIPT Messaging'''<br />
* If set to 'Y' then Script messaging is enabled between the physician and the pharmacies using the SureScripts network. This requires other setup as well, but must be enabled for physicians or systems that have been setup and want to use this type of messaging. When turned on, the system will determine if the pharmacy is a script enabled pharmacy and determine if a script should be sent electronically or as a fax. This occurs when the Rx Action is Send to Retail. Inbound Script messages will appear as New Prescription Request (NEWRX), Renewal Request (REFREQ), and Renewal Response (REFRES) messages.<br />
* If set to 'N' Script messaging will be disabled. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N', unless setup for SureScripts usage<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Enable Touchscript Messaging'''<br />
* If 'Y' is selected then organizations can send in-office medication requests from AE-EHR to TouchScripts. This would be used if you are using the FirstFill product which is a part of TouchScripts. If you are interested in this product you would contact your account manager.<br />
* If set to 'N' this feature will be disabled.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N', unless setup for FirstFill usage<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Formulary Alternatives Reason Required'''<br />
* If set to 'off formulary with preferred' the user would be required to enter a reason for prescribing a specific medication when the medication is off formulary and there are preferred medications available. <br />
* If set to 'preferred' the user would be required to enter a reason for prescribing a specific medication when the medication has preferred alternatives available.<br />
* If set to 'never' the user would not be forced to provide a reason for ignoring formulary alternatives. <br />
<br />
Available Options: 'off formulary with preferred', 'preferred', 'never'<br />
Recommended Setting: 'never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Formulary Checking Interrupt Timing'''<br />
* If set to 'Immediate' the user would be prompted with formulary checking alternatives as they are prescribing the medication. <br />
* If set to 'Deferred' the user would be prompted with formulary checking alternatives as they are committing the encounter summary information.<br />
* If set to 'Never' the user would not receive the warning.<br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Immunization Order Authorization Required'''<br />
* If set to 'Prospective' a task will be created for a user/provider that does not have the appropriate medication prescribing levels. The task must be authorized by the ordering provider before the request can be fulfilled.<br />
* If set to 'Retrospective' a task will be created for the ordering provider for auditing purposes only. The immunization can still be fulfilled at the time of entry, but the audit task will be created for review. <br />
* If set to 'Not Required' no tasks will be created and the immunization will be completed at the time of entry and completion. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Not Required'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
*Special Note - If a user has the 'Med Order Protocol' Security code assigned to them, they do have the ability to override the Prospective authorization setting. This allows for users to choose "Per Protocol" or "Per Verbal Order" on the Immunization Detail screen and allows for clinics to continue these workflows. This would change the setting to Retrospective in this case and the provider would receive an audit task. <br />
<br />
'''MAR Prescription BarCode'''<br />
* If set to 'AHS RX Number' the bar code printed on the MAR prescription will use the Allscripts Rx Number. <br />
* If set to 'NDC' the bar code printed will have the National Drug Code. <br />
* If set tp 'GPI' the bar code printed will use the Gingival-Periodontal Index code. <br />
<br />
Available Options: 'AHS Rx Number', 'NDC', 'GPI'<br />
Recommended Setting: Leave this setting alone. This is only used with the MAR product which most clinics do not use. <br />
For the few clients that do use this module, this setting would be based on their needs.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Med History Query Duration'''<br />
* Available in 11.1.6 and newer only!<br />
* Allows for a specific amount of time (in months) for retrieval of patients medication history from Rx Hub<br />
* Configurable from one month to 24 months.<br />
Available Options: Numeric from 1 to 24<br />
Default Setting: is 6 (months)<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Minutes Before Re-Authentication Is Required For Medication Order'''<br />
* This preference is enacted when the setting for '''Order Authentication Required''' is set to yes. If order authentication is required, this value is the number of minutes before a user is required to reauthenticate within the system. If this setting is set to 0, the system will only ask for a password once during a session when ordering a med. If set to 5, the user will need to reauthenticate if they have not completed an action that required authentication within the past 5 minutes. This setting does not apply to the login screen.<br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: '0'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Non-Scheduled Meds Order Authorization Required'''<br />
* If set to 'Prospective' a task will be created for a user/provider that does not have the appropriate medication prescribing levels. The task must be authorized by the ordering provider before the request can be fulfilled.<br />
* If set to 'Retrospective' a task will be created for the ordering provider for auditing purposes only. The medication request can still be fulfilled at the time of entry, but the audit task will be created for review. <br />
* If set to 'Not Required' no tasks will be created and the medication request will be completed at the time of entry and completion. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Prospective'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
*Special Note - If a user has the 'Med Order Protocol' Security code assigned to them, they do have the ability to override the Prospective authorization setting. This allows for users to choose "Per Protocol" or "Per Verbal Order" on the Medication Detail screen and allows for clinics to continue these workflows. This would change the setting to Retrospective in this case and the provider would receive an audit task. <br />
<br />
'''OrderPresentForumlaryAlternatives'''<br />
* If set to 'off formulary with preferred' the user would be presented with formulary alternatives when the medication is off formulary and there are preferred medications available. <br />
* If set to 'preferred' the user would be presented with formulary alternatives when the medication has preferred alternatives available.<br />
* If set to 'never' the user would not be presented with formulary alternatives. <br />
<br />
Available Options: 'off formulary with preferred', 'preferred', 'never'<br />
Recommended Setting: 'off formulary with preferred'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on and should be described during training<br />
<br />
<br />
'''Prohibit Transmission of Schedule III Rx'''<br />
* If set to 'Y' the transmission of Schedule III drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule III drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule II Rx'''<br />
* If set to 'Y' the transmission of Schedule II drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule II drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule IV Rx'''<br />
* If set to 'Y' the transmission of Schedule IV drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule IV drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule V Rx'''<br />
* If set to 'Y' the transmission of Schedule V drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule V drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Override Sign Rx Task for Schedule II Meds'''<br />
* This setting is not used and should be left blank.<br />
<br />
'''Override Sign RX Task for Schedule III-V Meds (Override Sign Rx CIII-V)'''<br />
* This setting is not used and should be left blank.<br />
-------------------------------------------------------------------------------------------------------------<br />
'''Enable Medication Administration Schedule''' - Need to verify this. This preference goes along with the MAR system.<br />
<br />
* If set to 'Y' the ability to schedule a medication administration is available.<br />
* If set to 'N' the ability to schedule a medication administration is not available.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
-------------------------------------------------------------------------------------------------------------<br />
'''Non-Formulary Authorization Required'''<br />
* If set to 'Y' the medication will require authorization prior to fulfillment if prescribing off formulary and will not print without authorization.<br />
* If set to 'N' the system will not require authorization if prescribed medications are off formulary<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribe Print Problem'''<br />
* If set to 'Y' the problem tied to the medication will be printed on the prescription.<br />
* If set to 'N' the problem tied to the medication will not display on prescriptions.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Sites'''<br />
* If set to 'Y' the Site will display on the prescription<br />
* If set to 'N' the Site will not display on the prescription<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Sites name/address on the printed scheduled prescription'''<br />
* If set to 'Y' the Site name and address will display on the controlled prescription<br />
* If set to 'N' the Site name and address will not display on the controlled prescription<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Prescribe Problem Linking Required'''<br />
* If set to 'Required to Save", the prescription details screen will require a user to select a linked problem prior to saving the prescription. <br />
* If set to 'Needs Info Reason', the user does not have to select a problem on the medication detail screen, but the medication will go to a needs info status and create a "Rx Info - Problem" task. This task will need to be worked and completed before the medication can be fulfilled.<br />
* If set to 'Not Required' the system will not force the user to select a problem when prescribing or renewing a medication.<br />
<br />
Available Options: 'Required to save', 'needs info reason', 'not required'<br />
Recommended Setting: 'Required to save' - this helps build quicksets<br />
Can be set on these levels: Enterprise, Organization, user<br />
User Can Override: Yes this is an option<br />
<br />
'''Editing Rx updates Ordered By Field'''<br />
* If set to 'Y' the Ordered by field will update to the current user renewing a medication if they are a valid ordering provider. This can be a good feature when physicians are covering for others and the desired behavior is to have the actual prescribing doctor documented as the Ordering Physician.<br />
* If set to 'N' the original Ordering Provider will remain unless manually overridden. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Warn if a medication is not participating in checking'''<br />
* If set to 'Y' the user will be prompted when prescribing a medication that does not participate in DUR checking. This is usually the case with user defined medications.<br />
* If set to 'N' the user will not be prompted when prescribing a medication that does not participate in DUR checking.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show Allscripts watermark on Faxed Prescriptions'''<br />
* If set to 'Hide' the Allscripts watermark will not appear on faxed prescriptions.<br />
* If set to 'Show' the Allscripts watermark will appear on faxed prescriptions.<br />
<br />
Available Options: 'Show' or 'Hide'<br />
Recommended Setting: 'Show'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Allscripts watermark on Printed prescriptions'''<br />
* If set to 'Hide' the Allscripts watermark will not appear on printed prescriptions.<br />
* If set to 'Show' the Allscripts watermark will appear on printed prescriptions.<br />
<br />
Available Options: 'Show' or 'Hide'<br />
Recommended Setting: 'Show'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribing without Allergy Status'''<br />
* If set to 'Prevent' the user will be prompted when a patient's allergy status is not set. This will require them to define a patient's allergy status prior to completing a medication request. <br />
* If set to 'Warn' the user will receive a warning message stating the patient has an unknown allergy status when they are not defined for a patient. This occurs when selecting a medication from the ACI. <br />
* If set to 'Do Not Warn' the user will not receive a warning when prescribing medications.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a non-controlled medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a non-controlled medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a non-controlled medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required for Schedule II Meds'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a schedule II medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a schedule II medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a schedule II medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required for Schedule III-V Meds'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a schedule III-V medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a schedule III-V medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a schedule III-V medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribing without Pharmacy Specified'''<br />
* If set to 'Prevent' the user will be prompted when a patient's pharmacy is not set. This will require them to define a pharmacy prior to completing a medication request. <br />
* If set to 'Warn' the user will receive a warning message stating the patient has no pharmacy when they are not defined for a patient. This occurs when selecting a medication from the ACI. <br />
* If set to 'Do Not Warn' the user will not receive a warning when prescribing medications and a pharmacy is not defined.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Require Re-Authentication For New or Renewed Prescriptions'''<br />
* If set to 'Y' the physician or user will be prompted to enter their password when prescribing or renewing a medication. This behavior is also dependant on the 'Authentication Time-Out' in the general preferences.<br />
* If set to 'N' the physician or user will not be prompted to enter their password.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Disable faxing of Class 2,3,4,5 Scheduled Meds'''<br />
* If set to '2' the system will not allow faxing of schedule II medications<br />
* If set to '2,3' the system will not allow faxing of schedule II or III medications<br />
* If set to '2,3,4' the system will not allow faxing of schedule II, III or IV medications<br />
* If set to '2,3,4,5' the system will not allow faxing of controlled medications<br />
* If set to 'Always' the system will not allow faxing of medications<br />
* If set to '' all medication levels will fax<br />
<br />
Available Options: '2', '2,3', '2,3,4', '2,3,4,5', 'Always', ''<br />
Recommended Setting: '2' - this is the typical state requirement. <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Disable Printing of Class 2,3,4,5 Scheduled Meds'''<br />
* If set to '2' the system will not allow printing of schedule II medications<br />
* If set to '2,3' the system will not allow printing of schedule II or III medications<br />
* If set to '2,3,4' the system will not allow printing of schedule II, III or IV medications<br />
* If set to '2,3,4,5' the system will not allow printing of controlled medications<br />
* If set to 'Always' the system will not allow printing of medications<br />
* If set to '' all medication levels will print<br />
<br />
Available Options: '2', '2,3', '2,3,4', '2,3,4,5', 'Always', ''<br />
Recommended Setting: '' <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''RxWeb List Limit'''<br />
* This is a numeric value that limits the number of medications returned in a search. This can be limited if searching is causing slow responses, but typically this is left blank.<br />
<br />
Available Options: Numeric value between 0-99<br />
Recommended Setting: leave blank (unlimited)<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option<br />
<br />
<br />
'''Samples - Expiration Date Required'''<br />
* If set to 'Y' the Expiration Date would be a required field when dispensing samples.<br />
* If set to 'N' the Expiration Date would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Lot Required'''<br />
* If set to 'Y' the Lot Number would be a required field when dispensing samples.<br />
* If set to 'N' the Lot Number would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Manufacturer required'''<br />
* If set to 'Y' the Manufacturer would be a required field when dispensing samples.<br />
* If set to 'N' the Manufacturer would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Quantity Required'''<br />
* If set to 'Y' the Quantity would be a required field when dispensing samples.<br />
* If set to 'N' the Quantity would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Quantity Units Required'''<br />
* If set to 'Y' the Quantity Units would be a required field when dispensing samples.<br />
* If set to 'N' the Quantity Units would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Schedule III to V Meds Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task would be created if a level III to V medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and the medication would not be fulfilled until the provider authorizes the task.<br />
* If set to 'Retrospective' a Order Notification task would be created if a level III to V medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and serves as an audit trail. The medication would be fulfilled immediately and does not require this task to be worked first. <br />
* If set to 'Not Required' no tasks will be created if a level III to V medication is prescribed by a user without proper license information. That medication would be fulfilled immediately. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required' <br />
Recommended Setting: 'Prospective' - this should be based on your organizations policy<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Schedule II Meds Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task would be created if a level II medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and the medication would not be fulfilled until the provider authorizes the task.<br />
* If set to 'Retrospective' a Order Notification task would be created if a level II medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and serves as an audit trail. The medication would be fulfilled immediately and does not require this task to be worked first. <br />
* If set to 'Not Required' no tasks will be created if a level II medication is prescribed by a user without proper license information. That medication would be fulfilled immediately. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required' <br />
Recommended Setting: 'Prospective' - this should be based on your organizations policy<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
==Meds/Orders Preferences==<br />
'''Duplicate Checking Order Interval (Hrs)'''<br />
* This Value is a number representing number of hours. This tells the system how many hours in the past it should look for a duplicate order. If a duplicate is found within the specified timeframe, the user will receive a message with that information, which allows them to determine if another test is needed or not. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 48<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable Rx-Orders Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' this will require verification when non-provider users enter med or order history. This means that a provider will be tasked with verifying the clinical items before it becomes a true addition to the patient's chart. A Task would be created for the Ordering physician to verify.<br />
* If set to 'N', the med or order entries would not require verification prior to being added to the patient's chart when added by a non-provider user.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Med/Orders List Review''' - Leave blank, this is currently unused.<br />
<br />
'''Monitor Order Selection'''<br />
* If set to 'Y' the system will track how users are selecting orders. This will determine if the user used their favorites, QuickSets or CareGuides. This can be used to review workflows. This information is stored in the database, but would require a special script to retrieve the data.<br />
* If set to 'N', they will not track how orders are selected.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Cancel Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Cancel reason if they choose to cancel an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Cancel reason, but it is not required to continue.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Cancel reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Chargeable Requires Billable ICD-9'''<br />
* If set to 'Required to Save' the system will require that the problem is tied to a billable Problem with an appropriate ICD9 code when the Orderable item is defined as chargeable. This will need to be selected before the user can save the Order.<br />
* If set to 'Needs Info Reason' the system will allow a user to save an Order with a CPT code, but it would go to a needs info status until someone associates an appropriate billable problem to the Order. <br />
* If set to 'Not Required' the system will not require a chargeable order be tied to an appropriate billable problem. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''CPT Requires Billable ICD9'''<br />
* If set to 'Required to Save' the system will require that the problem is tied to a billable Problem with an appropriate ICD9 code when the Orderable item has an associated CPT code. This will need to be selected before the user can save the Order.<br />
* If set to 'Needs Info Reason' the system will allow a user to save an Order with a CPT code, but it would go to a needs info status until someone associates an appropriate billable problem to the Order. <br />
* If set to 'Not Required' the system will not require a chargeable order be tied to an approapriate billable problem. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Discontinue Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Discontinue reason if they choose to discontinue an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Discontinue reason, but it is not required to discontinue.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Discontinue reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''OderDeferReason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Defer reason if they choose to defer an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Defer reason, but it is not required to defer.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Defer reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Entered in Error Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Entered in Error reason if they choose to mark an order as entered in error. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Entered in Error reason, but it is not required to mark an order as entered in error. <br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Entered in Error reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''OrderPermanentDeferReason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Permanent Defer reason if they choose to permanently defer an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Permanent Defer reason, but it is not required to permanently defer.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Permanent Defer reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Void Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Void reason if they choose to void an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Void reason, but it is not required to void an order.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Void reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Create Overdue Tasks for'''<br />
* If set to 'All Overdue' the system will create Overdue order tasks assigned to the ordering provider for all orders that are considered overdue. <br />
* If set to 'Overdue Important' the system will create overdue order tasks assigned to the ordering provider if the ordering provider selected the "Overdue Important" setting on the Order Details screen. <br />
<br />
Available Options: 'All Overdue', 'Overdue Important'<br />
Recommended Setting: 'Overdue Important'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
==Note Preferences==<br />
<br />
'''Document Add Review Stamp''' Add in v11.1.7<br />
Add review stamp when a document review task is completed. <br />
* When set to 'Y' a review stamp displaying the reviewing provider's name, date & time will display on the document reviewed.<br />
* When set to 'N' no review stamp will display<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes<br />
<br />
'''Note Auto Unlock Notes After Time'''<br />
* This is a numeric value that represents hours. This will tell the system how many hours should occur before the system automatically unlocks v11 note. A note remains locked when a user is editing a note and at times this can be left open accidentally or an issue may have occurred that didn't properly close the note. This preference only applies to v11 note. This preference prevents notes from being locked when there is no AE-EHR session open. <br />
<br />
<br />
<br />
Available Options: Numeric value<br />
Recommended Setting: 24<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Make Final'''<br />
* Allows the System Administrator to configure a default state for the Make Final option on the Note Signature page to accommodate the provider’s most common workflow for signing documents and the need to finalize.<br />
* If set to 'Y' the 'Make Final' checkbox will default to being selected when a user or provider that has the appropriate signature levels. <br />
* If set to 'N' the 'Make Final' checkbox will default to not being selected.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Navigation After Signing'''<br />
<br />
* Determines to which page the system navigates after the user signs a note.<br />
* If set to 'No Navigation' the user or provider will not be taken off of the note upon signing. <br />
* If set to 'Schedule' the user or provider will be brought to the Daily Schedule screen upon signing the note.<br />
* If set to 'Task View' the user or provider will be brought to the Task List screen upon signing the note.<br />
* If set to 'MD Charges' the user or provider will be brought to the Charge screen upon signing the note.<br />
<br />
Available Options: 'No Navigation', 'Schedule', 'Task View', 'MD Charges'<br />
Recommended Setting: 'No Navigation' - this really should be set on a user level based on their desired workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Note Default Owner'''<br />
* Determines the default owner for Notes.<br />
* If set to 'Use Appointment Encounter Provider if available, else use Most Recently Used' the system will default the note owner as the Appointment Provider. If there is no encounter provider available it will default to the most recently used provider.<br />
* If set to 'Always use Most recently used note owner' the system will default the note owner to the last provider used for that user. This is a preferred method when the user primarily works from an ancillary schedule such as a Lab Schedule and the encounter provider is not an actual human.<br />
* If set to 'None' the note owner will not default and will need to be selected each time a new note is created.<br />
<br />
Available Options: 'Use Appointment Encounter Provider if available, else use MRU', 'Always use MRU note owner', 'None'<br />
Recommended Setting: 'Use Appointment Encounter Provider if available, else use MRU'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Signature Display'''<br />
<br />
* This setting defines the format of the signature when signing a note. The available formats are:<br />
<br />
# Firstname Lastname, Credentials; Date/Time (Signature Type) <br />
# Firstname Lastname, Credentials; User/Profession Date/Time (Signature Type) <br />
# Firstname Lastname, Date/Time (Signature Type) <br />
# Firstname Lastname, User/Profession Date/Time (Signature Type)<br />
<br />
Recommended Setting: 'Firstname Lastname, Date/Time (Signature Type)'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Signature Type'''<br />
* This is a drop down menu that lists all available options from the Signature Type dictionary. The option selected will be defaulted into the Sign Note dialog box.<br />
<br />
Available Options: All active entries from the Signature Type dictionary<br />
Recommended Setting: Leave Blank and train the user to set the appropriate default.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Visit Type'''<br />
* Allows users to default to the previously used Visit Type.<br />
* If set to 'None' the visit type will not have a default value on the v11 note selector screen.<br />
* If set to 'Last' the visit type will default to the last visit type selected in the v11 note selector screen.<br />
<br />
Available Options: 'None', 'Last'<br />
Recommended Setting: 'Last'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Don't Generate Document Appt Encounter Tasks'''<br />
* If set to 'Y' the system will not generate Document Appointment Encounter Tasks.<br />
* If set to 'N' the system will generate Document Appointment Encounter Tasks. This task would serve as a reminder for the appointment encounter provider to create a note for the patients visit. The task will automatically be removed once a note is created. Most organizations use the note icon display on the schedule as the reminder or confirmation that all notes were created and choose not to use this option.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Don't Generate Review Covered Note Tasks'''<br />
* If set to 'Y' the system will not generate Review Covered Note Tasks.<br />
* If set to 'N' the system will generate Review Covered Note Tasks. This task would apply when a physician is covering for another doctor and signs off on a note for them. This setting also depends on the 'Create Review Covered Note Task on Finalization' setting in the [[Document Type]] dictionary. Both settings must be set properly to activate the task workflow.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Note Lock Lists After Number Days'''<br />
<br />
* This is a numeric value that defines how many days until all lists within a note are locked. This includes lists such as Problems, Vitals, Immunizations, and Medications. This only applies to notes that have not been finalized. Once a note is finalized or this time limit has been reached, the lists will not update automatically.<br />
<br />
<br />
Available Options: Numeric value<br />
Recommended Setting: 7<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Is V10 Note User Only'''<br />
* If set to 'Y' the user or provider will only be able to create v10 notes. The v10 note selector will be presented to the user.<br />
* If set to 'N' the user or provider will be presented with the v11 note selector and have the ability to select either version of notes available to them. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: This should be set based on the organizations preference to use v11 note<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''CC or RFV Required for E&M Code''' - need further details to explain.<br />
* If set to 'Y' the E&M coder will require the CC or RFV be set.<br />
* If set to 'N' the E&M coder will not require these values. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''E/M Coder default to MDM tab'''<br />
* If set to 'Y' the E/M coder will default to the Medical Decision Making tab instead of the Summary tab.<br />
* If set to 'N' the E/M coder will default to the Summary tab.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''Post Text to Current Note'''<br />
* If set to 'Y' the default will be for the "post text to current note" option to be on. This will tell the system that the users actions should be posted to a note. There is a toggle button on the Clinical toolbar that can change this behavior easily during certain workflows. <br />
* If set to 'N' the default will be for the "post text to current note" option to be off. There is a toggle button on the Clinical toolbar that can change this behavior easily during certain workflows. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''UseAutoPrintForDefaultTemplate'''<br />
* If set to 'Y' the document will print using the document type specific document template and override the users preferred setting. This can be useful if certain types of document require specific document templates. <br />
* If set to 'N' the users auto-print defaults will be used. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
==Orders Preferences==<br />
'''Add Clinical Item Order Selection Method Default'''<br />
* If set to 'Problem Based' the ACI window will default to the problem based tab which is best for users that utilize CareGuide or QuickSets.<br />
* If set to 'Rx-Orders' the ACI window will default to the Rx/Orders tab which is best for users that don't use CareGuides or QuickSets.<br />
<br />
Available Options: 'Problem Based', 'Rx-Orders'<br />
Recommended Setting: This depends on the use of CareGuides and QuickSets<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option<br />
<br />
'''Always Present Fax Dialog When Requesting Faxing Requisition'''<br />
* If set to 'Y' the Fax Dialog screen will always present to a user when faxing a requisition.<br />
* If set to 'N' the Fax Dialog screen will only present to a user if they don't have a default defined.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Always Present Print Dialog When Printing Requisition'''<br />
* If set to 'Y' the 'Use Default Order Requisition Printer' option on the Encounter summary will default to unchecked and unless changed, the user will always be presented with the Print Dialog box when printing an Order Requisition.<br />
* If set to 'N' the 'Use Default Order Requisition Printer' option on the Encounter summary will default to checked and unless changed, the user will only be presented with the Print Dialog box when printing an Order Requisition if they do not have defaults defined.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Days before Scheduled Order Children To Be Done Date to Create Them'''<br />
* This is a numeric value that represents the number of days before a scheduled order is created. This is based on the "To Be Done Date" defined on the scheduled order. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 6<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Hold Orders for ABN'''<br />
* If set to 'Y' and order will be put in an 'On Hold' status until the ABN requirements are fulfilled.<br />
* If set to 'N' the order will not be put on an 'On Hold' status due to ABN requirements.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Minutes Before Re-Authentication Is Required for Non-Medication Order'''<br />
* This is a numeric value that represents the number of minutes before a user must enter their password to authenticate when ordering a non-medication order. <br />
<br />
Available Options: Numeric or Blank Values<br />
Value of "0" means that the users will be prompted every time to enter their password<br />
Value of "blank" means that the user will never be prompted to enter their password<br />
Recommended Setting: 0<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Non-Medication Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task will be created for the Ordering Physician if the user entering the order does not have the required ordering authority to order the item. This task must be completed before the order will be sent or fulfilled.<br />
* If set to 'Retrospective' and Order Notification task will be created for the Ordering Physician if the user entering the order does not have the required ordering authority to order the item. This task is informational only and does not prevent the order from being sent or fulfilled.<br />
* If set to 'Not Required' no tasks will be created.<br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Not Required' - this should be based on your organizational policies<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Order Medical Necessity Turned On'''<br />
* If set to 'Y' Medical Necessity checking will be enabled.<br />
* If set to 'N' Medical Necessity checking will be disabled.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Order Authorization level''' - this setting is not used, leave blank.<br />
<br />
'''Enable Order Authorization'''<br />
* If set to 'Y' Order Authorization tasks will be created if an orderable item is defined to require prospective authorization.<br />
* If set to 'N' orders will not require authorization.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Enable Order notification'''<br />
* If set to 'Y' order notification tasks will be created if an orderable item is defined to require retrospective authorization.<br />
* If set to 'N' orders notification tasks will not be created.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Order Notification Level'''<br />
* This is a numeric value that defines the Order level that a notification task should be created for. This number must be 1-10 and the system will create Order Notification tasks for any order that has a higher level than the value defined here if an Order is defined as requiring retrospective authorization.<br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: Leave blank<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Ordering Medications if Patient has Unverified Allergies'''<br />
* If set to 'Prevent' the system will require that the user verify unverified allergies before they can complete or save the order.<br />
* If set to 'Warn' the system will notify the user that a patient has unverified allergies, but will not prevent them from ordering the medication.<br />
* If set to 'Do Not Warn' the system will not notify the user if the patient has unverified allergies.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Do Not Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Ordering Medications if Patient has Unverified Medications'''<br />
* If set to 'Prevent' the system will require that the user verify unverified medications before they can complete or save the order.<br />
* If set to 'Warn' the system will notify the user that a patient has unverified medications, but will not prevent them from ordering the medication.<br />
* If set to 'Do Not Warn' the system will not notify the user if the patient has unverified medications.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Do Not Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Order Problem Linking Required'''<br />
* If set to 'Required to Save' the user must select a problem on the order detail screen before they are allowed to save the order. <br />
* If set to 'Needs Info Reason' the user will not be required to select a problem on the order detail screen, but the order will go to a 'Needs Info' status and must be completed before the order can be sent. <br />
* If set to 'Not Required' a user will not be required to select a problem when completing an order. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Editing Order Updates Supervised by Field'''<br />
* If set to 'Y' the supervised field will be updated to the current user when updating an order.<br />
* If set to 'N' the supervised field will remain unless manually changed by the user. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Chargeable Order Problem Linkage to Billable ICD-9 Interrupt timing'''<br />
* If set to 'Immediate' the system will immediately warn and require the user to select an appropriate billable ICD9 code if the 'Chargeable Requires Billable ICD9' setting is on.<br />
* If set to 'Deferred' the system will warn and require the user to select an appropriate billable ICD9 code if the 'Chargeable Requires Billable ICD9' setting is on when they attempt to commit the patient data.<br />
* If set to 'Never' and the 'Chargeable Requires Billable ICD9' setting is off, the user will not be prompted.<br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Problem Linkage Interrupt Timing'''<br />
* If set to 'Immediate' and problem linking is required, the system will prompt the user to select a problem upon entering the order.<br />
* If set to 'Deferred' and problem linking is required, the system will prompt the user to select a problem upon selecting the commit button.<br />
* If set to 'Never' and problem linking is not required, the user will not be prompted. <br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Performing Location Problem Linkage to Billable ICD9 Required Interrupt Timing'''<br />
* If set to 'Immediate' and problem linking is required for the performing location, the system will prompt the user to select a problem upon entering the order.<br />
* If set to 'Deferred' and problem linking is required for the performing location, the system will prompt the user to select a problem upon selecting the commit button.<br />
* If set to 'Never' and problem linking is not required for the performing location, the user will not be prompted. <br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Require Re-Authentication For New or Renewed Orders'''<br />
* If set to 'Y' the user will be prompted to enter their password if they have not authenticated within the timeframe specified for the 'Minutes Before Re-Authentication Is Required for Non-Medication Order' setting.<br />
* If set to 'N' the user will not be required to enter their password for new or renewed orders. This setting does not apply to medications.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Unspecified Billing Provider Matching''' Added in v11.1.7<br />
* It can be set to Order Only or Exact Match. If set to order Only, the system behaves as it is currently. If set to exact match, the billing provider derived from the order must match exactly to the encounter on which the charges are generated. So if set to Exact match – if the ordering provider and billing provider don’t match it won’t drop the charges to that encounter.<br />
<br />
Available Options: 'Order Only' or 'Exact Match'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
==Problem Preferences==<br />
'''Enable Problem Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' problems will be set to an unverified status when entered by a non-provider user. This information would need to be verified by a provider prior to becoming part of the patient chart.<br />
* If set to 'N' problems will not get set to an unverified status.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Problem resolved date equals today'''<br />
* If set to 'Y' the resolved date will default to today when resolving a problem.<br />
* If set to 'N' the resolved date will not default and must be manually entered if desired.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Problem Include in PMH'''<br />
* If set to 'Unchecked' the 'Include in PMHx' option will not be selected by default on the problem detail screen.<br />
* If set to 'Checked for All' the 'Include in PMHx' option will always be selected by default on the problem detail screen.<br />
* If set to 'Checked for Chronic Only' the 'Include in PMHx' option will only be selected by default on the problem detail screen if the problem is classified as a chronic problem.<br />
<br />
Available Options: 'Unchecked', 'Checked for All', 'Checked for Chronic Only'<br />
Recommended Setting: 'Unchecked'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Problem List Review''' - this is currently unused, leave blank.<br />
<br />
'''Problem Post to Encounter'''<br />
* If set to 'Y' the problem will post to the encounter form when assessed. <br />
* If set to 'N' the problem will not post to the encounter form when assessed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Show unverified problems in the ALL view only'''<br />
* If set to 'Y' unverified problems will only appear in the All Problem view. <br />
* If set to 'N' unverified problems will appear in their respective categories.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''When No Linked V code for PMH''' Added in v11.1.7<br />
<br />
Available Options: 'Show ICD-9 for active problem' or 'Show no ICD-9'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No<br />
<br />
==Results Preferences==<br />
'''Abnormal Result Flag OverrideAllowed'''<br />
* If set to 'Y' users will have the ability to override the abnormal flag sent from a vendor on the results detail screen. <br />
* If set to 'N' users will not have the ability to override the abnormal flag sent from a vendor. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Vitals - <10 years old'''<br />
* This is a free text field that defined the default vitals panel used for children under 10 years old. This value must be equal to the exact name of the vital sign picklist and is case sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by deault and should be explained during training.<br />
<br />
'''Default Vitals - 3 year old and younger'''<br />
* This is a free text field that defined the default vitals panel used for children 3 years old and younger. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Default Vitals - Female 10 years old or older'''<br />
* This is a free text field that defined the default vitals panel used for female patients 10 years old and older. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group and gender.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Default Vitals - Male 10 years old or older'''<br />
* This is a free text field that defined the default vitals panel used for male patients 10 years old and older. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group and gender.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Disable QVerify All and Verify All''' Added in v11.1.7<br />
* If set to 'Y' this will disable the use of Qverify All and Verify All<br />
* If set to 'N' this will enable the use of Qverify All and Verify All<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Hide Grid Header from Result Display in Worklist''' Added in v11.1.7<br />
Determines if the grid header is hidden or not from the result display in the Worklist.<br />
* If set to 'Y' this will hide the grid header from the display in the Worklist<br />
* If set to 'N' this will not hide the grid header from the display in the Worklist<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: Optional<br />
<br />
'''HMP Vitals Units'''<br />
* If set to 'US' the vitals flowsheet on the Health Management Screen will display in US units.<br />
* If set to 'Metric' the vitals flowsheet on the Health Management Screen will display in Metric units.<br />
* If set to 'As Entered' the vitals flowsheet on the Health Management Screen will display in the units that the vitals were entered as.<br />
<br />
Available Options: 'US', 'Metric', 'As Entered'<br />
Recommended Setting: 'US'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Number of Days of Results to include in Clinical Exchange Document'''<br />
* This is a numeric value that determines the number of days in the past that the Clinical Exchange Document will obtain results when created. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 3<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off by default.<br />
<br />
'''Number of Days of Vital Signs to include in Clinical Exchange Document'''<br />
* This is a numeric value that determines the number of days in the past that the Clinical Exchange Document will obtain vitals data when created. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 3<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off by default.<br />
<br />
'''Result Verification Append Staff Message to Staff Comment''' Added in v11.1.7<br />
Determines the default value for Append Staff Message to Task Comment checkbox.<br />
* When set to 'Y' the system checks the Copy Message to Staff to the Task Comment checkbox by default. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Result Verification Disable To/CC Button''' Added in v11.1.7<br />
Determines if the To/CC button is disabled on the Results Verification page. <br />
* If set to 'Y' this will disable the To/CC Button on the Results Verification page<br />
* If set to 'N' this will enable the To/CC Button on the Results Verification page<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Result Verification If Did Not Order'''<br />
Determines system response when the user that is verifying the result is not the ordering provider.<br />
* If set to 'Prevent' a provider will not be allowed to verify results that they did not order.<br />
* If set to 'Warn' a provider will be notified that they are attempting to verify results that they did not order.<br />
* If set to 'Do Not Warn' a provider will not get notified if attempting to verify results that they did not order.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Navigation After QVerify'''<br />
Determines the navigation path after the user clicks QVerify or QVerify All<br />
* If set to 'Go To Note' the provider will be brought to the Note when selecting QVerify during the results verification process.<br />
* If set to 'Go To Next Patient' the provider will remain in the patient worklist screen and the next patient with worklist items defined in their current view will be brought into context.<br />
* If set to 'Stay on Worklist' the provider will remain in the worklist on the current patient. <br />
<br />
Available Options: 'Go To Note', 'Go To Next Patient', 'Stay on Worklist'<br />
Recommended Setting: Depends on desired workflow, set the best default and train users to select their preference.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Note Type for QVerify''' Modified in v11.1.7<br />
* This is a drop down of all available note types in the system. The selection will default as the note type to use when performing a results verification workflow that requires a note. This also defines the note type used for QVerify.<br />
<br />
Available Options: Any note type in the document type dictionary that is valid (v10 or v11 note)<br />
Recommended Setting: Results Verification note type designed for this workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Note Type for Verify''' Added in v11.1.7<br />
* This is a drop down of all available note types in the system. The selection will default as the note type to use when performing a results verification workflow that requires a note. This also defines the note type used for Verify.<br />
<br />
Available Options: Any note type in the document type dictionary that is valid (v10 or v11 note)<br />
Recommended Setting: Results Verification note type designed for this workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Note Use - For QVerify''' Modified in v11.1.7<br />
This preference determines the default note use value for the QVerify action. <br />
* If set to 'Create New Note' the user will default to creating a new note on the results verification screen. This will also define the default behavior when using QVerify.<br />
* If set to 'No Note' the results verification screen will not be set to use a note by default. This would also set the behavior of QVerify.<br />
* If set to 'Select Note' the results verification screen will be setup to use a note, but the user will need to select the note type they want to use.<br />
<br />
Available Options: 'Create New Note', 'No Note', 'Select Note'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Note Use - For Verify''' Added in v11.1.7<br />
This preference determines the default note use value for the QVerify action. <br />
* If set to 'Create New Note' the user will default to creating a new note on the results verification screen. This will also define the default behavior when using Verify.<br />
* If set to 'No Note' the results verification screen will not be set to use a note by default. This would also set the behavior of Verify.<br />
* If set to 'Select Note' the results verification screen will be setup to use a note, but the user will need to select the note type they want to use.<br />
<br />
Available Options: 'Create New Note', 'No Note', 'Select Note'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Patient Communication Methods for QVerify''' Added in v11.1.7<br />
This preference determines the default communication method for QVerify. <br />
* If set to 'Call Patient with Results' the 'Call Pt with Results' option will be selected by default on the Results Verification Screen. This option creates a 'Call Patient with Results' task and requires a note.<br />
* If set to 'Discussed Results With Patient' the 'Discussed results with patient' option is selected by default on the Results Verification Screen. This option does not require a note and it is noted in the Results communication details that this option was selected.<br />
* If set to 'Mail Results to Patient' the 'Mail Results to Patient' option is selected by default on the Results Verification Screen. This requires a note.<br />
* If set to 'No Patient Communication Needed at this Time' the 'No Patient communication needed at this time' option is selected by default. If used, this option is noted in the results communication details within the results details. <br />
* If set to 'Schedule Appointment to Discuss Results' the 'Schedule Results F/U' option is selected by default. This action creates a 'Schedule Results follow up task and does not require a note. <br />
<br />
Available Options: 'Call Patient with Results', 'Discussed Results With Patient', 'Mail Results to Patient', <br />
'No Patient Communication Needed at this Time','Schedule Appointment to Discuss Results'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Patient Communication Methods for Verify''' Added in v11.1.7<br />
This preference determines the default communication method for Verify. <br />
* If set to 'Call Patient with Results' the 'Call Pt with Results' option will be selected by default on the Results Verification Screen. This option creates a 'Call Patient with Results' task and requires a note.<br />
* If set to 'Discussed Results With Patient' the 'Discussed results with patient' option is selected by default on the Results Verification Screen. This option does not require a note and it is noted in the Results communication details that this option was selected.<br />
* If set to 'Mail Results to Patient' the 'Mail Results to Patient' option is selected by default on the Results Verification Screen. This requires a note.<br />
* If set to 'No Patient Communication Needed at this Time' the 'No Patient communication needed at this time' option is selected by default. If used, this option is noted in the results communication details within the results details. <br />
* If set to 'Schedule Appointment to Discuss Results' the 'Schedule Results F/U' option is selected by default. This action creates a 'Schedule Results follow up task and does not require a note. <br />
<br />
Available Options: 'Call Patient with Results', 'Discussed Results With Patient', 'Mail Results to Patient', <br />
'No Patient Communication Needed at this Time', 'Schedule Appointment to Discuss Results'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Task Assignment'''<br />
Determines the default value for the assignment of delegated ResultsVerification tasks. <br />
* If set to 'Current User' the user entering the result will be assigned the Results Verification task.<br />
* If set to 'Ordering Provider' the provider defined as the Ordering Provider will receive the Results Verification Task.<br />
<br />
Available Options: 'Current User'. 'Ordering Provider' <br />
Recommended Setting: 'Ordering Provider'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Required'''<br />
Determines the if results verification is required. <br />
* If set to 'Y' the 'Verification Required' field on the Order Details screen will be selected by default. This specifically pertains to manually entered results. Interfaced results will be set based on the interface definition and is in no way altered with this setting. If a manual result is entered and this option is selected, a Results Verification task will be created and assigned to the user based on the 'Result Verification Task Assignment' setting. <br />
* If set to 'N' the 'Verification Required' field will not be selected by default. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Results Verification Shows Verified Results in Results Document - For QVerify''' Modified in v11.1.7<br />
Determines if the verified results should display on the Results Document for QVerify action. <br />
* If set to 'Y' the 'Show Verified Results in Result Document' option will be selected by default on the Result Verification Screen. Having this option selected automatically posts the verified results to the note created in the verification process.<br />
* If set to 'N' the 'Show verified results in Result Document' option will not be selected by default on the Result Verification screen.<br />
* If set to 'As Per Post to Note Icon' the 'Show verified results in Result Document' option will be selected by default if the users post to note option is on at the time. <br />
<br />
Available Options: 'Y', 'N', 'As Per Post to Note Icon'<br />
Recommended Setting: 'As Per Post to Note Icon'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training.<br />
<br />
'''Results Verification Shows Verified Results in Results Document - For Verify...''' Addedin v11.1.7<br />
Determines if the verified results should display on the Results Document for a Verify action. <br />
* If set to 'Y' the 'Show Verified Results in Result Document' option will be selected by default on the Result Verification Screen. Having this option selected automatically posts the verified results to the note created in the verification process.<br />
* If set to 'N' the 'Show verified results in Result Document' option will not be selected by default on the Result Verification screen.<br />
* If set to 'As Per Post to Note Icon' the 'Show verified results in Result Document' option will be selected by default if the users post to note option is on at the time. <br />
<br />
Available Options: 'Y', 'N', 'As Per Post to Note Icon'<br />
Recommended Setting: 'As Per Post to Note Icon'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training.<br />
<br />
'''Require Abnormal Flag for Results Entry'''<br />
* If set to 'Y' the Abnormal flag will be required for all resultable items with an order. If you have an Order with many resultable items, the user will be required to select an abnormal flag for all values even if those values are not being reported. This applies to manually entered results only. <br />
* If set to 'N' the user will not be required to specify the abnormal flag when manually entering results. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No this is off and enforced.<br />
<br />
'''Use UAI Vital Signs Integration'''<br />
* If set to 'Y' the user will have the ability to capture vital signs using the UAI tool. This requires extra setup and the UAI module. This product allows you to capture and import vitals using a 3rd party device such as a Welch Alyn device.<br />
* If set to 'N' the user will not have the option to capture vital signs using the UAI tool. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No this is off and enforced.<br />
<br />
'''Vitals Picklist'''<br />
* This is a drop down list that defines the default Vitals Picklist to be used. This picklist defines the Vital Sign Views available to the end user.<br />
<br />
Available Options: Drop down list of valid Vital Sign Picklists defined in your OID dictionary.<br />
Recommended Setting: Use the preferred vital signs picklist defined by your organization.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=.NET_Preferences&diff=9387.NET Preferences2010-09-23T18:16:29Z<p>Troy.Forcier: /* Note Preferences */</p>
<hr />
<div>=How to set .NET Preferences=<br />
<br />
In the TWAdmin workspace, navigate to Preferences on the [[VTB]]. From this location you are able to edit preferences at the [[Enterprise]], [[Organizational]] or [[User]] level and determine if users will be able to override certain preferences on the front end.<br />
<br />
:[[Image:Pref_Nav_75_Bold.jpg]]<br />
<br />
==Choosing Preferences Before Test Upgrade==<br />
An Excel workbook is available to record preference decisions before the system is available.<br />
Preferences drive much of the system behavior so it is easier to complete the other build tasks if preferences are set first. Preference decisions often require input from multiple representatives of the clinical staff and can therefore be time consuming. For these two reasons it is sometimes helpful to start this decision process before the test upgrade. The preferences can always be altered after the clinical team sees the test system. The worksheet also provides a record of your settings in the event a Hotfix or staff member changes them. We recommend only one person be allowed to change preferences and that same person maintain the worksheet for change control.<br />
<br />
First review the following articles to understand how each level is set, then review each preference description and record the organization's decisions in the workbook available via download below.<br />
<br />
Pay special attention to article: [[TW .NET Preferences#Setting .NET Preferences at the User Level for Multiple Users via SSMT|Setting .NET Preferences at the User Level for Multiple Users via SSMT]]. This article explains how to use the last column of the workbook.<br />
<br />
This workbook is also useful for organizations who wish to keep track of the preferences independent of the system in case they are altered by accident or for setting up new users.<br />
<br />
[http://wiki.galenhealthcare.com/images/c/c0/TW_.NET_Preferences_Workbook.xls .NET Preferences Workbook]<br />
<br />
==Setting Preferences at an Enterprise or Org Level==<br />
To set preferences for all users in a system, and to establish which preferences users have the ability to personalize (set themselves), the administrator will set these preferences at an Enterprise level.<br />
The ability of users to personalize can only be set at the enterprise level i.e. all users can personalize or no users can personalize. The ability of users to personalize cannot be set at the user level i.e. it is not possible for one user to personalize and another not. <br />
<br />
For this Example we are going to set how a user’s favorites are populated.<br />
<br />
# To set preferences at the Enterprise level, select Enterprise from the Ent/Org/User Settings dropdown.<br />
#:[[Image:Select_Enterprise.jpg]]<br />
# The preferences for populating favorites are located under the preferences category General so select General from the Preferences: dropdown.<br />
#:[[Image:Pref_Nav to General.jpg]]<br />
# Highlight the “Add Favorites Automatically” line <br />
# Click on the cell under the header “Value”<br />
# Setting the value to Y or N. Y = when providers make selections those selections will automatically be added to their favorites list, N = when providers make selections those selections will not automatically be added to their favorites list.<br />
# To allow the user to change this preference, keep the Can Override box checked.<br />
#: [[Image:Set_Add_Fav_75.jpg]]<br />
# Click save in the lower right hand corner of the screen<br />
# Login as a user and test to see if the interface acts as expected<br />
<br />
==Setting .NET Preferences at the User Level via TW Admin > Preferences==<br />
For this Example, the user level preference will be set to display the site selector when a user logs in<br />
<br />
# Select 'User' from the Ent/Org/User dropdown to edit settings at the user level<br />
# Select the organization the user belongs to<br />
# Click the binoculars to seach for the user. The Select a User dialog will open<br />
#:[[Image:LevelReplacement.jpg]]<br />
# Set the search criteria. In this case: UserName - Starting With - Test<br />
# Click binoculars to search<br />
# All users fitting the search criteria will be displayed. Highlight the user to be edited<br />
# Click OK<br />
#:[[Image:UserReplacement.jpg]]<br />
#:<br>The user level preferences will be displayed. Note that the User Can Override column is not available at this level. Only preferences with a value of user can override = Y will be visible.<br />
# Preferences are grouped into categories. Select the preference category from the Preference dropdown. For this example choose the preference category General<br />
# Select the preference row “Always Present Site Selector for User”<br />
# Click on the cell under the header “Value” and select a value from the dropdown. For a description of each preference and what the values will do see [[TW .NET Preferences#TW .NET Preferences|TW .NET Preferences]]<br />
# Click Save in the lower right hand corner of the screen<br />
#:[[Image:PrefReplacement.jpg]]<br />
# Login as a user and test to see if the interface acts as expected<br />
<br />
==Setting .NET Preferences at the User Level for Multiple Users via SSMT==<br />
In some cases an organization may want to set a preference differently for different users within the same organization. In this situation the best practice is to set the preference of the smaller group of users at the user level and leave the larger group of users at the org or enterprise level preference. These instructions use the example of setting the site selector to appear at login for floating nurses but not for anyone else.<br />
# Determine which group of users is smaller and create a list of their usernames. Of all the organization's users the floating nurses are the only users who prefer to have the site selector appear at login so they are the smaller group.<br />
# [[TW .NET Preferences#Setting Preferences at an Enterprise Level|Set the Enterprise or Org level preference]] based on what the majority of users prefers. Most users prefer the site selector not to appear at login so set the Enterprise or Org level preference to N<br />
# Choose a member of the smaller group and [[TW .NET Preferences#Setting .NET Preferences at the User Level via TW Admin > Preferences|set their preference at the user level in TW Admin]]. Test User is a floating nurse and wants the site selector to appear at login so set her user level preference to Y<br />
# Log out and extract the category '''TW .NET Preferences''' using SSMT<br />
# Use Excel to delete all rows except the one with 'Test User' under '''*HDRUserName'''<br />
#:[[Image:Excel1Replacement.jpg]]<br />
# Copy the setting to create as many rows as there are users in the smaller group<br />
#:[[Image:Excel2Replacement.jpg]]<br />
# Replace the '''*HDRUserName''' with the usernames of the smaller group<br />
#:[[Image:Excel3Replacement.jpg]]<br />
# Reload the table<br />
<br />
For more details about the SSMT category '''TW .NET Preferences''' see [[SSMT: TW .NET Preferences]]<br />
<br />
==How a User can set their own Personal Preferences==<br />
A provider can personalize their preferences from the clinical toolbar. For this example we are going to say that this user wants to include active problems in past medical history and automatically post those problems to the encounter summary.<br />
<br />
*Login as a provider<br />
*Navigate to Chart on the vertical toolbar<br />
*Select the arrow on the far right hand side of the Clinical Toolbar<br />
<br />
[[Image:Ppref1.jpg]]<br />
<br />
*From the dropdown menu, select personalize.<br />
<br />
[[Image:Ppref2.jpg]]<br />
<br />
This opens the Personalize dialog box. From here a provider has the ability to change many individualized settings to suit their personal preferences. <br />
<br />
*Navigate to the Problem Tab <br />
*Select “Problem include in PMH” and change the value to “checked for all”<br />
<br />
[[Image:Ppref3.jpg]]<br />
<br />
*select “post problem to encounter” and change the value to Y<br />
*click on Save<br />
<br />
=.NET Preferences=<br />
V11 Preferences can be set in the TWAdmin workplace, by entering the value that corresponds to the Preference.<br />
<br />
'''Categories'''<br />
Preferences are grouped into categories. The categories are General, Meds, Meds/Orders, Note, Orders, Problems and Results. Specific information about each preference is listed below.<br />
<br />
'''Recommended Setting''' - Recommended settings are based on certified workflows and the most common setting. Each of them must be reviewed with your organizations workflows in mind.<br />
<br />
===Clinical Trial Preferences===<br />
'''Works Time Batch Match Starting Time''' Added in v11.1.7<br />
<br />
Indicates the time that the night job runs. The night job reviews the next day's appointment list and compares the patients to the patients to the available clinical trial definitions. <br />
Available Options: 12:00 am; 1:00 am; 2:00 am; 3:00 am; 11:00 pm<br />
Default Value: 12:00 am<br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: N/A<br />
<br />
'''Clinical Trial Maximum Patient Drive Miles''' Added in v11.1.7<br />
<br />
The maximum number of miles the client would have a patient drive to participate in a trial. <br />
Available Options: 5, 10, 25, 50, 100<br />
Default Value: 5<br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: N/A<br />
<br />
==General Preferences==<br />
'''Add Favorites Lists Automatically'''<br />
*When set to 'Y', this preference causes items to get automatically assigned to a users favorites list as they use them. This includes meds, allergies, orders, and problems.<br />
*When set to 'N', items will not be added to a users favorite list unless they manually add it.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Allergy list Review'''<br />
Per Allscripts July, 2008 this preference is currently not used. It does not matter how it is set, but it is best to leave blank and revisited when the preference becomes active.<br />
Recommended Setting: Leave Blank<br />
<br />
'''Allow Advanced Personal Editing of Careguide templates'''<br />
* When set to 'Y' providers have the ability to edit many aspects of CareGuide Templates at a personal level, including adding new orderable items, deleting items, editing headers and rearranging items or headers. <br />
* When set to 'N', the provider has only the ability to save some preferences within the CareGuide Template. They may select their preferred medications, SIGs or labs, but the structure of the CareGuide is based on Enterprise settings.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Always Present Dialog When Printing Rx'''<br />
* When set to 'Y' the "Use Default Rx Printer" option on the commit screen will not be selected and the default behavior will be to show the Print Dialogue box when a medication is committed and activated. This forces the user to review the print dialogue before sending the print request.<br />
* When set to 'N' the "Use Default Rx Printer" option on the commit screen will be selected and the default behavior will be to suppress the Print Dialogue box when a medication is committed and activated. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Always Present Site Selector for User'''<br />
*When set to 'Y' the Site Selector will appear every time a user logs into AE-EHR. This is a great option for floating staff, but can become a nuisance.<br />
*When set to 'N' the Site Selector would only appear if a user hasn't previously set a default. In this case it will default to their default site. The user can change their site in AE-EHR if the menu item has been given to them. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is off by default, but can be allowed.<br />
<br />
'''Audit level''' - Allows administrators to capture and track the following information about users’ activity in the AE-EHR application including: User name, Patient name,Patient MRN, Access date, Access time, Device used (Web, PDA), Action time, Action taken (viewed, printed,created, and/or faxed), WebFramework Page accessed This setting determines the amount of information contained in the Audit Log Report. Please be aware that increasing the level of auditing increases the amount of data that is tracked and stored. Due to the nature of this, it can cause performance issues, so please be sure to test this before implementing in production. This is not seen often, but should be considered. These settings do not change the level of auditing on particular items such as notes. This simply changes what is written to the Audit log report. <br />
* When set to 'High' the audit trail will capture viewing, editing, creating, printing, and faxing of clinical items.<br />
* When set to 'Medium' the audit trail will capture editing, creating, and viewing of clinical items.<br />
* When set to 'Low' the audit trail will capture editing and creating of clinical items. <br />
<br />
Available Options: 'High', 'Medium', 'Low'<br />
Recommended Setting: 'Low' unless your Enterprise requires higher levels of auditing<br />
Can be set on these levels: Enterprise<br />
User Can Override: No, this is off and enforced<br />
<br />
'''CareGuide Default Opening Section''' Added in v11.1.7<br />
<br />
Allows users to choose the default opening section of CareGuides.<br />
* When set to 'All' the display opens all sections of the CareGuide selected<br />
* When set to 'Follow-Ups and Referrals' the display opens to the Follow-Ups and Referrals section of the CareGuide selected<br />
* When set to 'Instructions' the display opens to the Instructions section of the CareGuide selected<br />
* When set to 'Medications' the display opens to the Medications section of the CareGuide selected<br />
* When set to 'Orders' the display opens to the Orders section of the CareGuide selected<br />
<br />
Available Options: All, Follow-Ups and Referrals, Instructions, Medications, Orders<br />
Default Setting: All<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes<br />
<br />
'''Clinical Exchange Documents Verification'''<br />
* When set to 'Y' this will require verification when CED documents are imported. This means that a provider will be tasked with verifying the document before it becomes a true addition to the patient's chart. The task routing is based on the 'Clinical Exchange Documents Verification Routing' preference setting.<br />
* When set to 'N', the CED document would be imported and would not require verification prior to being added to the patient's chart.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Clinical Exchange Documents Verification Routing''' - If you have turned on "Clinical Exchange Document Verification" or "Clinical Exchange Documents Item Verification" this specifies the tasking behavior. <br />
* If set to 'Recipient then PCP then Clinical Exchange Document Team' the system will attempt to assign the task to the defined recipient first, if the system can't make a match or if the recipient isn't defined as a user, it will attempt to assign the task the the PCP defined for the patient. If the PCP isn't defined or is not setup as a AE-EHR user, the task would then be assigned to the Clinical Exchange Document Team. <br />
* If set to 'Recipient then Clinical Exchange Document Team' the system will attempt to assign the task to the defined recipient. IF the system can't make a match or the recipient isn't setup as a user, the task will get assigned to the Clinical Exchange Document Team.<br />
* If set to 'PCP then Clinical Exchange Document Team' the system will attempt to assign the task to the PCP first. If the patient does not have a PCP defined or the PCP is not setup as a user, the system will assign the task to the Clinical Exchange Document Team.<br />
* If set to 'Clinical Exchange Document Team' the task will be assigned to the Clinical Exchange Document Team.<br />
<br />
Available Options: 'Recipient then PCP then Clinical Exchange Document Team', 'Recipient then Clinical Exchange Document Team', <br />
'PCP then Clinical Exchange Document Team', 'Clinical Exchange Document Team' <br />
Recommended Setting: 'Clinical Exchange Document Team'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''ClinEGuide Credentials (User|Pwd)'''<br />
* This is a free text field which would hold your username and password for integration with the [http://www.clineguide.com/marketing/ContentPage.aspx Wolters Kluwer Clin-Eguide]. If a value is provided, an icon will apear on the v11 toolbar that looks like an open book. if a user selects the book, it will launch an Internet Explorer session which brings the user to the Clin-eguide home page. The credentials are passed with the action and will log them into the site if valid. <br />
<br />
Available Options: Free Text <br />
Recommended Setting: Blank<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Clinical Exchange Documents Item Verification'''<br />
* When set to 'Y' this will require verificaiton when CED items (meds, allergies, problems, etc.) are imported. This means that a provider will be tasked with verifying the clinical items before it becomes a true addition to the patient's chart. The task routing is based on the 'Clinical Exchange Documents Verification Routing' preference setting.<br />
* When set to 'N', the CED items would be imported and would not require verification prior to being added to the patient's chart.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Create Future Encounter''' Added in v11.1.7<br />
Allows the creation of future encounters<br />
* When set to 'Y' this will allow users to create documentation on a future encounter<br />
* When set to 'N' this will not allow users to create documentation on a future encounter<br />
<br />
Available Options: 'Y' or 'N'<br />
Defaulted Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Days Before Instruction Expiration Date To Consider Near Due'''<br />
* This Value is a number representing number of days. This tells the system when incomplete instructions should show as near due on the patient's chart. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Days Before Scheduled Order Expiration Date to Consider Near Due'''<br />
* This Value is a number representing number of days. This tells the system when incomplete or scheduled Orders should show as near due on the patient's chart. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Entering For Provider ID'''<br />
* This value specifies the default provider ID that should default into fields such as the Ordering Provider on medications or Orders within the system. This is primarily used for non-provider users that support a specific physician. For example, if an MA always works for Dr. Smith, they would want to set this within their personalize options so it would pre-populate and default properly. This is typically a setting that should be shown to users during training.<br />
<br />
Available Options: Any entry in the Provider Dictionary<br />
Recommended Setting: Blank Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default Specialty ID'''<br />
* This value specifies a non-provider's default specialty. This is best used as a personal setting from within the UI and should be shown to end users during training. This setting will default the specialty for a user in certain areas of the product that are driven by specialty such as the note selector, ACI specialty favorites, and flowsheets. Providers usually have their specialty specified in the provider dictionary and do not need to utilize this preference. <br />
<br />
Available Options: Any entry in the Specialty Dictionary<br />
Recommended Setting: Caution -Blank for user/providers (adverse affect of their favorites if not left blank),<br />
Users can populate as needed, but the recommended setign is still "Blank"<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default Supervising Provider ID'''<br />
* This value specifies the default supervising physician for users that require supervision with Orders. This should be shown during training and is best when set on a personal level. <br />
<br />
Available Options: Any entry in the Provider Dictionary<br />
Recommended Setting: Blank<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default to QuickList Favorites'''<br />
*When set to 'Y', this preference causes items to get automatically assigned to a users QuickList as they use them. This includes meds, allergies, orders, and problems.<br />
*When set to 'N', items will not be added to a users QuickList unless they manually add it.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Dictionary Cache'''<br />
* This setting is looking for a numeric value, but should be left alone. This is a development setting and is not intended to be used unless instructed otherwise. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: Do not change<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Dictionary Edit Max Count'''<br />
* This setting should be a value between 100 and 1000. This determines how many rows will be visible in a dictionary grid before the dictionary automatically goes into search mode.<br />
<br />
Available Options: Numeric Value between 100 and 1000<br />
Recommended Setting: 1000<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''DirectivesEditable'''<br />
* If set to 'Y' the Patient Directives on the Patient Profile Dialog or "i" screen will be editable. This would be set to 'Y' if you want users to document patient directives in the UI.<br />
* If set to 'N' the Patient Directives on the Patient Profile Dialog or "i" screen will be viewable only. This would be set to 'N' if you do not want users to document or edit this or if this value is populated through the registration interface. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Display <R> in Patient Banner for Restricted Documents''' Added in v11.1.7<br />
* If set to 'Y' the system will display the <R> in the patient banner when they have a restricted document. <br />
* If set to 'N' the system will not display the <R> in the patient banner when they have a restricted document. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise,Organization<br />
User Can Override: N/A <br />
<br />
'''Display Future Encounters in selector X days in the future'''<br />
* This is a numeric value which specifies how far in the future pending appointments are shown in the encounter selector. In most workflows, users will be working on an arrived appointment for the current day. If there are workflows that require people to prepare for a future appointment and begin documenting on encounters before the arrival occurs, this setting would allow those encounters to display and be selectable. It is advised that this be set to 1 to avoid any issues if the scheduling interface was to go down. If appointments can't be arrived in the system due to interface issue, this would allow end users the ability to complete their work on pending appointments until the issues are resolved. <br />
<br />
Available Options: Numeric Value between 0-99<br />
Recommended Setting: 1<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''DisplayPatientPicture'''<br />
* If set to 'Y', this would display the patient picture on the Patient Profile Page or "i" screen. This also allows the ability to upload pictures. <br />
* If set to 'N', this would hide the patient picture on the Patient Profile Page or "i" screen and would disable the ability to upload pictures.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Double Click Action'''<br />
* If set to "View" this would specify that double-clicking an item from the clinical desktop would open it in view mode.<br />
* If set to "Edit" this would specify that double-clicking an item from the clinical desktop would open it in edit mode.<br />
<br />
Available Options: 'View' or 'Edit'<br />
Recommended Setting: 'View'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Due Date or Start Date for Newly Added Bulk Enrollment'''<br />
* Bulk Enrollment is currently not available. Leave this as is for now.<br />
<br />
<br />
'''Enable Allergy Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' the system would generate verification tasks for providers when allergies are entered by non-provider users. In this setting a newly entered allergy will remain in a unverified mode until verified by a provider. This is important for JCAHO accreditation. <br />
* If set to 'N' the system will add allergies to the patient's allergy list in a completed status without verification from a provider.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Enable E-Prescribe G Code Alert''' Added in v11.1.7<br />
For 2009, to be a "successful e-prescriber", a provider must report the e-prescribing quality measure through their Medicare Part B claims on at least 50% of applicable cases during the reporting year. <br />
<br />
* If set to 'Y' a reminder will be added to the Encounter Summary for all Medicare patients that an e-Prescribing G-Code may be appropriate for this encounter. This is a reminder to the facility that they need to manually add the G-Code to their Encounter Form. This ensures all prescriptions should count towards the qualifications necessary to be seen as a "successful e-prescriber."<br />
* If set to 'N' no reminder will appear.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Enable MSHV''' Added in v11.1.7<br />
Determines whether or not the HealthVault specific settings should be available on the patient profile dialog. <br />
* If set to 'Y' the Health specific settings shodul display on the patient profile dialog and allow for a patient to be linked to their HealthVault account. <br />
* If set to 'N' then patient accounts cannot be linked to HealthVault.<br />
Note: Enterprise EHR usres should also not have the ability to import or export CEDs from MS HealthVault if this preference is set to N<br />
<br />
Available Options: 'Y' or 'N'<br />
Default Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Encounter Selection from Worklist'''<br />
* When set to 'Encounter Selector'<br />
* When set to 'Create New Encounter'<br />
<br />
Available Options: 'Encounter Selector' or 'Create New Encounter'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Summary Always Print Medication Profile''' Added in v11.1.7<br />
Encounter Summary: Always print medication profile<br />
* <br />
<br />
Available Options: 'Y' or 'N'<br />
Default Seting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Type for Worklist'''<br />
This preference previously only applied to results. Effective in v11.1.7, this preference is applied to all work done on Worklist. The intent is to reduce the instances when a use is presented with an encounter selector without increasing the number of times work done during an appointment is documented against a non-appointment encounter.<br />
<br />
Available Options: Active entries in the Encounter Type dictionary<br />
Recommended Setting: Chart Update<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Summary Default View'''<br />
* When set to 'Type' the encounter summary or commit screen will default to display items grouped by type (orders, problems, etc.)<br />
* When set to 'Problem' the encounter summary or commit screen will default to display items grouped by their associated problem. <br />
<br />
Available Options: 'Type' or 'Problem'<br />
Recommended Setting: 'Problem'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Encounter Summary Password Required on Save'''<br />
* If set to 'Y' the user must enter their password when saving the Encounter Summary <br />
* If set to 'N' the user does not need to enter their password when saving the encounter summary.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Encounter Summary Review Before Save'''<br />
*If set to 'Y', the encounter summary will appear when a user hits the commit button or leaves the patient's chart. This acts as a review process prior to committing the data. <br />
* If set to 'N', the Encounter Summary will not appear when a user hits the commit button or leaves the patient's chart. This will commit the data without the chance to review it. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is selected by default and should be shown in training<br />
<br />
'''Enterprise Emergency Telephone Number'''<br />
* This is a free text value designed to house the emergency telephone number for an Enterprise. This is displayed when printing patient instructions. <br />
<br />
Available Options: Free Text<br />
Recommended Setting: '911'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Fax Maximum Pages''' Added in v11.1.7<br />
Maximum number of pages (estimated)allowed in a chart fax<br />
* This is a numeric field<br />
<br />
Available Options: Free Text Numeric Field<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Fax Warning Type''' Added in v11.1.7<br />
Determines the type of warning users receive when exceeding the maximum number of pages to be faxed.<br />
<br />
Available Options: Block Fax, Disabled, Warn User<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''LanguageEditable'''<br />
* When set to 'Y', this allows users to edit the patient language on the Patient Profile Dialog or "i" screen. This allows users to specify the patient's primary language within AE-EHR.<br />
* When set to 'N', this will only allow users to view the patient's primary language on the Patient Profile Dialog or "i" screen. This is usually the preferred setting when this value is populated by the registration interface or if an organization prefers not to capture this information.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Mask SSN in Reports, Patient Search, & Patient Profile'''<br />
* When set to 'Y', this will hide the Social Security Number in the standard delivered reports, the patient search screen and the patient profile or "i" screen.<br />
* When set to 'N', this will allow users to see the Social Security Number in the standard delivered reports, the patient search screen and the patient profile or "i" screen.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Max # of Providers for All Provider View'''<br />
* This is a numeric value between 0-99. This specifies the maximum number of providers a user can add to the All Provider view. This is defined on the Daily Schedule within the personalize options. The recommendation is 20 and any more than that should be tested prior to implementing. This could introduce a performance issue or become unusable if too many schedules are merged together. <br />
<br />
Available Options: Numeric Value between 0-99<br />
Recommended Setting: 20<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Maximum Number of Seconds to allow for Worklist Load'''<br />
* This is a numeric value that represents the maximum number of seconds that the WorkList is allowed to consume before timing out. This setting is put into place to prevent any long term lock ups for a WorkList view that are improperly defined and potentially hindering system performance. In most cases, if the view is defined properly, this setting should have no merit. <br />
<br />
<br />
Available Options: Numeric Value <br />
Recommended Setting: 30<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Minimum # of Hours to Keep Patient Site Location and Encounter Status'''<br />
* This is a numeric value that establishes the length of time that the patient location and encounter status will be stored. This timeframe is based on the last update of either of the fields. For example, if this is set to 1 hour, this information would be cleared 1 hour after the last update to the patient location or encounter status. This is cleared out to ensure it is reset for the patients next visit. <br />
<br />
Available Options: Numeric value between 1-99<br />
Recommended Value: 2<br />
Available on these levels: Enterprise, Organization<br />
User Can Override? No, This is off and enforced<br />
<br />
'''Normative Growth Chart in Units'''<br />
* If set to ‘Us Units’ the Normative Growth chart will be displayed using US Units.<br />
* If set to ‘Metric Units’ the Normative Growth Chart will be displayed using Metric Units.<br />
<br />
Available Options: ‘Us Units’, ‘Metric Units’<br />
Recommended Value: ‘Us Units’<br />
Available on these levels: Enterprise, Organization, User<br />
User Can Override? Yes, This is on by default and should be shown during training. <br />
<br />
'''Authentication Time-Out'''<br />
* This is a numeric value that determines the number of minutes before the system requires authentication since the last time they authenticated. The system can be configured to ask for passwords when signing notes, prescribing medications, or committing the encounter summary. If a user has entered their password within the allowed timeframe defined by the setting, the user will not be required to enter their password. Once the time period has passed, the user will need to enter their password to verify their access. Setting this to 0 means that a user will need to enter their password once and their authentication session will not expire again during the session. <br />
Available Options: Numeric value from 0 – 99<br />
Recommended Setting: 5<br />
Available on these levels: Enterprise, Organization<br />
User can override? No, this is off an enforced<br />
<br />
'''Patient Tracking-Use Patient Encounter Status'''<br />
* If set to 'Y', this will enable this drop down and the values available for the assigned site will apear in the drop down for an arrived patient. <br />
* If set to 'N', the drop down box on the patient toolbar will be disabled, but still visible. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Patient Tracking-Use Patient Site Location'''<br />
* If set to 'Y', this will enable this drop down and the values available for the assigned site will appear in the drop down for an arrived patient. <br />
* If set to 'N', the drop down box on the patient toolbar will be disabled, but still visible. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Previously Discontinued Patient'''<br />
* If set to 'Immediate' the user will be prompted with a warning if an order being added has been discontinued for that patient in the past. <br />
* If set to 'Never' the user will not be warned of this condition.<br />
<br />
Available Options: 'Immediate' or 'Never' <br />
Recommended Setting: 'Never' <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Print Patient Education'''<br />
* If set to 'Always' the indicator on the encounter summary screen will be selected and printed anytime patient edcuation is available whether it is part of a CareGuide or custom education materials added by the client. This setting can be overridden on the encounter summary if the user doesn't want them for a specific encounter.<br />
* If set to 'CareGuide Only', the indicator on the encounter summary screen will be selected and printed anytime patient education is available if included with the CareGuide. This setting can be overridden on the Encounter Summary if the user doesn't want them for a specific encounter.<br />
<br />
Available Options: 'Always' or 'CareGuide Only'<br />
Recommended Setting: 'Always' <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option, but not selected by default<br />
<br />
'''Provider Selection limited to Favorites'''<br />
* If set to 'Y' the user or provider is limited to selecting a provider from their favorites list in the drop down. The search field will be hidden and they are prevented from selecting other providers. This is typically only used in a multi-org situation when it is not viable for users to see the entire list of providers. <br />
* If set to 'N' the user or provider has the ability to do a lookup against the entire provider dictionary. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Toolbar Default for Clinician Choice Button''' Added in v11.1.7<br />
Default for Clinical Choice Button to direct user to a specific tab in ACI<br />
<br />
Available Options: 'Active', 'Past Medical History', 'Past Surgical History', 'Family History', 'Social History'<br />
'Allergies', 'Medication History', 'Immunization History', 'Chief Complaint', 'Rx'<br />
'Medication Administration', 'Lab/Procedures', 'Imaging', 'Follow Up/Referral', 'Instructions'<br />
'Immunizations', 'Supplies', 'CareGuides', or 'QSets'<br />
Default Setting: 'Chief Complaint'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for History Builder Button''' Added in v11.1.7<br />
Default for History Builder Button to direct user to a specific History Builder tab in ACI<br />
<br />
Available Options: 'Active', 'Past Medical History', 'Past Surgical History', 'Family History', 'Social History'<br />
'Allergies', 'Medication History', 'Immunization History', or 'Chief Complaint'<br />
Default Setting: 'Active'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for Problem-Based Order Button''' Added in v11.1.7<br />
Default for Problem-Based Order Button to direct user to a specific Problem-Based Order tab in ACI<br />
<br />
Available Options: 'CareGuide' or 'QSets'<br />
Default Setting: 'QSets'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
<br />
'''Toolbar Default for Rx/Orders Button - Lab Icon''' Added in v11.1.7<br />
Default for Rx/Orders Button - Lab Icon to direct user to a specific Rx/Orders tab in ACI<br />
<br />
Available Options: 'Lab/Procedures', 'Imaging', 'Follow Up/Referral', 'Instructions'<br />
'Immunizations', or 'Supplies'<br />
Default Setting: 'Lab/Procedures'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for Rx/Orders Button - Rx Icon''' Added in v11.1.7<br />
Default for Rx/Orders Button - Rx Icon to direct user to a specific Rx/Orders tab in ACI<br />
<br />
Available Options: 'Rx' or 'Medication Administration'<br />
Default Setting: 'Rx'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''UA Install Location''' This preference is no longer used. <br />
<br />
'''Use Clinical Desktop Default View When Switching Patients''' Added in v11.1.7<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Use Organization or Site Address for Patient Ed Print Out''' Added in v11.1.7<br />
Determines which address to display on the patient education print out. <br />
<br />
Available Options: 'Site' or 'Organization'<br />
Default Setting: 'Organization'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''URL to find the UAI DesktopAgent install (optional)'''<br />
* This setting is to be used by clients using the UAI application only. If this is to be used, the technical resource installing the UAI tool would provide the appropriate setting for this field. <br />
<br />
Available Options: Free Text - provided by technical representative<br />
Recommended Setting: Blank unless using UAI<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Works 0 FingerPrintAuthEnc'''<br />
* This is disabled and not used at this time. Do not modify. <br />
<br />
'''Workspace view for tasks that navigate to worklist'''<br />
* This setting determines the default clinical desktop view to use when working an worklist related item from the task list. When a worklist task is double-clicked from the task list, it will navigate the user to the clinical desktop and use the defined view. This should be set to a Clinical Desktop View that is designed to efficiently complete worklist items. <br />
<br />
Available Options: Drop down list of available clinical desktop views<br />
Recommended Setting: Worklist view designed to efficiently complete worklist items<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this should be explained in training.<br />
<br />
==Meds Preferences==<br />
'''Apply to All checkbox on the Print Dialog presented for Prescriptions'''<br />
* If set to 'Y' the 'apply to all' checkbox will be selected by default on the Prescription Print Dialog.<br />
* If set to 'N' the 'apply to all' check box will not be selected by default on the Prescription Print Dialog.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Auto Dispense Inventory Medications''' Added in v11.1.7<br />
Set prescribe action to dispense for in-inventory medications<br />
<br />
Available Options: 'Y' or 'N'<br />
Default Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Days Before RxAction Date To Consider Near Due'''<br />
* This is a numeric value between 0-99. This represents the number of days prior to a Prescription Action being due to consider it near due and a reminder is created. <br />
<br />
Available Options: Numeric value between 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Rx Action for a renewal from'''<br />
* If set to 'previous action' the renewed prescription will default to the Rx action used during for the original version of the prescription.<br />
* If set to 'User Default' the renewed prescription will default to the users default Rx action. <br />
<br />
Available Options: 'previous action', 'user default'<br />
Recommended Setting: 'previous action'<br />
Can be set on these levels: Enterprise, Organization, user<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Default Rx Action'''<br />
* If set to 'Call Rx' the Rx action will default to Call Rx.<br />
* If set to 'Dispense Sample', the Rx action will default to Dispense sample.<br />
* If set to 'Print Rx' the Rx action will default to Print Rx.<br />
* If set to 'Record' the Rx action will default to Record.<br />
* If set to 'Send To Mail Order' the Rx action will default to Send To Mail Order.<br />
* If set to 'Send to Retail' the Rx action will default to Send to Retail.<br />
<br />
Available Options: 'CallRx', 'Dispense Sample', 'Print Rx', 'Record', 'Send To Mail Order', 'Send to Retail'<br />
Recommended Setting: 'Send to Retail'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Default Admin By'''<br />
* If set to 'Y' the Default Admin By for a Medication Administration and Immunizations will default based on the previously used value. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin By for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
<br />
'''Default Admin Date'''<br />
* If set to 'Y' the Default Admin Date for a Medication Administration and Immunizations will default based on the previously used value. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Date for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Dose'''<br />
* If set to 'Y' the Default Admin Dose for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Dose for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Lot'''<br />
* If set to 'Y' the Default Admin Lot for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Lot for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Manufacturer'''<br />
* If set to 'Y' the Default Admin Manufacturer for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Manufacturer for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Route'''<br />
* If set to 'Y' the Default Admin Route for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Route for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Site'''<br />
* If set to 'Y' the Default Admin Site for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Site for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Disp Save Default'''<br />
* If set to 'Y', this defaults the 'save as default for selected SIG' option to be selected on the medication screen. If this information is saved, the next time a provider selects that SIG, the Days, Quantity, Units, Refill, and DAW option will fill in based on the previously saved values. <br />
* If set to 'N', the 'save as default for selected SIG' will not be selected by default, but the provider can select this option if they prefer to save a default from time to time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
<br />
'''DUR Acknowledge Reason''' <br />
* If set to 'Y' the user must provide a reason when ignoring a DUR Warning. <br />
* If set to 'N' the user will not be required to provide a reason for ignoring the warning. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Dose Check Interrupt Timing''' <br />
* If set to 'Immediate' the user will be prompted with a dose check DUR warning immediately after selecting the medication. For this setting to work, the Enterprise DUR settings for dosage must also be on.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Alcohol Check Interrupt Timing''' [DUR Preferences are no longer set per severity levels. They can only be set to "Immediate" or "Never".]<br />
* If set to 'Immediate' the user will be prompted with an alcohol check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Alcohol screening must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Drug Check Interrupt Timing''' [DUR Preferences are no longer set per severity levels. They can only be set to "Immediate'or Never".]<br />
<br />
* If set to 'Immediate' the user will be prompted with a drug-drug check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Drug-Drug interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Food Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a food check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for food screening interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning.<br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Healthstate Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Drug-Health State check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Drug-Health State interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Duplicate Therapy Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Duplicate Therapy DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Duplicate Therapy interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning.<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise''' <br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Immunization - Expiration Date''' Added in v11.1.7<br />
Determines whether or not an expiration date is required to complete an immunization administration. <br />
* If set to 'Y' this will require the user to enter an expiration date<br />
* If set to 'N' this will not require the user to enter an expiration date<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Lot Required''' Added in v11.1.7<br />
Determines whether or not a lot is required to complete an immunization administration.<br />
* If set to 'Y' this will require the user to enter a lot number<br />
* If set to 'N' this will not require the user to enter a lot number<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Manufacturer''' Added in v11.1.7<br />
Determines whether or not a manufacturer is required to complete an immunization administration.<br />
* If set to 'Y' this will require the user to enter a manufacturer number<br />
* If set to 'N' this will not require the user to enter a manufacturer number<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - NDC''' Added in v11.1.7<br />
Determines whether or not an NDC number is required to complete an immunization administration. If Chargeable, is required only when value is configured in Charge Code field in OID.<br />
* If set to 'Y'<br />
* If set to 'N'<br />
* If set to 'Chargeable'<br />
<br />
Available Options: 'Y', 'N' or 'Chargeable'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Requiredness''' Added in v11.1.7<br />
Required field behavior.<br />
* If set to Required to Complete<br />
* If set to Required to Save<br />
<br />
Available Options: 'Required to Complete' or 'Required to Save'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Expiration Date ''' Added in v11.1.7<br />
Determines whether or not an expiration date is required to complete a medication administration. <br />
* If set to 'Y' an expiration date is required to complete a medication administration<br />
* If set to 'N' an expiration date is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Lot Required ''' Added in v11.1.7<br />
Determines whether or not a lot is required to complete a medication administration. <br />
* If set to 'Y' a lot is required to complete a medication administration<br />
* If set to 'N' a lot is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Manufacturer''' Added in v11.1.7<br />
Determines whether or not a manufacturer is required to complete a medication administration. <br />
* If set to 'Y' a manufacturer is required to complete a medication administration<br />
* If set to 'N' a manufacturer is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A <br />
<br />
'''Med Admin - NDC''' Added in v11.1.7<br />
Determines whether or not an NDC number is required to complete an medication administration. If Chargeable, is required only when value is configured in Charge Code field in OID.<br />
* If set to 'Y'<br />
* If set to 'N'<br />
* If set to 'Chargeable'<br />
<br />
Available Options: 'Y', 'N' or 'Chargeable'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Requiredness''' Added in v11.1.7<br />
Required field behavior.<br />
* If set to Required to Complete<br />
* If set to Required to Save<br />
<br />
Available Options: 'Required to Complete' or 'Required to Save'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''PAR Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Prior Adverse Reaction (PAR) warning immediately after selecting the medication. For this to work the Enterprise settings for PAR interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable Rx Hub Medication History'''<br />
* If set to 'Y' the application will allow patient history to be loaded from Rx Hub. This requires that the patient's medication benefits information is added to the application and a match can be made with the Rx Hub Warehouse. If these items are both true, a patients historical medications will be loaded into the system. <br />
* If set to 'N' the system will not attempt to load the patient's historical medications. <br />
* New in v11.1.6 and newer this can be disabled for individual patients to meet HIPPA -see [[Med History Patient Disable]] <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable SCRIPT Messaging'''<br />
* If set to 'Y' then Script messaging is enabled between the physician and the pharmacies using the SureScripts network. This requires other setup as well, but must be enabled for physicians or systems that have been setup and want to use this type of messaging. When turned on, the system will determine if the pharmacy is a script enabled pharmacy and determine if a script should be sent electronically or as a fax. This occurs when the Rx Action is Send to Retail. Inbound Script messages will appear as New Prescription Request (NEWRX), Renewal Request (REFREQ), and Renewal Response (REFRES) messages.<br />
* If set to 'N' Script messaging will be disabled. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N', unless setup for SureScripts usage<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Enable Touchscript Messaging'''<br />
* If 'Y' is selected then organizations can send in-office medication requests from TouchWorks to TouchScripts. This would be used if you are using the FirstFill product which is a part of TouchScripts. If you are interested in this product you would contact your account manager.<br />
* If set to 'N' this feature will be disabled.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N', unless setup for FirstFill usage<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Formulary Alternatives Reason Required'''<br />
* If set to 'off formulary with preferred' the user would be required to enter a reason for prescribing a specific medication when the medication is off formulary and there are preferred medications available. <br />
* If set to 'preferred' the user would be required to enter a reason for prescribing a specific medication when the medication has preferred alternatives available.<br />
* If set to 'never' the user would not be forced to provide a reason for ignoring formulary alternatives. <br />
<br />
Available Options: 'off formulary with preferred', 'preferred', 'never'<br />
Recommended Setting: 'never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Formulary Checking Interrupt Timing'''<br />
* If set to 'Immediate' the user would be prompted with formulary checking alternatives as they are prescribing the medication. <br />
* If set to 'Deferred' the user would be prompted with formulary checking alternatives as they are committing the encounter summary information.<br />
* If set to 'Never' the user would not receive the warning.<br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Immunization Order Authorization Required'''<br />
* If set to 'Prospective' a task will be created for a user/provider that does not have the appropriate medication prescribing levels. The task must be authorized by the ordering provider before the request can be fulfilled.<br />
* If set to 'Retrospective' a task will be created for the ordering provider for auditing purposes only. The immunization can still be fulfilled at the time of entry, but the audit task will be created for review. <br />
* If set to 'Not Required' no tasks will be created and the immunization will be completed at the time of entry and completion. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Not Required'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
*Special Note - If a user has the 'Med Order Protocol' Security code assigned to them, they do have the ability to override the Prospective authorization setting. This allows for users to choose "Per Protocol" or "Per Verbal Order" on the Immunization Detail screen and allows for clinics to continue these workflows. This would change the setting to Retrospective in this case and the provider would receive an audit task. <br />
<br />
'''MAR Prescription BarCode'''<br />
* If set to 'AHS RX Number' the bar code printed on the MAR prescription will use the Allscripts Rx Number. <br />
* If set to 'NDC' the bar code printed will have the National Drug Code. <br />
* If set tp 'GPI' the bar code printed will use the Gingival-Periodontal Index code. <br />
<br />
Available Options: 'AHS Rx Number', 'NDC', 'GPI'<br />
Recommended Setting: Leave this setting alone. This is only used with the MAR product which most clinics do not use. <br />
For the few clients that do use this module, this setting would be based on their needs.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Med History Query Duration'''<br />
* Available in 11.1.6 and newer only!<br />
* Allows for a specific amount of time (in months) for retrieval of patients medication history from Rx Hub<br />
* Configurable from one month to 24 months.<br />
Available Options: Numeric from 1 to 24<br />
Default Setting: is 6 (months)<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Minutes Before Re-Authentication Is Required For Medication Order'''<br />
* This preference is enacted when the setting for '''Order Authentication Required''' is set to yes. If order authentication is required, this value is the number of minutes before a user is required to reauthenticate within the system. If this setting is set to 0, the system will only ask for a password once during a session when ordering a med. If set to 5, the user will need to reauthenticate if they have not completed an action that required authentication within the past 5 minutes. This setting does not apply to the login screen.<br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: '0'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Non-Scheduled Meds Order Authorization Required'''<br />
* If set to 'Prospective' a task will be created for a user/provider that does not have the appropriate medication prescribing levels. The task must be authorized by the ordering provider before the request can be fulfilled.<br />
* If set to 'Retrospective' a task will be created for the ordering provider for auditing purposes only. The medication request can still be fulfilled at the time of entry, but the audit task will be created for review. <br />
* If set to 'Not Required' no tasks will be created and the medication request will be completed at the time of entry and completion. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Prospective'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
*Special Note - If a user has the 'Med Order Protocol' Security code assigned to them, they do have the ability to override the Prospective authorization setting. This allows for users to choose "Per Protocol" or "Per Verbal Order" on the Medication Detail screen and allows for clinics to continue these workflows. This would change the setting to Retrospective in this case and the provider would receive an audit task. <br />
<br />
'''OrderPresentForumlaryAlternatives'''<br />
* If set to 'off formulary with preferred' the user would be presented with formulary alternatives when the medication is off formulary and there are preferred medications available. <br />
* If set to 'preferred' the user would be presented with formulary alternatives when the medication has preferred alternatives available.<br />
* If set to 'never' the user would not be presented with formulary alternatives. <br />
<br />
Available Options: 'off formulary with preferred', 'preferred', 'never'<br />
Recommended Setting: 'off formulary with preferred'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on and should be described during training<br />
<br />
<br />
'''Prohibit Transmission of Schedule III Rx'''<br />
* If set to 'Y' the transmission of Schedule III drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule III drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule II Rx'''<br />
* If set to 'Y' the transmission of Schedule II drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule II drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule IV Rx'''<br />
* If set to 'Y' the transmission of Schedule IV drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule IV drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule V Rx'''<br />
* If set to 'Y' the transmission of Schedule V drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule V drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Override Sign Rx Task for Schedule II Meds'''<br />
* This setting is not used and should be left blank.<br />
<br />
'''Override Sign RX Task for Schedule III-V Meds (Override Sign Rx CIII-V)'''<br />
* This setting is not used and should be left blank.<br />
-------------------------------------------------------------------------------------------------------------<br />
'''Enable Medication Administration Schedule''' - Need to verify this. This preference goes along with the MAR system.<br />
<br />
* If set to 'Y' the ability to schedule a medication administration is available.<br />
* If set to 'N' the ability to schedule a medication administration is not available.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
-------------------------------------------------------------------------------------------------------------<br />
'''Non-Formulary Authorization Required'''<br />
* If set to 'Y' the medication will require authorization prior to fulfillment if prescribing off formulary and will not print without authorization.<br />
* If set to 'N' the system will not require authorization if prescribed medications are off formulary<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribe Print Problem'''<br />
* If set to 'Y' the problem tied to the medication will be printed on the prescription.<br />
* If set to 'N' the problem tied to the medication will not display on prescriptions.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Sites'''<br />
* If set to 'Y' the Site will display on the prescription<br />
* If set to 'N' the Site will not display on the prescription<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Sites name/address on the printed scheduled prescription'''<br />
* If set to 'Y' the Site name and address will display on the controlled prescription<br />
* If set to 'N' the Site name and address will not display on the controlled prescription<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Prescribe Problem Linking Required'''<br />
* If set to 'Required to Save", the prescription details screen will require a user to select a linked problem prior to saving the prescription. <br />
* If set to 'Needs Info Reason', the user does not have to select a problem on the medication detail screen, but the medication will go to a needs info status and create a "Rx Info - Problem" task. This task will need to be worked and completed before the medication can be fulfilled.<br />
* If set to 'Not Required' the system will not force the user to select a problem when prescribing or renewing a medication.<br />
<br />
Available Options: 'Required to save', 'needs info reason', 'not required'<br />
Recommended Setting: 'Required to save' - this helps build quicksets<br />
Can be set on these levels: Enterprise, Organization, user<br />
User Can Override: Yes this is an option<br />
<br />
'''Editing Rx updates Ordered By Field'''<br />
* If set to 'Y' the Ordered by field will update to the current user renewing a medication if they are a valid ordering provider. This can be a good feature when physicians are covering for others and the desired behavior is to have the actual prescribing doctor documented as the Ordering Physician.<br />
* If set to 'N' the original Ordering Provider will remain unless manually overridden. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Warn if a medication is not participating in checking'''<br />
* If set to 'Y' the user will be prompted when prescribing a medication that does not participate in DUR checking. This is usually the case with user defined medications.<br />
* If set to 'N' the user will not be prompted when prescribing a medication that does not participate in DUR checking.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show Allscripts watermark on Faxed Prescriptions'''<br />
* If set to 'Hide' the Allscripts watermark will not appear on faxed prescriptions.<br />
* If set to 'Show' the Allscripts watermark will appear on faxed prescriptions.<br />
<br />
Available Options: 'Show' or 'Hide'<br />
Recommended Setting: 'Show'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Allscripts watermark on Printed prescriptions'''<br />
* If set to 'Hide' the Allscripts watermark will not appear on printed prescriptions.<br />
* If set to 'Show' the Allscripts watermark will appear on printed prescriptions.<br />
<br />
Available Options: 'Show' or 'Hide'<br />
Recommended Setting: 'Show'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribing without Allergy Status'''<br />
* If set to 'Prevent' the user will be prompted when a patient's allergy status is not set. This will require them to define a patient's allergy status prior to completing a medication request. <br />
* If set to 'Warn' the user will receive a warning message stating the patient has an unknown allergy status when they are not defined for a patient. This occurs when selecting a medication from the ACI. <br />
* If set to 'Do Not Warn' the user will not receive a warning when prescribing medications.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a non-controlled medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a non-controlled medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a non-controlled medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required for Schedule II Meds'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a schedule II medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a schedule II medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a schedule II medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required for Schedule III-V Meds'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a schedule III-V medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a schedule III-V medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a schedule III-V medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribing without Pharmacy Specified'''<br />
* If set to 'Prevent' the user will be prompted when a patient's pharmacy is not set. This will require them to define a pharmacy prior to completing a medication request. <br />
* If set to 'Warn' the user will receive a warning message stating the patient has no pharmacy when they are not defined for a patient. This occurs when selecting a medication from the ACI. <br />
* If set to 'Do Not Warn' the user will not receive a warning when prescribing medications and a pharmacy is not defined.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Require Re-Authentication For New or Renewed Prescriptions'''<br />
* If set to 'Y' the physician or user will be prompted to enter their password when prescribing or renewing a medication. This behavior is also dependant on the 'Authentication Time-Out' in the general preferences.<br />
* If set to 'N' the physician or user will not be prompted to enter their password.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Disable faxing of Class 2,3,4,5 Scheduled Meds'''<br />
* If set to '2' the system will not allow faxing of schedule II medications<br />
* If set to '2,3' the system will not allow faxing of schedule II or III medications<br />
* If set to '2,3,4' the system will not allow faxing of schedule II, III or IV medications<br />
* If set to '2,3,4,5' the system will not allow faxing of controlled medications<br />
* If set to 'Always' the system will not allow faxing of medications<br />
* If set to '' all medication levels will fax<br />
<br />
Available Options: '2', '2,3', '2,3,4', '2,3,4,5', 'Always', ''<br />
Recommended Setting: '2' - this is the typical state requirement. <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Disable Printing of Class 2,3,4,5 Scheduled Meds'''<br />
* If set to '2' the system will not allow printing of schedule II medications<br />
* If set to '2,3' the system will not allow printing of schedule II or III medications<br />
* If set to '2,3,4' the system will not allow printing of schedule II, III or IV medications<br />
* If set to '2,3,4,5' the system will not allow printing of controlled medications<br />
* If set to 'Always' the system will not allow printing of medications<br />
* If set to '' all medication levels will print<br />
<br />
Available Options: '2', '2,3', '2,3,4', '2,3,4,5', 'Always', ''<br />
Recommended Setting: '' <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''RxWeb List Limit'''<br />
* This is a numeric value that limits the number of medications returned in a search. This can be limited if searching is causing slow responses, but typically this is left blank.<br />
<br />
Available Options: Numeric value between 0-99<br />
Recommended Setting: leave blank (unlimited)<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option<br />
<br />
<br />
'''Samples - Expiration Date Required'''<br />
* If set to 'Y' the Expiration Date would be a required field when dispensing samples.<br />
* If set to 'N' the Expiration Date would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Lot Required'''<br />
* If set to 'Y' the Lot Number would be a required field when dispensing samples.<br />
* If set to 'N' the Lot Number would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Manufacturer required'''<br />
* If set to 'Y' the Manufacturer would be a required field when dispensing samples.<br />
* If set to 'N' the Manufacturer would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Quantity Required'''<br />
* If set to 'Y' the Quantity would be a required field when dispensing samples.<br />
* If set to 'N' the Quantity would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Quantity Units Required'''<br />
* If set to 'Y' the Quantity Units would be a required field when dispensing samples.<br />
* If set to 'N' the Quantity Units would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Schedule III to V Meds Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task would be created if a level III to V medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and the medication would not be fulfilled until the provider authorizes the task.<br />
* If set to 'Retrospective' a Order Notification task would be created if a level III to V medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and serves as an audit trail. The medication would be fulfilled immediately and does not require this task to be worked first. <br />
* If set to 'Not Required' no tasks will be created if a level III to V medication is prescribed by a user without proper license information. That medication would be fulfilled immediately. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required' <br />
Recommended Setting: 'Prospective' - this should be based on your organizations policy<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Schedule II Meds Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task would be created if a level II medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and the medication would not be fulfilled until the provider authorizes the task.<br />
* If set to 'Retrospective' a Order Notification task would be created if a level II medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and serves as an audit trail. The medication would be fulfilled immediately and does not require this task to be worked first. <br />
* If set to 'Not Required' no tasks will be created if a level II medication is prescribed by a user without proper license information. That medication would be fulfilled immediately. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required' <br />
Recommended Setting: 'Prospective' - this should be based on your organizations policy<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
==Meds/Orders Preferences==<br />
'''Duplicate Checking Order Interval (Hrs)'''<br />
* This Value is a number representing number of hours. This tells the system how many hours in the past it should look for a duplicate order. If a duplicate is found within the specified timeframe, the user will receive a message with that information, which allows them to determine if another test is needed or not. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 48<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable Rx-Orders Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' this will require verification when non-provider users enter med or order history. This means that a provider will be tasked with verifying the clinical items before it becomes a true addition to the patient's chart. A Task would be created for the Ordering physician to verify.<br />
* If set to 'N', the med or order entries would not require verification prior to being added to the patient's chart when added by a non-provider user.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Med/Orders List Review''' - Leave blank, this is currently unused.<br />
<br />
'''Monitor Order Selection'''<br />
* If set to 'Y' the system will track how users are selecting orders. This will determine if the user used their favorites, QuickSets or CareGuides. This can be used to review workflows. This information is stored in the database, but would require a special script to retrieve the data.<br />
* If set to 'N', they will not track how orders are selected.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Cancel Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Cancel reason if they choose to cancel an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Cancel reason, but it is not required to continue.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Cancel reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Chargeable Requires Billable ICD-9'''<br />
* If set to 'Required to Save' the system will require that the problem is tied to a billable Problem with an appropriate ICD9 code when the Orderable item is defined as chargeable. This will need to be selected before the user can save the Order.<br />
* If set to 'Needs Info Reason' the system will allow a user to save an Order with a CPT code, but it would go to a needs info status until someone associates an appropriate billable problem to the Order. <br />
* If set to 'Not Required' the system will not require a chargeable order be tied to an appropriate billable problem. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''CPT Requires Billable ICD9'''<br />
* If set to 'Required to Save' the system will require that the problem is tied to a billable Problem with an appropriate ICD9 code when the Orderable item has an associated CPT code. This will need to be selected before the user can save the Order.<br />
* If set to 'Needs Info Reason' the system will allow a user to save an Order with a CPT code, but it would go to a needs info status until someone associates an appropriate billable problem to the Order. <br />
* If set to 'Not Required' the system will not require a chargeable order be tied to an approapriate billable problem. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Discontinue Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Discontinue reason if they choose to discontinue an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Discontinue reason, but it is not required to discontinue.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Discontinue reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''OderDeferReason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Defer reason if they choose to defer an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Defer reason, but it is not required to defer.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Defer reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Entered in Error Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Entered in Error reason if they choose to mark an order as entered in error. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Entered in Error reason, but it is not required to mark an order as entered in error. <br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Entered in Error reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''OrderPermanentDeferReason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Permanent Defer reason if they choose to permanently defer an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Permanent Defer reason, but it is not required to permanently defer.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Permanent Defer reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Void Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Void reason if they choose to void an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Void reason, but it is not required to void an order.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Void reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Create Overdue Tasks for'''<br />
* If set to 'All Overdue' the system will create Overdue order tasks assigned to the ordering provider for all orders that are considered overdue. <br />
* If set to 'Overdue Important' the system will create overdue order tasks assigned to the ordering provider if the ordering provider selected the "Overdue Important" setting on the Order Details screen. <br />
<br />
Available Options: 'All Overdue', 'Overdue Important'<br />
Recommended Setting: 'Overdue Important'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
==Note Preferences==<br />
<br />
'''Document Add Review Stamp''' Add in v11.1.7<br />
Add review stamp when a document review task is completed. <br />
* When set to 'Y' a review stamp displaying the reviewing provider's name, date & time will display on the document reviewed.<br />
* When set to 'N' no review stamp will display<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes<br />
<br />
'''Note Auto Unlock Notes After Time'''<br />
* This is a numeric value that represents hours. This will tell the system how many hours should occur before the system automatically unlocks v11 note. A note remains locked when a user is editing a note and at times this can be left open accidentally or an issue may have occurred that didn't properly close the note. This preference only applies to v11 note. This preference prevents notes from being locked when there is no AE-EHR session open. <br />
<br />
<br />
<br />
Available Options: Numeric value<br />
Recommended Setting: 24<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Make Final'''<br />
* Allows the System Administrator to configure a default state for the Make Final option on the Note Signature page to accommodate the provider’s most common workflow for signing documents and the need to finalize.<br />
* If set to 'Y' the 'Make Final' checkbox will default to being selected when a user or provider that has the appropriate signature levels. <br />
* If set to 'N' the 'Make Final' checkbox will default to not being selected.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Navigation After Signing'''<br />
<br />
* Determines to which page the system navigates after the user signs a note.<br />
* If set to 'No Navigation' the user or provider will not be taken off of the note upon signing. <br />
* If set to 'Schedule' the user or provider will be brought to the Daily Schedule screen upon signing the note.<br />
* If set to 'Task View' the user or provider will be brought to the Task List screen upon signing the note.<br />
* If set to 'MD Charges' the user or provider will be brought to the Charge screen upon signing the note.<br />
<br />
Available Options: 'No Navigation', 'Schedule', 'Task View', 'MD Charges'<br />
Recommended Setting: 'No Navigation' - this really should be set on a user level based on their desired workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Note Default Owner'''<br />
* Determines the default owner for Notes.<br />
* If set to 'Use Appointment Encounter Provider if available, else use Most Recently Used' the system will default the note owner as the Appointment Provider. If there is no encounter provider available it will default to the most recently used provider.<br />
* If set to 'Always use Most recently used note owner' the system will default the note owner to the last provider used for that user. This is a preferred method when the user primarily works from an ancillary schedule such as a Lab Schedule and the encounter provider is not an actual human.<br />
* If set to 'None' the note owner will not default and will need to be selected each time a new note is created.<br />
<br />
Available Options: 'Use Appointment Encounter Provider if available, else use MRU', 'Always use MRU note owner', 'None'<br />
Recommended Setting: 'Use Appointment Encounter Provider if available, else use MRU'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Signature Display'''<br />
<br />
* This setting defines the format of the signature when signing a note. The available formats are:<br />
<br />
# Firstname Lastname, Credentials; Date/Time (Signature Type) <br />
# Firstname Lastname, Credentials; User/Profession Date/Time (Signature Type) <br />
# Firstname Lastname, Date/Time (Signature Type) <br />
# Firstname Lastname, User/Profession Date/Time (Signature Type)<br />
<br />
Recommended Setting: 'Firstname Lastname, Date/Time (Signature Type)'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Signature Type'''<br />
* This is a drop down menu that lists all available options from the Signature Type dictionary. The option selected will be defaulted into the Sign Note dialog box.<br />
<br />
Available Options: All active entries from the Signature Type dictionary<br />
Recommended Setting: Leave Blank and train the user to set the appropriate default.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Visit Type'''<br />
* Allows users to default to the previously used Visit Type.<br />
* If set to 'None' the visit type will not have a default value on the v11 note selector screen.<br />
* If set to 'Last' the visit type will default to the last visit type selected in the v11 note selector screen.<br />
<br />
Available Options: 'None', 'Last'<br />
Recommended Setting: 'Last'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Don't Generate Document Appt Encounter Tasks'''<br />
* If set to 'Y' the system will not generate Document Appointment Encounter Tasks.<br />
* If set to 'N' the system will generate Document Appointment Encounter Tasks. This task would serve as a reminder for the appointment encounter provider to create a note for the patients visit. The task will automatically be removed once a note is created. Most organizations use the note icon display on the schedule as the reminder or confirmation that all notes were created and choose not to use this option.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Don't Generate Review Covered Note Tasks'''<br />
* If set to 'Y' the system will not generate Review Covered Note Tasks.<br />
* If set to 'N' the system will generate Review Covered Note Tasks. This task would apply when a physician is covering for another doctor and signs off on a note for them. This setting also depends on the 'Create Review Covered Note Task on Finalization' setting in the [[Document Type]] dictionary. Both settings must be set properly to activate the task workflow.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Note Lock Lists After Number Days'''<br />
<br />
* This is a numeric value that defines how many days until all lists within a note are locked. This includes lists such as Problems, Vitals, Immunizations, and Medications. This only applies to notes that have not been finalized. Once a note is finalized or this time limit has been reached, the lists will not update automatically.<br />
<br />
<br />
Available Options: Numeric value<br />
Recommended Setting: 7<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Is V10 Note User Only'''<br />
* If set to 'Y' the user or provider will only be able to create v10 notes. The v10 note selector will be presented to the user.<br />
* If set to 'N' the user or provider will be presented with the v11 note selector and have the ability to select either version of notes available to them. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: This should be set based on the organizations preference to use v11 note<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''CC or RFV Required for E&M Code''' - need further details to explain.<br />
* If set to 'Y' the E&M coder will require the CC or RFV be set.<br />
* If set to 'N' the E&M coder will not require these values. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''E/M Coder default to MDM tab'''<br />
* If set to 'Y' the E/M coder will default to the Medical Decision Making tab instead of the Summary tab.<br />
* If set to 'N' the E/M coder will default to the Summary tab.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''Post Text to Current Note'''<br />
* If set to 'Y' the default will be for the "post text to current note" option to be on. This will tell the system that the users actions should be posted to a note. There is a toggle button on the Clinical toolbar that can change this behavior easily during certain workflows. <br />
* If set to 'N' the default will be for the "post text to current note" option to be off. There is a toggle button on the Clinical toolbar that can change this behavior easily during certain workflows. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''UseAutoPrintForDefaultTemplate'''<br />
* If set to 'Y' the document will print using the document type specific document template and override the users preferred setting. This can be useful if certain types of document require specific document templates. <br />
* If set to 'N' the users auto-print defaults will be used. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
==Orders Preferences==<br />
'''Add Clinical Item Order Selection Method Default'''<br />
* If set to 'Problem Based' the ACI window will default to the problem based tab which is best for users that utilize CareGuide or QuickSets.<br />
* If set to 'Rx-Orders' the ACI window will default to the Rx/Orders tab which is best for users that don't use CareGuides or QuickSets.<br />
<br />
Available Options: 'Problem Based', 'Rx-Orders'<br />
Recommended Setting: This depends on the use of CareGuides and QuickSets<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option<br />
<br />
'''Always Present Fax Dialog When Requesting Faxing Requisition'''<br />
* If set to 'Y' the Fax Dialog screen will always present to a user when faxing a requisition.<br />
* If set to 'N' the Fax Dialog screen will only present to a user if they don't have a default defined.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Always Present Print Dialog When Printing Requisition'''<br />
* If set to 'Y' the 'Use Default Order Requisition Printer' option on the Encounter summary will default to unchecked and unless changed, the user will always be presented with the Print Dialog box when printing an Order Requisition.<br />
* If set to 'N' the 'Use Default Order Requisition Printer' option on the Encounter summary will default to checked and unless changed, the user will only be presented with the Print Dialog box when printing an Order Requisition if they do not have defaults defined.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Days before Scheduled Order Children To Be Done Date to Create Them'''<br />
* This is a numeric value that represents the number of days before a scheduled order is created. This is based on the "To Be Done Date" defined on the scheduled order. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 6<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Hold Orders for ABN'''<br />
* If set to 'Y' and order will be put in an 'On Hold' status until the ABN requirements are fulfilled.<br />
* If set to 'N' the order will not be put on an 'On Hold' status due to ABN requirements.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Minutes Before Re-Authentication Is Required for Non-Medication Order'''<br />
* This is a numeric value that represents the number of minutes before a user must enter their password to authenticate when ordering a non-medication order. <br />
<br />
Available Options: Numeric or Blank Values<br />
Value of "0" means that the users will be prompted every time to enter their password<br />
Value of "blank" means that the user will never be prompted to enter their password<br />
Recommended Setting: 0<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Non-Medication Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task will be created for the Ordering Physician if the user entering the order does not have the required ordering authority to order the item. This task must be completed before the order will be sent or fulfilled.<br />
* If set to 'Retrospective' and Order Notification task will be created for the Ordering Physician if the user entering the order does not have the required ordering authority to order the item. This task is informational only and does not prevent the order from being sent or fulfilled.<br />
* If set to 'Not Required' no tasks will be created.<br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Not Required' - this should be based on your organizational policies<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Order Medical Necessity Turned On'''<br />
* If set to 'Y' Medical Necessity checking will be enabled.<br />
* If set to 'N' Medical Necessity checking will be disabled.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Order Authorization level''' - this setting is not used, leave blank.<br />
<br />
'''Enable Order Authorization'''<br />
* If set to 'Y' Order Authorization tasks will be created if an orderable item is defined to require prospective authorization.<br />
* If set to 'N' orders will not require authorization.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Enable Order notification'''<br />
* If set to 'Y' order notification tasks will be created if an orderable item is defined to require retrospective authorization.<br />
* If set to 'N' orders notification tasks will not be created.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Order Notification Level'''<br />
* This is a numeric value that defines the Order level that a notification task should be created for. This number must be 1-10 and the system will create Order Notification tasks for any order that has a higher level than the value defined here if an Order is defined as requiring retrospective authorization.<br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: Leave blank<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Ordering Medications if Patient has Unverified Allergies'''<br />
* If set to 'Prevent' the system will require that the user verify unverified allergies before they can complete or save the order.<br />
* If set to 'Warn' the system will notify the user that a patient has unverified allergies, but will not prevent them from ordering the medication.<br />
* If set to 'Do Not Warn' the system will not notify the user if the patient has unverified allergies.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Do Not Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Ordering Medications if Patient has Unverified Medications'''<br />
* If set to 'Prevent' the system will require that the user verify unverified medications before they can complete or save the order.<br />
* If set to 'Warn' the system will notify the user that a patient has unverified medications, but will not prevent them from ordering the medication.<br />
* If set to 'Do Not Warn' the system will not notify the user if the patient has unverified medications.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Do Not Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Order Problem Linking Required'''<br />
* If set to 'Required to Save' the user must select a problem on the order detail screen before they are allowed to save the order. <br />
* If set to 'Needs Info Reason' the user will not be required to select a problem on the order detail screen, but the order will go to a 'Needs Info' status and must be completed before the order can be sent. <br />
* If set to 'Not Required' a user will not be required to select a problem when completing an order. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Editing Order Updates Supervised by Field'''<br />
* If set to 'Y' the supervised field will be updated to the current user when updating an order.<br />
* If set to 'N' the supervised field will remain unless manually changed by the user. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Chargeable Order Problem Linkage to Billable ICD-9 Interrupt timing'''<br />
* If set to 'Immediate' the system will immediately warn and require the user to select an appropriate billable ICD9 code if the 'Chargeable Requires Billable ICD9' setting is on.<br />
* If set to 'Deferred' the system will warn and require the user to select an appropriate billable ICD9 code if the 'Chargeable Requires Billable ICD9' setting is on when they attempt to commit the patient data.<br />
* If set to 'Never' and the 'Chargeable Requires Billable ICD9' setting is off, the user will not be prompted.<br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Problem Linkage Interrupt Timing'''<br />
* If set to 'Immediate' and problem linking is required, the system will prompt the user to select a problem upon entering the order.<br />
* If set to 'Deferred' and problem linking is required, the system will prompt the user to select a problem upon selecting the commit button.<br />
* If set to 'Never' and problem linking is not required, the user will not be prompted. <br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Performing Location Problem Linkage to Billable ICD9 Required Interrupt Timing'''<br />
* If set to 'Immediate' and problem linking is required for the performing location, the system will prompt the user to select a problem upon entering the order.<br />
* If set to 'Deferred' and problem linking is required for the performing location, the system will prompt the user to select a problem upon selecting the commit button.<br />
* If set to 'Never' and problem linking is not required for the performing location, the user will not be prompted. <br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Require Re-Authentication For New or Renewed Orders'''<br />
* If set to 'Y' the user will be prompted to enter their password if they have not authenticated within the timeframe specified for the 'Minutes Before Re-Authentication Is Required for Non-Medication Order' setting.<br />
* If set to 'N' the user will not be required to enter their password for new or renewed orders. This setting does not apply to medications.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Unspecified Billing Provider Matching''' Added in v11.1.7<br />
* It can be set to Order Only or Exact Match. If set to order Only, the system behaves as it is currently. If set to exact match, the billing provider derived from the order must match exactly to the encounter on which the charges are generated. So if set to Exact match – if the ordering provider and billing provider don’t match it won’t drop the charges to that encounter.<br />
<br />
Available Options: 'Order Only' or 'Exact Match'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
==Problem Preferences==<br />
'''Enable Problem Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' problems will be set to an unverified status when entered by a non-provider user. This information would need to be verified by a provider prior to becoming part of the patient chart.<br />
* If set to 'N' problems will not get set to an unverified status.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Problem resolved date equals today'''<br />
* If set to 'Y' the resolved date will default to today when resolving a problem.<br />
* If set to 'N' the resolved date will not default and must be manually entered if desired.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Problem Include in PMH'''<br />
* If set to 'Unchecked' the 'Include in PMHx' option will not be selected by default on the problem detail screen.<br />
* If set to 'Checked for All' the 'Include in PMHx' option will always be selected by default on the problem detail screen.<br />
* If set to 'Checked for Chronic Only' the 'Include in PMHx' option will only be selected by default on the problem detail screen if the problem is classified as a chronic problem.<br />
<br />
Available Options: 'Unchecked', 'Checked for All', 'Checked for Chronic Only'<br />
Recommended Setting: 'Unchecked'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Problem List Review''' - this is currently unused, leave blank.<br />
<br />
'''Problem Post to Encounter'''<br />
* If set to 'Y' the problem will post to the encounter form when assessed. <br />
* If set to 'N' the problem will not post to the encounter form when assessed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Show unverified problems in the ALL view only'''<br />
* If set to 'Y' unverified problems will only appear in the All Problem view. <br />
* If set to 'N' unverified problems will appear in their respective categories.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''When No Linked V code for PMH''' Added in v11.1.7<br />
<br />
Available Options: 'Show ICD-9 for active problem' or 'Show no ICD-9'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No<br />
<br />
==Results Preferences==<br />
'''Abnormal Result Flag OverrideAllowed'''<br />
* If set to 'Y' users will have the ability to override the abnormal flag sent from a vendor on the results detail screen. <br />
* If set to 'N' users will not have the ability to override the abnormal flag sent from a vendor. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Vitals - <10 years old'''<br />
* This is a free text field that defined the default vitals panel used for children under 10 years old. This value must be equal to the exact name of the vital sign picklist and is case sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by deault and should be explained during training.<br />
<br />
'''Default Vitals - 3 year old and younger'''<br />
* This is a free text field that defined the default vitals panel used for children 3 years old and younger. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Default Vitals - Female 10 years old or older'''<br />
* This is a free text field that defined the default vitals panel used for female patients 10 years old and older. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group and gender.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Default Vitals - Male 10 years old or older'''<br />
* This is a free text field that defined the default vitals panel used for male patients 10 years old and older. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group and gender.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Disable QVerify All and Verify All''' Added in v11.1.7<br />
* If set to 'Y' this will disable the use of Qverify All and Verify All<br />
* If set to 'N' this will enable the use of Qverify All and Verify All<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Hide Grid Header from Result Display in Worklist''' Added in v11.1.7<br />
Determines if the grid header is hidden or not from the result display in the Worklist.<br />
* If set to 'Y' this will hide the grid header from the display in the Worklist<br />
* If set to 'N' this will not hide the grid header from the display in the Worklist<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: Optional<br />
<br />
'''HMP Vitals Units'''<br />
* If set to 'US' the vitals flowsheet on the Health Management Screen will display in US units.<br />
* If set to 'Metric' the vitals flowsheet on the Health Management Screen will display in Metric units.<br />
* If set to 'As Entered' the vitals flowsheet on the Health Management Screen will display in the units that the vitals were entered as.<br />
<br />
Available Options: 'US', 'Metric', 'As Entered'<br />
Recommended Setting: 'US'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Number of Days of Results to include in Clinical Exchange Document'''<br />
* This is a numeric value that determines the number of days in the past that the Clinical Exchange Document will obtain results when created. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 3<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off by default.<br />
<br />
'''Number of Days of Vital Signs to include in Clinical Exchange Document'''<br />
* This is a numeric value that determines the number of days in the past that the Clinical Exchange Document will obtain vitals data when created. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 3<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off by default.<br />
<br />
'''Result Verification Append Staff Message to Staff Comment''' Added in v11.1.7<br />
Determines the default value for Append Staff Message to Task Comment checkbox.<br />
* When set to 'Y' the system checks the Copy Message to Staff to the Task Comment checkbox by default. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Result Verification Disable To/CC Button''' Added in v11.1.7<br />
Determines if the To/CC button is disabled on the Results Verification page. <br />
* If set to 'Y' this will disable the To/CC Button on the Results Verification page<br />
* If set to 'N' this will enable the To/CC Button on the Results Verification page<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Result Verification If Did Not Order'''<br />
Determines system response when the user that is verifying the result is not the ordering provider.<br />
* If set to 'Prevent' a provider will not be allowed to verify results that they did not order.<br />
* If set to 'Warn' a provider will be notified that they are attempting to verify results that they did not order.<br />
* If set to 'Do Not Warn' a provider will not get notified if attempting to verify results that they did not order.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Navigation After QVerify'''<br />
Determines the navigation path after the user clicks QVerify or QVerify All<br />
* If set to 'Go To Note' the provider will be brought to the Note when selecting QVerify during the results verification process.<br />
* If set to 'Go To Next Patient' the provider will remain in the patient worklist screen and the next patient with worklist items defined in their current view will be brought into context.<br />
* If set to 'Stay on Worklist' the provider will remain in the worklist on the current patient. <br />
<br />
Available Options: 'Go To Note', 'Go To Next Patient', 'Stay on Worklist'<br />
Recommended Setting: Depends on desired workflow, set the best default and train users to select their preference.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Note Type for QVerify''' Modified in v11.1.7<br />
* This is a drop down of all available note types in the system. The selection will default as the note type to use when performing a results verification workflow that requires a note. This also defines the note type used for QVerify.<br />
<br />
Available Options: Any note type in the document type dictionary that is valid (v10 or v11 note)<br />
Recommended Setting: Results Verification note type designed for this workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Note Type for Verify''' Added in v11.1.7<br />
* This is a drop down of all available note types in the system. The selection will default as the note type to use when performing a results verification workflow that requires a note. This also defines the note type used for Verify.<br />
<br />
Available Options: Any note type in the document type dictionary that is valid (v10 or v11 note)<br />
Recommended Setting: Results Verification note type designed for this workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Note Use - For QVerify''' Modified in v11.1.7<br />
This preference determines the default note use value for the QVerify action. <br />
* If set to 'Create New Note' the user will default to creating a new note on the results verification screen. This will also define the default behavior when using QVerify.<br />
* If set to 'No Note' the results verification screen will not be set to use a note by default. This would also set the behavior of QVerify.<br />
* If set to 'Select Note' the results verification screen will be setup to use a note, but the user will need to select the note type they want to use.<br />
<br />
Available Options: 'Create New Note', 'No Note', 'Select Note'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Note Use - For Verify''' Added in v11.1.7<br />
This preference determines the default note use value for the QVerify action. <br />
* If set to 'Create New Note' the user will default to creating a new note on the results verification screen. This will also define the default behavior when using Verify.<br />
* If set to 'No Note' the results verification screen will not be set to use a note by default. This would also set the behavior of Verify.<br />
* If set to 'Select Note' the results verification screen will be setup to use a note, but the user will need to select the note type they want to use.<br />
<br />
Available Options: 'Create New Note', 'No Note', 'Select Note'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Patient Communication Methods for QVerify''' Added in v11.1.7<br />
This preference determines the default communication method for QVerify. <br />
* If set to 'Call Patient with Results' the 'Call Pt with Results' option will be selected by default on the Results Verification Screen. This option creates a 'Call Patient with Results' task and requires a note.<br />
* If set to 'Discussed Results With Patient' the 'Discussed results with patient' option is selected by default on the Results Verification Screen. This option does not require a note and it is noted in the Results communication details that this option was selected.<br />
* If set to 'Mail Results to Patient' the 'Mail Results to Patient' option is selected by default on the Results Verification Screen. This requires a note.<br />
* If set to 'No Patient Communication Needed at this Time' the 'No Patient communication needed at this time' option is selected by default. If used, this option is noted in the results communication details within the results details. <br />
* If set to 'Schedule Appointment to Discuss Results' the 'Schedule Results F/U' option is selected by default. This action creates a 'Schedule Results follow up task and does not require a note. <br />
<br />
Available Options: 'Call Patient with Results', 'Discussed Results With Patient', 'Mail Results to Patient', <br />
'No Patient Communication Needed at this Time','Schedule Appointment to Discuss Results'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Patient Communication Methods for Verify''' Added in v11.1.7<br />
This preference determines the default communication method for Verify. <br />
* If set to 'Call Patient with Results' the 'Call Pt with Results' option will be selected by default on the Results Verification Screen. This option creates a 'Call Patient with Results' task and requires a note.<br />
* If set to 'Discussed Results With Patient' the 'Discussed results with patient' option is selected by default on the Results Verification Screen. This option does not require a note and it is noted in the Results communication details that this option was selected.<br />
* If set to 'Mail Results to Patient' the 'Mail Results to Patient' option is selected by default on the Results Verification Screen. This requires a note.<br />
* If set to 'No Patient Communication Needed at this Time' the 'No Patient communication needed at this time' option is selected by default. If used, this option is noted in the results communication details within the results details. <br />
* If set to 'Schedule Appointment to Discuss Results' the 'Schedule Results F/U' option is selected by default. This action creates a 'Schedule Results follow up task and does not require a note. <br />
<br />
Available Options: 'Call Patient with Results', 'Discussed Results With Patient', 'Mail Results to Patient', <br />
'No Patient Communication Needed at this Time', 'Schedule Appointment to Discuss Results'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Task Assignment'''<br />
Determines the default value for the assignment of delegated ResultsVerification tasks. <br />
* If set to 'Current User' the user entering the result will be assigned the Results Verification task.<br />
* If set to 'Ordering Provider' the provider defined as the Ordering Provider will receive the Results Verification Task.<br />
<br />
Available Options: 'Current User'. 'Ordering Provider' <br />
Recommended Setting: 'Ordering Provider'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Required'''<br />
Determines the if results verification is required. <br />
* If set to 'Y' the 'Verification Required' field on the Order Details screen will be selected by default. This specifically pertains to manually entered results. Interfaced results will be set based on the interface definition and is in no way altered with this setting. If a manual result is entered and this option is selected, a Results Verification task will be created and assigned to the user based on the 'Result Verification Task Assignment' setting. <br />
* If set to 'N' the 'Verification Required' field will not be selected by default. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Results Verification Shows Verified Results in Results Document - For QVerify''' Modified in v11.1.7<br />
Determines if the verified results should display on the Results Document for QVerify action. <br />
* If set to 'Y' the 'Show Verified Results in Result Document' option will be selected by default on the Result Verification Screen. Having this option selected automatically posts the verified results to the note created in the verification process.<br />
* If set to 'N' the 'Show verified results in Result Document' option will not be selected by default on the Result Verification screen.<br />
* If set to 'As Per Post to Note Icon' the 'Show verified results in Result Document' option will be selected by default if the users post to note option is on at the time. <br />
<br />
Available Options: 'Y', 'N', 'As Per Post to Note Icon'<br />
Recommended Setting: 'As Per Post to Note Icon'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training.<br />
<br />
'''Results Verification Shows Verified Results in Results Document - For Verify...''' Addedin v11.1.7<br />
Determines if the verified results should display on the Results Document for a Verify action. <br />
* If set to 'Y' the 'Show Verified Results in Result Document' option will be selected by default on the Result Verification Screen. Having this option selected automatically posts the verified results to the note created in the verification process.<br />
* If set to 'N' the 'Show verified results in Result Document' option will not be selected by default on the Result Verification screen.<br />
* If set to 'As Per Post to Note Icon' the 'Show verified results in Result Document' option will be selected by default if the users post to note option is on at the time. <br />
<br />
Available Options: 'Y', 'N', 'As Per Post to Note Icon'<br />
Recommended Setting: 'As Per Post to Note Icon'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training.<br />
<br />
'''Require Abnormal Flag for Results Entry'''<br />
* If set to 'Y' the Abnormal flag will be required for all resultable items with an order. If you have an Order with many resultable items, the user will be required to select an abnormal flag for all values even if those values are not being reported. This applies to manually entered results only. <br />
* If set to 'N' the user will not be required to specify the abnormal flag when manually entering results. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No this is off and enforced.<br />
<br />
'''Use UAI Vital Signs Integration'''<br />
* If set to 'Y' the user will have the ability to capture vital signs using the UAI tool. This requires extra setup and the UAI module. This product allows you to capture and import vitals using a 3rd party device such as a Welch Alyn device.<br />
* If set to 'N' the user will not have the option to capture vital signs using the UAI tool. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No this is off and enforced.<br />
<br />
'''Vitals Picklist'''<br />
* This is a drop down list that defines the default Vitals Picklist to be used. This picklist defines the Vital Sign Views available to the end user.<br />
<br />
Available Options: Drop down list of valid Vital Sign Picklists defined in your OID dictionary.<br />
Recommended Setting: Use the preferred vital signs picklist defined by your organization.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=.NET_Preferences&diff=9386.NET Preferences2010-09-23T18:15:25Z<p>Troy.Forcier: /* General Preferences */</p>
<hr />
<div>=How to set .NET Preferences=<br />
<br />
In the TWAdmin workspace, navigate to Preferences on the [[VTB]]. From this location you are able to edit preferences at the [[Enterprise]], [[Organizational]] or [[User]] level and determine if users will be able to override certain preferences on the front end.<br />
<br />
:[[Image:Pref_Nav_75_Bold.jpg]]<br />
<br />
==Choosing Preferences Before Test Upgrade==<br />
An Excel workbook is available to record preference decisions before the system is available.<br />
Preferences drive much of the system behavior so it is easier to complete the other build tasks if preferences are set first. Preference decisions often require input from multiple representatives of the clinical staff and can therefore be time consuming. For these two reasons it is sometimes helpful to start this decision process before the test upgrade. The preferences can always be altered after the clinical team sees the test system. The worksheet also provides a record of your settings in the event a Hotfix or staff member changes them. We recommend only one person be allowed to change preferences and that same person maintain the worksheet for change control.<br />
<br />
First review the following articles to understand how each level is set, then review each preference description and record the organization's decisions in the workbook available via download below.<br />
<br />
Pay special attention to article: [[TW .NET Preferences#Setting .NET Preferences at the User Level for Multiple Users via SSMT|Setting .NET Preferences at the User Level for Multiple Users via SSMT]]. This article explains how to use the last column of the workbook.<br />
<br />
This workbook is also useful for organizations who wish to keep track of the preferences independent of the system in case they are altered by accident or for setting up new users.<br />
<br />
[http://wiki.galenhealthcare.com/images/c/c0/TW_.NET_Preferences_Workbook.xls .NET Preferences Workbook]<br />
<br />
==Setting Preferences at an Enterprise or Org Level==<br />
To set preferences for all users in a system, and to establish which preferences users have the ability to personalize (set themselves), the administrator will set these preferences at an Enterprise level.<br />
The ability of users to personalize can only be set at the enterprise level i.e. all users can personalize or no users can personalize. The ability of users to personalize cannot be set at the user level i.e. it is not possible for one user to personalize and another not. <br />
<br />
For this Example we are going to set how a user’s favorites are populated.<br />
<br />
# To set preferences at the Enterprise level, select Enterprise from the Ent/Org/User Settings dropdown.<br />
#:[[Image:Select_Enterprise.jpg]]<br />
# The preferences for populating favorites are located under the preferences category General so select General from the Preferences: dropdown.<br />
#:[[Image:Pref_Nav to General.jpg]]<br />
# Highlight the “Add Favorites Automatically” line <br />
# Click on the cell under the header “Value”<br />
# Setting the value to Y or N. Y = when providers make selections those selections will automatically be added to their favorites list, N = when providers make selections those selections will not automatically be added to their favorites list.<br />
# To allow the user to change this preference, keep the Can Override box checked.<br />
#: [[Image:Set_Add_Fav_75.jpg]]<br />
# Click save in the lower right hand corner of the screen<br />
# Login as a user and test to see if the interface acts as expected<br />
<br />
==Setting .NET Preferences at the User Level via TW Admin > Preferences==<br />
For this Example, the user level preference will be set to display the site selector when a user logs in<br />
<br />
# Select 'User' from the Ent/Org/User dropdown to edit settings at the user level<br />
# Select the organization the user belongs to<br />
# Click the binoculars to seach for the user. The Select a User dialog will open<br />
#:[[Image:LevelReplacement.jpg]]<br />
# Set the search criteria. In this case: UserName - Starting With - Test<br />
# Click binoculars to search<br />
# All users fitting the search criteria will be displayed. Highlight the user to be edited<br />
# Click OK<br />
#:[[Image:UserReplacement.jpg]]<br />
#:<br>The user level preferences will be displayed. Note that the User Can Override column is not available at this level. Only preferences with a value of user can override = Y will be visible.<br />
# Preferences are grouped into categories. Select the preference category from the Preference dropdown. For this example choose the preference category General<br />
# Select the preference row “Always Present Site Selector for User”<br />
# Click on the cell under the header “Value” and select a value from the dropdown. For a description of each preference and what the values will do see [[TW .NET Preferences#TW .NET Preferences|TW .NET Preferences]]<br />
# Click Save in the lower right hand corner of the screen<br />
#:[[Image:PrefReplacement.jpg]]<br />
# Login as a user and test to see if the interface acts as expected<br />
<br />
==Setting .NET Preferences at the User Level for Multiple Users via SSMT==<br />
In some cases an organization may want to set a preference differently for different users within the same organization. In this situation the best practice is to set the preference of the smaller group of users at the user level and leave the larger group of users at the org or enterprise level preference. These instructions use the example of setting the site selector to appear at login for floating nurses but not for anyone else.<br />
# Determine which group of users is smaller and create a list of their usernames. Of all the organization's users the floating nurses are the only users who prefer to have the site selector appear at login so they are the smaller group.<br />
# [[TW .NET Preferences#Setting Preferences at an Enterprise Level|Set the Enterprise or Org level preference]] based on what the majority of users prefers. Most users prefer the site selector not to appear at login so set the Enterprise or Org level preference to N<br />
# Choose a member of the smaller group and [[TW .NET Preferences#Setting .NET Preferences at the User Level via TW Admin > Preferences|set their preference at the user level in TW Admin]]. Test User is a floating nurse and wants the site selector to appear at login so set her user level preference to Y<br />
# Log out and extract the category '''TW .NET Preferences''' using SSMT<br />
# Use Excel to delete all rows except the one with 'Test User' under '''*HDRUserName'''<br />
#:[[Image:Excel1Replacement.jpg]]<br />
# Copy the setting to create as many rows as there are users in the smaller group<br />
#:[[Image:Excel2Replacement.jpg]]<br />
# Replace the '''*HDRUserName''' with the usernames of the smaller group<br />
#:[[Image:Excel3Replacement.jpg]]<br />
# Reload the table<br />
<br />
For more details about the SSMT category '''TW .NET Preferences''' see [[SSMT: TW .NET Preferences]]<br />
<br />
==How a User can set their own Personal Preferences==<br />
A provider can personalize their preferences from the clinical toolbar. For this example we are going to say that this user wants to include active problems in past medical history and automatically post those problems to the encounter summary.<br />
<br />
*Login as a provider<br />
*Navigate to Chart on the vertical toolbar<br />
*Select the arrow on the far right hand side of the Clinical Toolbar<br />
<br />
[[Image:Ppref1.jpg]]<br />
<br />
*From the dropdown menu, select personalize.<br />
<br />
[[Image:Ppref2.jpg]]<br />
<br />
This opens the Personalize dialog box. From here a provider has the ability to change many individualized settings to suit their personal preferences. <br />
<br />
*Navigate to the Problem Tab <br />
*Select “Problem include in PMH” and change the value to “checked for all”<br />
<br />
[[Image:Ppref3.jpg]]<br />
<br />
*select “post problem to encounter” and change the value to Y<br />
*click on Save<br />
<br />
=.NET Preferences=<br />
V11 Preferences can be set in the TWAdmin workplace, by entering the value that corresponds to the Preference.<br />
<br />
'''Categories'''<br />
Preferences are grouped into categories. The categories are General, Meds, Meds/Orders, Note, Orders, Problems and Results. Specific information about each preference is listed below.<br />
<br />
'''Recommended Setting''' - Recommended settings are based on certified workflows and the most common setting. Each of them must be reviewed with your organizations workflows in mind.<br />
<br />
===Clinical Trial Preferences===<br />
'''Works Time Batch Match Starting Time''' Added in v11.1.7<br />
<br />
Indicates the time that the night job runs. The night job reviews the next day's appointment list and compares the patients to the patients to the available clinical trial definitions. <br />
Available Options: 12:00 am; 1:00 am; 2:00 am; 3:00 am; 11:00 pm<br />
Default Value: 12:00 am<br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: N/A<br />
<br />
'''Clinical Trial Maximum Patient Drive Miles''' Added in v11.1.7<br />
<br />
The maximum number of miles the client would have a patient drive to participate in a trial. <br />
Available Options: 5, 10, 25, 50, 100<br />
Default Value: 5<br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: N/A<br />
<br />
==General Preferences==<br />
'''Add Favorites Lists Automatically'''<br />
*When set to 'Y', this preference causes items to get automatically assigned to a users favorites list as they use them. This includes meds, allergies, orders, and problems.<br />
*When set to 'N', items will not be added to a users favorite list unless they manually add it.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Allergy list Review'''<br />
Per Allscripts July, 2008 this preference is currently not used. It does not matter how it is set, but it is best to leave blank and revisited when the preference becomes active.<br />
Recommended Setting: Leave Blank<br />
<br />
'''Allow Advanced Personal Editing of Careguide templates'''<br />
* When set to 'Y' providers have the ability to edit many aspects of CareGuide Templates at a personal level, including adding new orderable items, deleting items, editing headers and rearranging items or headers. <br />
* When set to 'N', the provider has only the ability to save some preferences within the CareGuide Template. They may select their preferred medications, SIGs or labs, but the structure of the CareGuide is based on Enterprise settings.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Always Present Dialog When Printing Rx'''<br />
* When set to 'Y' the "Use Default Rx Printer" option on the commit screen will not be selected and the default behavior will be to show the Print Dialogue box when a medication is committed and activated. This forces the user to review the print dialogue before sending the print request.<br />
* When set to 'N' the "Use Default Rx Printer" option on the commit screen will be selected and the default behavior will be to suppress the Print Dialogue box when a medication is committed and activated. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Always Present Site Selector for User'''<br />
*When set to 'Y' the Site Selector will appear every time a user logs into AE-EHR. This is a great option for floating staff, but can become a nuisance.<br />
*When set to 'N' the Site Selector would only appear if a user hasn't previously set a default. In this case it will default to their default site. The user can change their site in AE-EHR if the menu item has been given to them. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is off by default, but can be allowed.<br />
<br />
'''Audit level''' - Allows administrators to capture and track the following information about users’ activity in the AE-EHR application including: User name, Patient name,Patient MRN, Access date, Access time, Device used (Web, PDA), Action time, Action taken (viewed, printed,created, and/or faxed), WebFramework Page accessed This setting determines the amount of information contained in the Audit Log Report. Please be aware that increasing the level of auditing increases the amount of data that is tracked and stored. Due to the nature of this, it can cause performance issues, so please be sure to test this before implementing in production. This is not seen often, but should be considered. These settings do not change the level of auditing on particular items such as notes. This simply changes what is written to the Audit log report. <br />
* When set to 'High' the audit trail will capture viewing, editing, creating, printing, and faxing of clinical items.<br />
* When set to 'Medium' the audit trail will capture editing, creating, and viewing of clinical items.<br />
* When set to 'Low' the audit trail will capture editing and creating of clinical items. <br />
<br />
Available Options: 'High', 'Medium', 'Low'<br />
Recommended Setting: 'Low' unless your Enterprise requires higher levels of auditing<br />
Can be set on these levels: Enterprise<br />
User Can Override: No, this is off and enforced<br />
<br />
'''CareGuide Default Opening Section''' Added in v11.1.7<br />
<br />
Allows users to choose the default opening section of CareGuides.<br />
* When set to 'All' the display opens all sections of the CareGuide selected<br />
* When set to 'Follow-Ups and Referrals' the display opens to the Follow-Ups and Referrals section of the CareGuide selected<br />
* When set to 'Instructions' the display opens to the Instructions section of the CareGuide selected<br />
* When set to 'Medications' the display opens to the Medications section of the CareGuide selected<br />
* When set to 'Orders' the display opens to the Orders section of the CareGuide selected<br />
<br />
Available Options: All, Follow-Ups and Referrals, Instructions, Medications, Orders<br />
Default Setting: All<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes<br />
<br />
'''Clinical Exchange Documents Verification'''<br />
* When set to 'Y' this will require verification when CED documents are imported. This means that a provider will be tasked with verifying the document before it becomes a true addition to the patient's chart. The task routing is based on the 'Clinical Exchange Documents Verification Routing' preference setting.<br />
* When set to 'N', the CED document would be imported and would not require verification prior to being added to the patient's chart.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Clinical Exchange Documents Verification Routing''' - If you have turned on "Clinical Exchange Document Verification" or "Clinical Exchange Documents Item Verification" this specifies the tasking behavior. <br />
* If set to 'Recipient then PCP then Clinical Exchange Document Team' the system will attempt to assign the task to the defined recipient first, if the system can't make a match or if the recipient isn't defined as a user, it will attempt to assign the task the the PCP defined for the patient. If the PCP isn't defined or is not setup as a AE-EHR user, the task would then be assigned to the Clinical Exchange Document Team. <br />
* If set to 'Recipient then Clinical Exchange Document Team' the system will attempt to assign the task to the defined recipient. IF the system can't make a match or the recipient isn't setup as a user, the task will get assigned to the Clinical Exchange Document Team.<br />
* If set to 'PCP then Clinical Exchange Document Team' the system will attempt to assign the task to the PCP first. If the patient does not have a PCP defined or the PCP is not setup as a user, the system will assign the task to the Clinical Exchange Document Team.<br />
* If set to 'Clinical Exchange Document Team' the task will be assigned to the Clinical Exchange Document Team.<br />
<br />
Available Options: 'Recipient then PCP then Clinical Exchange Document Team', 'Recipient then Clinical Exchange Document Team', <br />
'PCP then Clinical Exchange Document Team', 'Clinical Exchange Document Team' <br />
Recommended Setting: 'Clinical Exchange Document Team'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''ClinEGuide Credentials (User|Pwd)'''<br />
* This is a free text field which would hold your username and password for integration with the [http://www.clineguide.com/marketing/ContentPage.aspx Wolters Kluwer Clin-Eguide]. If a value is provided, an icon will apear on the v11 toolbar that looks like an open book. if a user selects the book, it will launch an Internet Explorer session which brings the user to the Clin-eguide home page. The credentials are passed with the action and will log them into the site if valid. <br />
<br />
Available Options: Free Text <br />
Recommended Setting: Blank<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Clinical Exchange Documents Item Verification'''<br />
* When set to 'Y' this will require verificaiton when CED items (meds, allergies, problems, etc.) are imported. This means that a provider will be tasked with verifying the clinical items before it becomes a true addition to the patient's chart. The task routing is based on the 'Clinical Exchange Documents Verification Routing' preference setting.<br />
* When set to 'N', the CED items would be imported and would not require verification prior to being added to the patient's chart.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Create Future Encounter''' Added in v11.1.7<br />
Allows the creation of future encounters<br />
* When set to 'Y' this will allow users to create documentation on a future encounter<br />
* When set to 'N' this will not allow users to create documentation on a future encounter<br />
<br />
Available Options: 'Y' or 'N'<br />
Defaulted Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Days Before Instruction Expiration Date To Consider Near Due'''<br />
* This Value is a number representing number of days. This tells the system when incomplete instructions should show as near due on the patient's chart. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Days Before Scheduled Order Expiration Date to Consider Near Due'''<br />
* This Value is a number representing number of days. This tells the system when incomplete or scheduled Orders should show as near due on the patient's chart. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Entering For Provider ID'''<br />
* This value specifies the default provider ID that should default into fields such as the Ordering Provider on medications or Orders within the system. This is primarily used for non-provider users that support a specific physician. For example, if an MA always works for Dr. Smith, they would want to set this within their personalize options so it would pre-populate and default properly. This is typically a setting that should be shown to users during training.<br />
<br />
Available Options: Any entry in the Provider Dictionary<br />
Recommended Setting: Blank Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default Specialty ID'''<br />
* This value specifies a non-provider's default specialty. This is best used as a personal setting from within the UI and should be shown to end users during training. This setting will default the specialty for a user in certain areas of the product that are driven by specialty such as the note selector, ACI specialty favorites, and flowsheets. Providers usually have their specialty specified in the provider dictionary and do not need to utilize this preference. <br />
<br />
Available Options: Any entry in the Specialty Dictionary<br />
Recommended Setting: Caution -Blank for user/providers (adverse affect of their favorites if not left blank),<br />
Users can populate as needed, but the recommended setign is still "Blank"<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default Supervising Provider ID'''<br />
* This value specifies the default supervising physician for users that require supervision with Orders. This should be shown during training and is best when set on a personal level. <br />
<br />
Available Options: Any entry in the Provider Dictionary<br />
Recommended Setting: Blank<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default. <br />
<br />
'''Default to QuickList Favorites'''<br />
*When set to 'Y', this preference causes items to get automatically assigned to a users QuickList as they use them. This includes meds, allergies, orders, and problems.<br />
*When set to 'N', items will not be added to a users QuickList unless they manually add it.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: This is on by default<br />
<br />
'''Dictionary Cache'''<br />
* This setting is looking for a numeric value, but should be left alone. This is a development setting and is not intended to be used unless instructed otherwise. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: Do not change<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Dictionary Edit Max Count'''<br />
* This setting should be a value between 100 and 1000. This determines how many rows will be visible in a dictionary grid before the dictionary automatically goes into search mode.<br />
<br />
Available Options: Numeric Value between 100 and 1000<br />
Recommended Setting: 1000<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''DirectivesEditable'''<br />
* If set to 'Y' the Patient Directives on the Patient Profile Dialog or "i" screen will be editable. This would be set to 'Y' if you want users to document patient directives in the UI.<br />
* If set to 'N' the Patient Directives on the Patient Profile Dialog or "i" screen will be viewable only. This would be set to 'N' if you do not want users to document or edit this or if this value is populated through the registration interface. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Display <R> in Patient Banner for Restricted Documents''' Added in v11.1.7<br />
* If set to 'Y' the system will display the <R> in the patient banner when they have a restricted document. <br />
* If set to 'N' the system will not display the <R> in the patient banner when they have a restricted document. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise,Organization<br />
User Can Override: N/A <br />
<br />
'''Display Future Encounters in selector X days in the future'''<br />
* This is a numeric value which specifies how far in the future pending appointments are shown in the encounter selector. In most workflows, users will be working on an arrived appointment for the current day. If there are workflows that require people to prepare for a future appointment and begin documenting on encounters before the arrival occurs, this setting would allow those encounters to display and be selectable. It is advised that this be set to 1 to avoid any issues if the scheduling interface was to go down. If appointments can't be arrived in the system due to interface issue, this would allow end users the ability to complete their work on pending appointments until the issues are resolved. <br />
<br />
Available Options: Numeric Value between 0-99<br />
Recommended Setting: 1<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''DisplayPatientPicture'''<br />
* If set to 'Y', this would display the patient picture on the Patient Profile Page or "i" screen. This also allows the ability to upload pictures. <br />
* If set to 'N', this would hide the patient picture on the Patient Profile Page or "i" screen and would disable the ability to upload pictures.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Double Click Action'''<br />
* If set to "View" this would specify that double-clicking an item from the clinical desktop would open it in view mode.<br />
* If set to "Edit" this would specify that double-clicking an item from the clinical desktop would open it in edit mode.<br />
<br />
Available Options: 'View' or 'Edit'<br />
Recommended Setting: 'View'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Due Date or Start Date for Newly Added Bulk Enrollment'''<br />
* Bulk Enrollment is currently not available. Leave this as is for now.<br />
<br />
<br />
'''Enable Allergy Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' the system would generate verification tasks for providers when allergies are entered by non-provider users. In this setting a newly entered allergy will remain in a unverified mode until verified by a provider. This is important for JCAHO accreditation. <br />
* If set to 'N' the system will add allergies to the patient's allergy list in a completed status without verification from a provider.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Enable E-Prescribe G Code Alert''' Added in v11.1.7<br />
For 2009, to be a "successful e-prescriber", a provider must report the e-prescribing quality measure through their Medicare Part B claims on at least 50% of applicable cases during the reporting year. <br />
<br />
* If set to 'Y' a reminder will be added to the Encounter Summary for all Medicare patients that an e-Prescribing G-Code may be appropriate for this encounter. This is a reminder to the facility that they need to manually add the G-Code to their Encounter Form. This ensures all prescriptions should count towards the qualifications necessary to be seen as a "successful e-prescriber."<br />
* If set to 'N' no reminder will appear.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Enable MSHV''' Added in v11.1.7<br />
Determines whether or not the HealthVault specific settings should be available on the patient profile dialog. <br />
* If set to 'Y' the Health specific settings shodul display on the patient profile dialog and allow for a patient to be linked to their HealthVault account. <br />
* If set to 'N' then patient accounts cannot be linked to HealthVault.<br />
Note: Enterprise EHR usres should also not have the ability to import or export CEDs from MS HealthVault if this preference is set to N<br />
<br />
Available Options: 'Y' or 'N'<br />
Default Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Encounter Selection from Worklist'''<br />
* When set to 'Encounter Selector'<br />
* When set to 'Create New Encounter'<br />
<br />
Available Options: 'Encounter Selector' or 'Create New Encounter'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Summary Always Print Medication Profile''' Added in v11.1.7<br />
Encounter Summary: Always print medication profile<br />
* <br />
<br />
Available Options: 'Y' or 'N'<br />
Default Seting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Type for Worklist'''<br />
This preference previously only applied to results. Effective in v11.1.7, this preference is applied to all work done on Worklist. The intent is to reduce the instances when a use is presented with an encounter selector without increasing the number of times work done during an appointment is documented against a non-appointment encounter.<br />
<br />
Available Options: Active entries in the Encounter Type dictionary<br />
Recommended Setting: Chart Update<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Encounter Summary Default View'''<br />
* When set to 'Type' the encounter summary or commit screen will default to display items grouped by type (orders, problems, etc.)<br />
* When set to 'Problem' the encounter summary or commit screen will default to display items grouped by their associated problem. <br />
<br />
Available Options: 'Type' or 'Problem'<br />
Recommended Setting: 'Problem'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Encounter Summary Password Required on Save'''<br />
* If set to 'Y' the user must enter their password when saving the Encounter Summary <br />
* If set to 'N' the user does not need to enter their password when saving the encounter summary.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Encounter Summary Review Before Save'''<br />
*If set to 'Y', the encounter summary will appear when a user hits the commit button or leaves the patient's chart. This acts as a review process prior to committing the data. <br />
* If set to 'N', the Encounter Summary will not appear when a user hits the commit button or leaves the patient's chart. This will commit the data without the chance to review it. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is selected by default and should be shown in training<br />
<br />
'''Enterprise Emergency Telephone Number'''<br />
* This is a free text value designed to house the emergency telephone number for an Enterprise. This is displayed when printing patient instructions. <br />
<br />
Available Options: Free Text<br />
Recommended Setting: '911'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Fax Maximum Pages''' Added in v11.1.7<br />
Maximum number of pages (estimated)allowed in a chart fax<br />
* This is a numeric field<br />
<br />
Available Options: Free Text Numeric Field<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Fax Warning Type''' Added in v11.1.7<br />
Determines the type of warning users receive when exceeding the maximum number of pages to be faxed.<br />
<br />
Available Options: Block Fax, Disabled, Warn User<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''LanguageEditable'''<br />
* When set to 'Y', this allows users to edit the patient language on the Patient Profile Dialog or "i" screen. This allows users to specify the patient's primary language within AE-EHR.<br />
* When set to 'N', this will only allow users to view the patient's primary language on the Patient Profile Dialog or "i" screen. This is usually the preferred setting when this value is populated by the registration interface or if an organization prefers not to capture this information.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Mask SSN in Reports, Patient Search, & Patient Profile'''<br />
* When set to 'Y', this will hide the Social Security Number in the standard delivered reports, the patient search screen and the patient profile or "i" screen.<br />
* When set to 'N', this will allow users to see the Social Security Number in the standard delivered reports, the patient search screen and the patient profile or "i" screen.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Max # of Providers for All Provider View'''<br />
* This is a numeric value between 0-99. This specifies the maximum number of providers a user can add to the All Provider view. This is defined on the Daily Schedule within the personalize options. The recommendation is 20 and any more than that should be tested prior to implementing. This could introduce a performance issue or become unusable if too many schedules are merged together. <br />
<br />
Available Options: Numeric Value between 0-99<br />
Recommended Setting: 20<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Maximum Number of Seconds to allow for Worklist Load'''<br />
* This is a numeric value that represents the maximum number of seconds that the WorkList is allowed to consume before timing out. This setting is put into place to prevent any long term lock ups for a WorkList view that are improperly defined and potentially hindering system performance. In most cases, if the view is defined properly, this setting should have no merit. <br />
<br />
<br />
Available Options: Numeric Value <br />
Recommended Setting: 30<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Minimum # of Hours to Keep Patient Site Location and Encounter Status'''<br />
* This is a numeric value that establishes the length of time that the patient location and encounter status will be stored. This timeframe is based on the last update of either of the fields. For example, if this is set to 1 hour, this information would be cleared 1 hour after the last update to the patient location or encounter status. This is cleared out to ensure it is reset for the patients next visit. <br />
<br />
Available Options: Numeric value between 1-99<br />
Recommended Value: 2<br />
Available on these levels: Enterprise, Organization<br />
User Can Override? No, This is off and enforced<br />
<br />
'''Normative Growth Chart in Units'''<br />
* If set to ‘Us Units’ the Normative Growth chart will be displayed using US Units.<br />
* If set to ‘Metric Units’ the Normative Growth Chart will be displayed using Metric Units.<br />
<br />
Available Options: ‘Us Units’, ‘Metric Units’<br />
Recommended Value: ‘Us Units’<br />
Available on these levels: Enterprise, Organization, User<br />
User Can Override? Yes, This is on by default and should be shown during training. <br />
<br />
'''Authentication Time-Out'''<br />
* This is a numeric value that determines the number of minutes before the system requires authentication since the last time they authenticated. The system can be configured to ask for passwords when signing notes, prescribing medications, or committing the encounter summary. If a user has entered their password within the allowed timeframe defined by the setting, the user will not be required to enter their password. Once the time period has passed, the user will need to enter their password to verify their access. Setting this to 0 means that a user will need to enter their password once and their authentication session will not expire again during the session. <br />
Available Options: Numeric value from 0 – 99<br />
Recommended Setting: 5<br />
Available on these levels: Enterprise, Organization<br />
User can override? No, this is off an enforced<br />
<br />
'''Patient Tracking-Use Patient Encounter Status'''<br />
* If set to 'Y', this will enable this drop down and the values available for the assigned site will apear in the drop down for an arrived patient. <br />
* If set to 'N', the drop down box on the patient toolbar will be disabled, but still visible. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Patient Tracking-Use Patient Site Location'''<br />
* If set to 'Y', this will enable this drop down and the values available for the assigned site will appear in the drop down for an arrived patient. <br />
* If set to 'N', the drop down box on the patient toolbar will be disabled, but still visible. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Previously Discontinued Patient'''<br />
* If set to 'Immediate' the user will be prompted with a warning if an order being added has been discontinued for that patient in the past. <br />
* If set to 'Never' the user will not be warned of this condition.<br />
<br />
Available Options: 'Immediate' or 'Never' <br />
Recommended Setting: 'Never' <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Print Patient Education'''<br />
* If set to 'Always' the indicator on the encounter summary screen will be selected and printed anytime patient edcuation is available whether it is part of a CareGuide or custom education materials added by the client. This setting can be overridden on the encounter summary if the user doesn't want them for a specific encounter.<br />
* If set to 'CareGuide Only', the indicator on the encounter summary screen will be selected and printed anytime patient education is available if included with the CareGuide. This setting can be overridden on the Encounter Summary if the user doesn't want them for a specific encounter.<br />
<br />
Available Options: 'Always' or 'CareGuide Only'<br />
Recommended Setting: 'Always' <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option, but not selected by default<br />
<br />
'''Provider Selection limited to Favorites'''<br />
* If set to 'Y' the user or provider is limited to selecting a provider from their favorites list in the drop down. The search field will be hidden and they are prevented from selecting other providers. This is typically only used in a multi-org situation when it is not viable for users to see the entire list of providers. <br />
* If set to 'N' the user or provider has the ability to do a lookup against the entire provider dictionary. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Toolbar Default for Clinician Choice Button''' Added in v11.1.7<br />
Default for Clinical Choice Button to direct user to a specific tab in ACI<br />
<br />
Available Options: 'Active', 'Past Medical History', 'Past Surgical History', 'Family History', 'Social History'<br />
'Allergies', 'Medication History', 'Immunization History', 'Chief Complaint', 'Rx'<br />
'Medication Administration', 'Lab/Procedures', 'Imaging', 'Follow Up/Referral', 'Instructions'<br />
'Immunizations', 'Supplies', 'CareGuides', or 'QSets'<br />
Default Setting: 'Chief Complaint'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for History Builder Button''' Added in v11.1.7<br />
Default for History Builder Button to direct user to a specific History Builder tab in ACI<br />
<br />
Available Options: 'Active', 'Past Medical History', 'Past Surgical History', 'Family History', 'Social History'<br />
'Allergies', 'Medication History', 'Immunization History', or 'Chief Complaint'<br />
Default Setting: 'Active'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for Problem-Based Order Button''' Added in v11.1.7<br />
Default for Problem-Based Order Button to direct user to a specific Problem-Based Order tab in ACI<br />
<br />
Available Options: 'CareGuide' or 'QSets'<br />
Default Setting: 'QSets'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
<br />
'''Toolbar Default for Rx/Orders Button - Lab Icon''' Added in v11.1.7<br />
Default for Rx/Orders Button - Lab Icon to direct user to a specific Rx/Orders tab in ACI<br />
<br />
Available Options: 'Lab/Procedures', 'Imaging', 'Follow Up/Referral', 'Instructions'<br />
'Immunizations', or 'Supplies'<br />
Default Setting: 'Lab/Procedures'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Toolbar Default for Rx/Orders Button - Rx Icon''' Added in v11.1.7<br />
Default for Rx/Orders Button - Rx Icon to direct user to a specific Rx/Orders tab in ACI<br />
<br />
Available Options: 'Rx' or 'Medication Administration'<br />
Default Setting: 'Rx'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''UA Install Location''' This preference is no longer used. <br />
<br />
'''Use Clinical Desktop Default View When Switching Patients''' Added in v11.1.7<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Use Organization or Site Address for Patient Ed Print Out''' Added in v11.1.7<br />
Determines which address to display on the patient education print out. <br />
<br />
Available Options: 'Site' or 'Organization'<br />
Default Setting: 'Organization'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''URL to find the UAI DesktopAgent install (optional)'''<br />
* This setting is to be used by clients using the UAI application only. If this is to be used, the technical resource installing the UAI tool would provide the appropriate setting for this field. <br />
<br />
Available Options: Free Text - provided by technical representative<br />
Recommended Setting: Blank unless using UAI<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Works 0 FingerPrintAuthEnc'''<br />
* This is disabled and not used at this time. Do not modify. <br />
<br />
'''Workspace view for tasks that navigate to worklist'''<br />
* This setting determines the default clinical desktop view to use when working an worklist related item from the task list. When a worklist task is double-clicked from the task list, it will navigate the user to the clinical desktop and use the defined view. This should be set to a Clinical Desktop View that is designed to efficiently complete worklist items. <br />
<br />
Available Options: Drop down list of available clinical desktop views<br />
Recommended Setting: Worklist view designed to efficiently complete worklist items<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this should be explained in training.<br />
<br />
==Meds Preferences==<br />
'''Apply to All checkbox on the Print Dialog presented for Prescriptions'''<br />
* If set to 'Y' the 'apply to all' checkbox will be selected by default on the Prescription Print Dialog.<br />
* If set to 'N' the 'apply to all' check box will not be selected by default on the Prescription Print Dialog.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Auto Dispense Inventory Medications''' Added in v11.1.7<br />
Set prescribe action to dispense for in-inventory medications<br />
<br />
Available Options: 'Y' or 'N'<br />
Default Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Days Before RxAction Date To Consider Near Due'''<br />
* This is a numeric value between 0-99. This represents the number of days prior to a Prescription Action being due to consider it near due and a reminder is created. <br />
<br />
Available Options: Numeric value between 0-99<br />
Recommended Setting: 14<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Rx Action for a renewal from'''<br />
* If set to 'previous action' the renewed prescription will default to the Rx action used during for the original version of the prescription.<br />
* If set to 'User Default' the renewed prescription will default to the users default Rx action. <br />
<br />
Available Options: 'previous action', 'user default'<br />
Recommended Setting: 'previous action'<br />
Can be set on these levels: Enterprise, Organization, user<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Default Rx Action'''<br />
* If set to 'Call Rx' the Rx action will default to Call Rx.<br />
* If set to 'Dispense Sample', the Rx action will default to Dispense sample.<br />
* If set to 'Print Rx' the Rx action will default to Print Rx.<br />
* If set to 'Record' the Rx action will default to Record.<br />
* If set to 'Send To Mail Order' the Rx action will default to Send To Mail Order.<br />
* If set to 'Send to Retail' the Rx action will default to Send to Retail.<br />
<br />
Available Options: 'CallRx', 'Dispense Sample', 'Print Rx', 'Record', 'Send To Mail Order', 'Send to Retail'<br />
Recommended Setting: 'Send to Retail'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be shown during training.<br />
<br />
'''Default Admin By'''<br />
* If set to 'Y' the Default Admin By for a Medication Administration and Immunizations will default based on the previously used value. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin By for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
<br />
'''Default Admin Date'''<br />
* If set to 'Y' the Default Admin Date for a Medication Administration and Immunizations will default based on the previously used value. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Date for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Dose'''<br />
* If set to 'Y' the Default Admin Dose for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Dose for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Lot'''<br />
* If set to 'Y' the Default Admin Lot for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Lot for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Manufacturer'''<br />
* If set to 'Y' the Default Admin Manufacturer for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Manufacturer for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Route'''<br />
* If set to 'Y' the Default Admin Route for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Route for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Admin Site'''<br />
* If set to 'Y' the Default Admin Site for a Medication Administration and Immunizations will default based on the previously used value for the particular medication. This value is based on the site and will be stored differently for each site the user may work at.<br />
* If set to 'N' the Default Admin Site for a Medication Administration and Immunizations will not default for the user. This forces them to manually select the value each time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
'''Default Disp Save Default'''<br />
* If set to 'Y', this defaults the 'save as default for selected SIG' option to be selected on the medication screen. If this information is saved, the next time a provider selects that SIG, the Days, Quantity, Units, Refill, and DAW option will fill in based on the previously saved values. <br />
* If set to 'N', the 'save as default for selected SIG' will not be selected by default, but the provider can select this option if they prefer to save a default from time to time. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training<br />
<br />
<br />
'''DUR Acknowledge Reason''' <br />
* If set to 'Y' the user must provide a reason when ignoring a DUR Warning. <br />
* If set to 'N' the user will not be required to provide a reason for ignoring the warning. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Dose Check Interrupt Timing''' <br />
* If set to 'Immediate' the user will be prompted with a dose check DUR warning immediately after selecting the medication. For this setting to work, the Enterprise DUR settings for dosage must also be on.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Alcohol Check Interrupt Timing''' [DUR Preferences are no longer set per severity levels. They can only be set to "Immediate" or "Never".]<br />
* If set to 'Immediate' the user will be prompted with an alcohol check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Alcohol screening must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Drug Check Interrupt Timing''' [DUR Preferences are no longer set per severity levels. They can only be set to "Immediate'or Never".]<br />
<br />
* If set to 'Immediate' the user will be prompted with a drug-drug check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Drug-Drug interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Food Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a food check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for food screening interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning.<br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Drug to Healthstate Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Drug-Health State check DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Drug-Health State interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise'''<br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Duplicate Therapy Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Duplicate Therapy DUR warning immediately after selecting the medication. For this to work the Enterprise settings for Duplicate Therapy interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning.<br />
'''Note: The Dur Severity Levels are set in TWAdmin/Org Setup/Enterprise''' <br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Immunization - Expiration Date''' Added in v11.1.7<br />
Determines whether or not an expiration date is required to complete an immunization administration. <br />
* If set to 'Y' this will require the user to enter an expiration date<br />
* If set to 'N' this will not require the user to enter an expiration date<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Lot Required''' Added in v11.1.7<br />
Determines whether or not a lot is required to complete an immunization administration.<br />
* If set to 'Y' this will require the user to enter a lot number<br />
* If set to 'N' this will not require the user to enter a lot number<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Manufacturer''' Added in v11.1.7<br />
Determines whether or not a manufacturer is required to complete an immunization administration.<br />
* If set to 'Y' this will require the user to enter a manufacturer number<br />
* If set to 'N' this will not require the user to enter a manufacturer number<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - NDC''' Added in v11.1.7<br />
Determines whether or not an NDC number is required to complete an immunization administration. If Chargeable, is required only when value is configured in Charge Code field in OID.<br />
* If set to 'Y'<br />
* If set to 'N'<br />
* If set to 'Chargeable'<br />
<br />
Available Options: 'Y', 'N' or 'Chargeable'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Immunization - Requiredness''' Added in v11.1.7<br />
Required field behavior.<br />
* If set to Required to Complete<br />
* If set to Required to Save<br />
<br />
Available Options: 'Required to Complete' or 'Required to Save'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Expiration Date ''' Added in v11.1.7<br />
Determines whether or not an expiration date is required to complete a medication administration. <br />
* If set to 'Y' an expiration date is required to complete a medication administration<br />
* If set to 'N' an expiration date is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Lot Required ''' Added in v11.1.7<br />
Determines whether or not a lot is required to complete a medication administration. <br />
* If set to 'Y' a lot is required to complete a medication administration<br />
* If set to 'N' a lot is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Manufacturer''' Added in v11.1.7<br />
Determines whether or not a manufacturer is required to complete a medication administration. <br />
* If set to 'Y' a manufacturer is required to complete a medication administration<br />
* If set to 'N' a manufacturer is not required to complete a medication administration<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A <br />
<br />
'''Med Admin - NDC''' Added in v11.1.7<br />
Determines whether or not an NDC number is required to complete an medication administration. If Chargeable, is required only when value is configured in Charge Code field in OID.<br />
* If set to 'Y'<br />
* If set to 'N'<br />
* If set to 'Chargeable'<br />
<br />
Available Options: 'Y', 'N' or 'Chargeable'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Med Admin - Requiredness''' Added in v11.1.7<br />
Required field behavior.<br />
* If set to Required to Complete<br />
* If set to Required to Save<br />
<br />
Available Options: 'Required to Complete' or 'Required to Save'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''PAR Check Interrupt Timing'''<br />
* If set to 'Immediate' the user will be prompted with a Prior Adverse Reaction (PAR) warning immediately after selecting the medication. For this to work the Enterprise settings for PAR interactions must also be enabled.<br />
* If set to 'Never' the user will not be prompted with this type of warning. <br />
<br />
Available Options: 'Immediate', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable Rx Hub Medication History'''<br />
* If set to 'Y' the application will allow patient history to be loaded from Rx Hub. This requires that the patient's medication benefits information is added to the application and a match can be made with the Rx Hub Warehouse. If these items are both true, a patients historical medications will be loaded into the system. <br />
* If set to 'N' the system will not attempt to load the patient's historical medications. <br />
* New in v11.1.6 and newer this can be disabled for individual patients to meet HIPPA -see [[Med History Patient Disable]] <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable SCRIPT Messaging'''<br />
* If set to 'Y' then Script messaging is enabled between the physician and the pharmacies using the SureScripts network. This requires other setup as well, but must be enabled for physicians or systems that have been setup and want to use this type of messaging. When turned on, the system will determine if the pharmacy is a script enabled pharmacy and determine if a script should be sent electronically or as a fax. This occurs when the Rx Action is Send to Retail. Inbound Script messages will appear as New Prescription Request (NEWRX), Renewal Request (REFREQ), and Renewal Response (REFRES) messages.<br />
* If set to 'N' Script messaging will be disabled. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N', unless setup for SureScripts usage<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Enable Touchscript Messaging'''<br />
* If 'Y' is selected then organizations can send in-office medication requests from TouchWorks to TouchScripts. This would be used if you are using the FirstFill product which is a part of TouchScripts. If you are interested in this product you would contact your account manager.<br />
* If set to 'N' this feature will be disabled.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N', unless setup for FirstFill usage<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Formulary Alternatives Reason Required'''<br />
* If set to 'off formulary with preferred' the user would be required to enter a reason for prescribing a specific medication when the medication is off formulary and there are preferred medications available. <br />
* If set to 'preferred' the user would be required to enter a reason for prescribing a specific medication when the medication has preferred alternatives available.<br />
* If set to 'never' the user would not be forced to provide a reason for ignoring formulary alternatives. <br />
<br />
Available Options: 'off formulary with preferred', 'preferred', 'never'<br />
Recommended Setting: 'never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Formulary Checking Interrupt Timing'''<br />
* If set to 'Immediate' the user would be prompted with formulary checking alternatives as they are prescribing the medication. <br />
* If set to 'Deferred' the user would be prompted with formulary checking alternatives as they are committing the encounter summary information.<br />
* If set to 'Never' the user would not receive the warning.<br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never'<br />
Recommended Setting: 'Immediate'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Immunization Order Authorization Required'''<br />
* If set to 'Prospective' a task will be created for a user/provider that does not have the appropriate medication prescribing levels. The task must be authorized by the ordering provider before the request can be fulfilled.<br />
* If set to 'Retrospective' a task will be created for the ordering provider for auditing purposes only. The immunization can still be fulfilled at the time of entry, but the audit task will be created for review. <br />
* If set to 'Not Required' no tasks will be created and the immunization will be completed at the time of entry and completion. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Not Required'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
*Special Note - If a user has the 'Med Order Protocol' Security code assigned to them, they do have the ability to override the Prospective authorization setting. This allows for users to choose "Per Protocol" or "Per Verbal Order" on the Immunization Detail screen and allows for clinics to continue these workflows. This would change the setting to Retrospective in this case and the provider would receive an audit task. <br />
<br />
'''MAR Prescription BarCode'''<br />
* If set to 'AHS RX Number' the bar code printed on the MAR prescription will use the Allscripts Rx Number. <br />
* If set to 'NDC' the bar code printed will have the National Drug Code. <br />
* If set tp 'GPI' the bar code printed will use the Gingival-Periodontal Index code. <br />
<br />
Available Options: 'AHS Rx Number', 'NDC', 'GPI'<br />
Recommended Setting: Leave this setting alone. This is only used with the MAR product which most clinics do not use. <br />
For the few clients that do use this module, this setting would be based on their needs.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Med History Query Duration'''<br />
* Available in 11.1.6 and newer only!<br />
* Allows for a specific amount of time (in months) for retrieval of patients medication history from Rx Hub<br />
* Configurable from one month to 24 months.<br />
Available Options: Numeric from 1 to 24<br />
Default Setting: is 6 (months)<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Minutes Before Re-Authentication Is Required For Medication Order'''<br />
* This preference is enacted when the setting for '''Order Authentication Required''' is set to yes. If order authentication is required, this value is the number of minutes before a user is required to reauthenticate within the system. If this setting is set to 0, the system will only ask for a password once during a session when ordering a med. If set to 5, the user will need to reauthenticate if they have not completed an action that required authentication within the past 5 minutes. This setting does not apply to the login screen.<br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: '0'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Non-Scheduled Meds Order Authorization Required'''<br />
* If set to 'Prospective' a task will be created for a user/provider that does not have the appropriate medication prescribing levels. The task must be authorized by the ordering provider before the request can be fulfilled.<br />
* If set to 'Retrospective' a task will be created for the ordering provider for auditing purposes only. The medication request can still be fulfilled at the time of entry, but the audit task will be created for review. <br />
* If set to 'Not Required' no tasks will be created and the medication request will be completed at the time of entry and completion. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Prospective'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
*Special Note - If a user has the 'Med Order Protocol' Security code assigned to them, they do have the ability to override the Prospective authorization setting. This allows for users to choose "Per Protocol" or "Per Verbal Order" on the Medication Detail screen and allows for clinics to continue these workflows. This would change the setting to Retrospective in this case and the provider would receive an audit task. <br />
<br />
'''OrderPresentForumlaryAlternatives'''<br />
* If set to 'off formulary with preferred' the user would be presented with formulary alternatives when the medication is off formulary and there are preferred medications available. <br />
* If set to 'preferred' the user would be presented with formulary alternatives when the medication has preferred alternatives available.<br />
* If set to 'never' the user would not be presented with formulary alternatives. <br />
<br />
Available Options: 'off formulary with preferred', 'preferred', 'never'<br />
Recommended Setting: 'off formulary with preferred'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on and should be described during training<br />
<br />
<br />
'''Prohibit Transmission of Schedule III Rx'''<br />
* If set to 'Y' the transmission of Schedule III drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule III drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule II Rx'''<br />
* If set to 'Y' the transmission of Schedule II drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule II drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule IV Rx'''<br />
* If set to 'Y' the transmission of Schedule IV drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule IV drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prohibit Transmission of Schedule V Rx'''<br />
* If set to 'Y' the transmission of Schedule V drugs electronically will be prohibited. This would not allow users the ability to use 'Send to Retail' for this class of drugs. <br />
* If set to 'N' the transmission of Schedule V drugs electronically will be allowed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Override Sign Rx Task for Schedule II Meds'''<br />
* This setting is not used and should be left blank.<br />
<br />
'''Override Sign RX Task for Schedule III-V Meds (Override Sign Rx CIII-V)'''<br />
* This setting is not used and should be left blank.<br />
-------------------------------------------------------------------------------------------------------------<br />
'''Enable Medication Administration Schedule''' - Need to verify this. This preference goes along with the MAR system.<br />
<br />
* If set to 'Y' the ability to schedule a medication administration is available.<br />
* If set to 'N' the ability to schedule a medication administration is not available.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
-------------------------------------------------------------------------------------------------------------<br />
'''Non-Formulary Authorization Required'''<br />
* If set to 'Y' the medication will require authorization prior to fulfillment if prescribing off formulary and will not print without authorization.<br />
* If set to 'N' the system will not require authorization if prescribed medications are off formulary<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribe Print Problem'''<br />
* If set to 'Y' the problem tied to the medication will be printed on the prescription.<br />
* If set to 'N' the problem tied to the medication will not display on prescriptions.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Sites'''<br />
* If set to 'Y' the Site will display on the prescription<br />
* If set to 'N' the Site will not display on the prescription<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Sites name/address on the printed scheduled prescription'''<br />
* If set to 'Y' the Site name and address will display on the controlled prescription<br />
* If set to 'N' the Site name and address will not display on the controlled prescription<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Prescribe Problem Linking Required'''<br />
* If set to 'Required to Save", the prescription details screen will require a user to select a linked problem prior to saving the prescription. <br />
* If set to 'Needs Info Reason', the user does not have to select a problem on the medication detail screen, but the medication will go to a needs info status and create a "Rx Info - Problem" task. This task will need to be worked and completed before the medication can be fulfilled.<br />
* If set to 'Not Required' the system will not force the user to select a problem when prescribing or renewing a medication.<br />
<br />
Available Options: 'Required to save', 'needs info reason', 'not required'<br />
Recommended Setting: 'Required to save' - this helps build quicksets<br />
Can be set on these levels: Enterprise, Organization, user<br />
User Can Override: Yes this is an option<br />
<br />
'''Editing Rx updates Ordered By Field'''<br />
* If set to 'Y' the Ordered by field will update to the current user renewing a medication if they are a valid ordering provider. This can be a good feature when physicians are covering for others and the desired behavior is to have the actual prescribing doctor documented as the Ordering Physician.<br />
* If set to 'N' the original Ordering Provider will remain unless manually overridden. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Warn if a medication is not participating in checking'''<br />
* If set to 'Y' the user will be prompted when prescribing a medication that does not participate in DUR checking. This is usually the case with user defined medications.<br />
* If set to 'N' the user will not be prompted when prescribing a medication that does not participate in DUR checking.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show Allscripts watermark on Faxed Prescriptions'''<br />
* If set to 'Hide' the Allscripts watermark will not appear on faxed prescriptions.<br />
* If set to 'Show' the Allscripts watermark will appear on faxed prescriptions.<br />
<br />
Available Options: 'Show' or 'Hide'<br />
Recommended Setting: 'Show'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Hide or Show the Allscripts watermark on Printed prescriptions'''<br />
* If set to 'Hide' the Allscripts watermark will not appear on printed prescriptions.<br />
* If set to 'Show' the Allscripts watermark will appear on printed prescriptions.<br />
<br />
Available Options: 'Show' or 'Hide'<br />
Recommended Setting: 'Show'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribing without Allergy Status'''<br />
* If set to 'Prevent' the user will be prompted when a patient's allergy status is not set. This will require them to define a patient's allergy status prior to completing a medication request. <br />
* If set to 'Warn' the user will receive a warning message stating the patient has an unknown allergy status when they are not defined for a patient. This occurs when selecting a medication from the ACI. <br />
* If set to 'Do Not Warn' the user will not receive a warning when prescribing medications.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a non-controlled medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a non-controlled medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a non-controlled medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required for Schedule II Meds'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a schedule II medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a schedule II medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a schedule II medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Rx Supervisor Signature Required for Schedule III-V Meds'''<br />
* If set to 'Not Required' the supervising physician will not be tasked when a ordering doctor that requires supervision prescribes a schedule III-V medication. <br />
* If set to 'Notification Only' the supervising physician will receive a Order Notification task when a ordering doctor that requires supervision prescribes a schedule III-V medication. The task will be assigned to the doctor that is defined as the supervising physician.<br />
* If set to 'Authorization before fulfillment' the supervising physician will receive an Authorize Order task when a ordering doctor that requires supervision prescribes a schedule III-V medication. The task will be assigned to the doctor that is defined as the supervising physician. The task must be completed before the medication will be fulfilled.<br />
<br />
Available Options: 'Not Required', 'Notification Only', 'Authorization before fulfillment'<br />
Recommended Setting: this should be based on your organizational policy<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Prescribing without Pharmacy Specified'''<br />
* If set to 'Prevent' the user will be prompted when a patient's pharmacy is not set. This will require them to define a pharmacy prior to completing a medication request. <br />
* If set to 'Warn' the user will receive a warning message stating the patient has no pharmacy when they are not defined for a patient. This occurs when selecting a medication from the ACI. <br />
* If set to 'Do Not Warn' the user will not receive a warning when prescribing medications and a pharmacy is not defined.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Require Re-Authentication For New or Renewed Prescriptions'''<br />
* If set to 'Y' the physician or user will be prompted to enter their password when prescribing or renewing a medication. This behavior is also dependant on the 'Authentication Time-Out' in the general preferences.<br />
* If set to 'N' the physician or user will not be prompted to enter their password.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Disable faxing of Class 2,3,4,5 Scheduled Meds'''<br />
* If set to '2' the system will not allow faxing of schedule II medications<br />
* If set to '2,3' the system will not allow faxing of schedule II or III medications<br />
* If set to '2,3,4' the system will not allow faxing of schedule II, III or IV medications<br />
* If set to '2,3,4,5' the system will not allow faxing of controlled medications<br />
* If set to 'Always' the system will not allow faxing of medications<br />
* If set to '' all medication levels will fax<br />
<br />
Available Options: '2', '2,3', '2,3,4', '2,3,4,5', 'Always', ''<br />
Recommended Setting: '2' - this is the typical state requirement. <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Disable Printing of Class 2,3,4,5 Scheduled Meds'''<br />
* If set to '2' the system will not allow printing of schedule II medications<br />
* If set to '2,3' the system will not allow printing of schedule II or III medications<br />
* If set to '2,3,4' the system will not allow printing of schedule II, III or IV medications<br />
* If set to '2,3,4,5' the system will not allow printing of controlled medications<br />
* If set to 'Always' the system will not allow printing of medications<br />
* If set to '' all medication levels will print<br />
<br />
Available Options: '2', '2,3', '2,3,4', '2,3,4,5', 'Always', ''<br />
Recommended Setting: '' <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''RxWeb List Limit'''<br />
* This is a numeric value that limits the number of medications returned in a search. This can be limited if searching is causing slow responses, but typically this is left blank.<br />
<br />
Available Options: Numeric value between 0-99<br />
Recommended Setting: leave blank (unlimited)<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option<br />
<br />
<br />
'''Samples - Expiration Date Required'''<br />
* If set to 'Y' the Expiration Date would be a required field when dispensing samples.<br />
* If set to 'N' the Expiration Date would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Lot Required'''<br />
* If set to 'Y' the Lot Number would be a required field when dispensing samples.<br />
* If set to 'N' the Lot Number would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Manufacturer required'''<br />
* If set to 'Y' the Manufacturer would be a required field when dispensing samples.<br />
* If set to 'N' the Manufacturer would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Quantity Required'''<br />
* If set to 'Y' the Quantity would be a required field when dispensing samples.<br />
* If set to 'N' the Quantity would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Samples - Quantity Units Required'''<br />
* If set to 'Y' the Quantity Units would be a required field when dispensing samples.<br />
* If set to 'N' the Quantity Units would not be a required field when dispensing samples<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Schedule III to V Meds Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task would be created if a level III to V medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and the medication would not be fulfilled until the provider authorizes the task.<br />
* If set to 'Retrospective' a Order Notification task would be created if a level III to V medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and serves as an audit trail. The medication would be fulfilled immediately and does not require this task to be worked first. <br />
* If set to 'Not Required' no tasks will be created if a level III to V medication is prescribed by a user without proper license information. That medication would be fulfilled immediately. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required' <br />
Recommended Setting: 'Prospective' - this should be based on your organizations policy<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
<br />
'''Schedule II Meds Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task would be created if a level II medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and the medication would not be fulfilled until the provider authorizes the task.<br />
* If set to 'Retrospective' a Order Notification task would be created if a level II medication is prescribed by a user without proper license information. The task would be assigned to the defined Ordering Provider and serves as an audit trail. The medication would be fulfilled immediately and does not require this task to be worked first. <br />
* If set to 'Not Required' no tasks will be created if a level II medication is prescribed by a user without proper license information. That medication would be fulfilled immediately. <br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required' <br />
Recommended Setting: 'Prospective' - this should be based on your organizations policy<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
==Meds/Orders Preferences==<br />
'''Duplicate Checking Order Interval (Hrs)'''<br />
* This Value is a number representing number of hours. This tells the system how many hours in the past it should look for a duplicate order. If a duplicate is found within the specified timeframe, the user will receive a message with that information, which allows them to determine if another test is needed or not. <br />
<br />
Available Options: 0-99<br />
Recommended Setting: 48<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Enable Rx-Orders Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' this will require verification when non-provider users enter med or order history. This means that a provider will be tasked with verifying the clinical items before it becomes a true addition to the patient's chart. A Task would be created for the Ordering physician to verify.<br />
* If set to 'N', the med or order entries would not require verification prior to being added to the patient's chart when added by a non-provider user.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Med/Orders List Review''' - Leave blank, this is currently unused.<br />
<br />
'''Monitor Order Selection'''<br />
* If set to 'Y' the system will track how users are selecting orders. This will determine if the user used their favorites, QuickSets or CareGuides. This can be used to review workflows. This information is stored in the database, but would require a special script to retrieve the data.<br />
* If set to 'N', they will not track how orders are selected.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Cancel Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Cancel reason if they choose to cancel an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Cancel reason, but it is not required to continue.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Cancel reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Chargeable Requires Billable ICD-9'''<br />
* If set to 'Required to Save' the system will require that the problem is tied to a billable Problem with an appropriate ICD9 code when the Orderable item is defined as chargeable. This will need to be selected before the user can save the Order.<br />
* If set to 'Needs Info Reason' the system will allow a user to save an Order with a CPT code, but it would go to a needs info status until someone associates an appropriate billable problem to the Order. <br />
* If set to 'Not Required' the system will not require a chargeable order be tied to an appropriate billable problem. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''CPT Requires Billable ICD9'''<br />
* If set to 'Required to Save' the system will require that the problem is tied to a billable Problem with an appropriate ICD9 code when the Orderable item has an associated CPT code. This will need to be selected before the user can save the Order.<br />
* If set to 'Needs Info Reason' the system will allow a user to save an Order with a CPT code, but it would go to a needs info status until someone associates an appropriate billable problem to the Order. <br />
* If set to 'Not Required' the system will not require a chargeable order be tied to an approapriate billable problem. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Discontinue Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Discontinue reason if they choose to discontinue an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Discontinue reason, but it is not required to discontinue.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Discontinue reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''OderDeferReason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Defer reason if they choose to defer an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Defer reason, but it is not required to defer.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Defer reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Entered in Error Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Entered in Error reason if they choose to mark an order as entered in error. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Entered in Error reason, but it is not required to mark an order as entered in error. <br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Entered in Error reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''OrderPermanentDeferReason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Permanent Defer reason if they choose to permanently defer an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Permanent Defer reason, but it is not required to permanently defer.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Permanent Defer reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Void Reason'''<br />
* If set to 'Required' the user or provider will be required to provide an Order Void reason if they choose to void an order. <br />
* If set to 'Prompt' the user or provider will be prompted to provide an Order Void reason, but it is not required to void an order.<br />
* If set to 'Allowed' the user or provider will not be prompted to provide an Order Void reason.<br />
<br />
Available Options: 'Required', 'Prompt', 'Allowed'<br />
Recommended Setting: 'Allowed'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes this is available<br />
<br />
'''Create Overdue Tasks for'''<br />
* If set to 'All Overdue' the system will create Overdue order tasks assigned to the ordering provider for all orders that are considered overdue. <br />
* If set to 'Overdue Important' the system will create overdue order tasks assigned to the ordering provider if the ordering provider selected the "Overdue Important" setting on the Order Details screen. <br />
<br />
Available Options: 'All Overdue', 'Overdue Important'<br />
Recommended Setting: 'Overdue Important'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
==Note Preferences==<br />
<br />
'''Document Add Review Stamp''' Add in v11.1.7<br />
Add review stamp when a document review task is completed. <br />
* When set to 'Y' a review stamp displaying the reviewing provider's name, date & time will display on the document reviewed.<br />
* When set to 'N' no review stamp will display<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes<br />
<br />
'''Note Auto Unlock Notes After Time'''<br />
* This is a numeric value that represents hours. This will tell the system how many hours should occur before the system automatically unlocks v11 note. A note remains locked when a user is editing a note and at times this can be left open accidentally or an issue may have occurred that didn't properly close the note. This preference only applies to v11 note. This preference prevents notes from being locked when there is no TouchWorks session open. <br />
<br />
<br />
<br />
Available Options: Numeric value<br />
Recommended Setting: 24<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Make Final'''<br />
* Allows the System Administrator to configure a default state for the Make Final option on the Note Signature page to accommodate the provider’s most common workflow for signing documents and the need to finalize.<br />
* If set to 'Y' the 'Make Final' checkbox will default to being selected when a user or provider that has the appropriate signature levels. <br />
* If set to 'N' the 'Make Final' checkbox will default to not being selected.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Navigation After Signing'''<br />
<br />
* Determines to which page the system navigates after the user signs a note.<br />
* If set to 'No Navigation' the user or provider will not be taken off of the note upon signing. <br />
* If set to 'Schedule' the user or provider will be brought to the Daily Schedule screen upon signing the note.<br />
* If set to 'Task View' the user or provider will be brought to the Task List screen upon signing the note.<br />
* If set to 'MD Charges' the user or provider will be brought to the Charge screen upon signing the note.<br />
<br />
Available Options: 'No Navigation', 'Schedule', 'Task View', 'MD Charges'<br />
Recommended Setting: 'No Navigation' - this really should be set on a user level based on their desired workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Note Default Owner'''<br />
* Determines the default owner for Notes.<br />
* If set to 'Use Appointment Encounter Provider if available, else use Most Recently Used' the system will default the note owner as the Appointment Provider. If there is no encounter provider available it will default to the most recently used provider.<br />
* If set to 'Always use Most recently used note owner' the system will default the note owner to the last provider used for that user. This is a preferred method when the user primarily works from an ancillary schedule such as a Lab Schedule and the encounter provider is not an actual human.<br />
* If set to 'None' the note owner will not default and will need to be selected each time a new note is created.<br />
<br />
Available Options: 'Use Appointment Encounter Provider if available, else use MRU', 'Always use MRU note owner', 'None'<br />
Recommended Setting: 'Use Appointment Encounter Provider if available, else use MRU'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Signature Display'''<br />
<br />
* This setting defines the format of the signature when signing a note. The available formats are:<br />
<br />
# Firstname Lastname, Credentials; Date/Time (Signature Type) <br />
# Firstname Lastname, Credentials; User/Profession Date/Time (Signature Type) <br />
# Firstname Lastname, Date/Time (Signature Type) <br />
# Firstname Lastname, User/Profession Date/Time (Signature Type)<br />
<br />
Recommended Setting: 'Firstname Lastname, Date/Time (Signature Type)'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Signature Type'''<br />
* This is a drop down menu that lists all available options from the Signature Type dictionary. The option selected will be defaulted into the Sign Note dialog box.<br />
<br />
Available Options: All active entries from the Signature Type dictionary<br />
Recommended Setting: Leave Blank and train the user to set the appropriate default.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Default Visit Type'''<br />
* Allows users to default to the previously used Visit Type.<br />
* If set to 'None' the visit type will not have a default value on the v11 note selector screen.<br />
* If set to 'Last' the visit type will default to the last visit type selected in the v11 note selector screen.<br />
<br />
Available Options: 'None', 'Last'<br />
Recommended Setting: 'Last'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Don't Generate Document Appt Encounter Tasks'''<br />
* If set to 'Y' the system will not generate Document Appointment Encounter Tasks.<br />
* If set to 'N' the system will generate Document Appointment Encounter Tasks. This task would serve as a reminder for the appointment encounter provider to create a note for the patients visit. The task will automatically be removed once a note is created. Most organizations use the note icon display on the schedule as the reminder or confirmation that all notes were created and choose not to use this option.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Don't Generate Review Covered Note Tasks'''<br />
* If set to 'Y' the system will not generate Review Covered Note Tasks.<br />
* If set to 'N' the system will generate Review Covered Note Tasks. This task would apply when a physician is covering for another doctor and signs off on a note for them. This setting also depends on the 'Create Review Covered Note Task on Finalization' setting in the [[Document Type]] dictionary. Both settings must be set properly to activate the task workflow.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''Note Lock Lists After Number Days'''<br />
<br />
* This is a numeric value that defines how many days until all lists within a note are locked. This includes lists such as Problems, Vitals, Immunizations, and Medications. This only applies to notes that have not been finalized. Once a note is finalized or this time limit has been reached, the lists will not update automatically.<br />
<br />
<br />
Available Options: Numeric value<br />
Recommended Setting: 7<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Is V10 Note User Only'''<br />
* If set to 'Y' the user or provider will only be able to create v10 notes. The v10 note selector will be presented to the user.<br />
* If set to 'N' the user or provider will be presented with the v11 note selector and have the ability to select either version of notes available to them. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: This should be set based on the organizations preference to use v11 note<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced <br />
<br />
'''CC or RFV Required for E&M Code''' - need further details to explain.<br />
* If set to 'Y' the E&M coder will require the CC or RFV be set.<br />
* If set to 'N' the E&M coder will not require these values. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''E/M Coder default to MDM tab'''<br />
* If set to 'Y' the E/M coder will default to the Medical Decision Making tab instead of the Summary tab.<br />
* If set to 'N' the E/M coder will default to the Summary tab.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''Post Text to Current Note'''<br />
* If set to 'Y' the default will be for the "post text to current note" option to be on. This will tell the system that the users actions should be posted to a note. There is a toggle button on the Clinical toolbar that can change this behavior easily during certain workflows. <br />
* If set to 'N' the default will be for the "post text to current note" option to be off. There is a toggle button on the Clinical toolbar that can change this behavior easily during certain workflows. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training<br />
<br />
'''UseAutoPrintForDefaultTemplate'''<br />
* If set to 'Y' the document will print using the document type specific document template and override the users preferred setting. This can be useful if certain types of document require specific document templates. <br />
* If set to 'N' the users auto-print defaults will be used. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
==Orders Preferences==<br />
'''Add Clinical Item Order Selection Method Default'''<br />
* If set to 'Problem Based' the ACI window will default to the problem based tab which is best for users that utilize CareGuide or QuickSets.<br />
* If set to 'Rx-Orders' the ACI window will default to the Rx/Orders tab which is best for users that don't use CareGuides or QuickSets.<br />
<br />
Available Options: 'Problem Based', 'Rx-Orders'<br />
Recommended Setting: This depends on the use of CareGuides and QuickSets<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is an option<br />
<br />
'''Always Present Fax Dialog When Requesting Faxing Requisition'''<br />
* If set to 'Y' the Fax Dialog screen will always present to a user when faxing a requisition.<br />
* If set to 'N' the Fax Dialog screen will only present to a user if they don't have a default defined.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Always Present Print Dialog When Printing Requisition'''<br />
* If set to 'Y' the 'Use Default Order Requisition Printer' option on the Encounter summary will default to unchecked and unless changed, the user will always be presented with the Print Dialog box when printing an Order Requisition.<br />
* If set to 'N' the 'Use Default Order Requisition Printer' option on the Encounter summary will default to checked and unless changed, the user will only be presented with the Print Dialog box when printing an Order Requisition if they do not have defaults defined.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training. <br />
<br />
'''Days before Scheduled Order Children To Be Done Date to Create Them'''<br />
* This is a numeric value that represents the number of days before a scheduled order is created. This is based on the "To Be Done Date" defined on the scheduled order. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 6<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Hold Orders for ABN'''<br />
* If set to 'Y' and order will be put in an 'On Hold' status until the ABN requirements are fulfilled.<br />
* If set to 'N' the order will not be put on an 'On Hold' status due to ABN requirements.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Minutes Before Re-Authentication Is Required for Non-Medication Order'''<br />
* This is a numeric value that represents the number of minutes before a user must enter their password to authenticate when ordering a non-medication order. <br />
<br />
Available Options: Numeric or Blank Values<br />
Value of "0" means that the users will be prompted every time to enter their password<br />
Value of "blank" means that the user will never be prompted to enter their password<br />
Recommended Setting: 0<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Non-Medication Order Authorization Required'''<br />
* If set to 'Prospective' an Order Authorization task will be created for the Ordering Physician if the user entering the order does not have the required ordering authority to order the item. This task must be completed before the order will be sent or fulfilled.<br />
* If set to 'Retrospective' and Order Notification task will be created for the Ordering Physician if the user entering the order does not have the required ordering authority to order the item. This task is informational only and does not prevent the order from being sent or fulfilled.<br />
* If set to 'Not Required' no tasks will be created.<br />
<br />
Available Options: 'Prospective', 'Retrospective', 'Not Required'<br />
Recommended Setting: 'Not Required' - this should be based on your organizational policies<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Order Medical Necessity Turned On'''<br />
* If set to 'Y' Medical Necessity checking will be enabled.<br />
* If set to 'N' Medical Necessity checking will be disabled.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Order Authorization level''' - this setting is not used, leave blank.<br />
<br />
'''Enable Order Authorization'''<br />
* If set to 'Y' Order Authorization tasks will be created if an orderable item is defined to require prospective authorization.<br />
* If set to 'N' orders will not require authorization.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Enable Order notification'''<br />
* If set to 'Y' order notification tasks will be created if an orderable item is defined to require retrospective authorization.<br />
* If set to 'N' orders notification tasks will not be created.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Order Notification Level'''<br />
* This is a numeric value that defines the Order level that a notification task should be created for. This number must be 1-10 and the system will create Order Notification tasks for any order that has a higher level than the value defined here if an Order is defined as requiring retrospective authorization.<br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: Leave blank<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Ordering Medications if Patient has Unverified Allergies'''<br />
* If set to 'Prevent' the system will require that the user verify unverified allergies before they can complete or save the order.<br />
* If set to 'Warn' the system will notify the user that a patient has unverified allergies, but will not prevent them from ordering the medication.<br />
* If set to 'Do Not Warn' the system will not notify the user if the patient has unverified allergies.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Do Not Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Ordering Medications if Patient has Unverified Medications'''<br />
* If set to 'Prevent' the system will require that the user verify unverified medications before they can complete or save the order.<br />
* If set to 'Warn' the system will notify the user that a patient has unverified medications, but will not prevent them from ordering the medication.<br />
* If set to 'Do Not Warn' the system will not notify the user if the patient has unverified medications.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Do Not Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Order Problem Linking Required'''<br />
* If set to 'Required to Save' the user must select a problem on the order detail screen before they are allowed to save the order. <br />
* If set to 'Needs Info Reason' the user will not be required to select a problem on the order detail screen, but the order will go to a 'Needs Info' status and must be completed before the order can be sent. <br />
* If set to 'Not Required' a user will not be required to select a problem when completing an order. <br />
<br />
Available Options: 'Required to Save', 'Needs Info Reason', 'Not Required'<br />
Recommended Setting: 'Required to Save'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Editing Order Updates Supervised by Field'''<br />
* If set to 'Y' the supervised field will be updated to the current user when updating an order.<br />
* If set to 'N' the supervised field will remain unless manually changed by the user. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Chargeable Order Problem Linkage to Billable ICD-9 Interrupt timing'''<br />
* If set to 'Immediate' the system will immediately warn and require the user to select an appropriate billable ICD9 code if the 'Chargeable Requires Billable ICD9' setting is on.<br />
* If set to 'Deferred' the system will warn and require the user to select an appropriate billable ICD9 code if the 'Chargeable Requires Billable ICD9' setting is on when they attempt to commit the patient data.<br />
* If set to 'Never' and the 'Chargeable Requires Billable ICD9' setting is off, the user will not be prompted.<br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Problem Linkage Interrupt Timing'''<br />
* If set to 'Immediate' and problem linking is required, the system will prompt the user to select a problem upon entering the order.<br />
* If set to 'Deferred' and problem linking is required, the system will prompt the user to select a problem upon selecting the commit button.<br />
* If set to 'Never' and problem linking is not required, the user will not be prompted. <br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Performing Location Problem Linkage to Billable ICD9 Required Interrupt Timing'''<br />
* If set to 'Immediate' and problem linking is required for the performing location, the system will prompt the user to select a problem upon entering the order.<br />
* If set to 'Deferred' and problem linking is required for the performing location, the system will prompt the user to select a problem upon selecting the commit button.<br />
* If set to 'Never' and problem linking is not required for the performing location, the user will not be prompted. <br />
<br />
Available Options: 'Immediate', 'Deferred', 'Never' <br />
Recommended Setting: 'Never'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced. <br />
<br />
'''Require Re-Authentication For New or Renewed Orders'''<br />
* If set to 'Y' the user will be prompted to enter their password if they have not authenticated within the timeframe specified for the 'Minutes Before Re-Authentication Is Required for Non-Medication Order' setting.<br />
* If set to 'N' the user will not be required to enter their password for new or renewed orders. This setting does not apply to medications.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Unspecified Billing Provider Matching''' Added in v11.1.7<br />
* It can be set to Order Only or Exact Match. If set to order Only, the system behaves as it is currently. If set to exact match, the billing provider derived from the order must match exactly to the encounter on which the charges are generated. So if set to Exact match – if the ordering provider and billing provider don’t match it won’t drop the charges to that encounter.<br />
<br />
Available Options: 'Order Only' or 'Exact Match'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced.<br />
<br />
==Problem Preferences==<br />
'''Enable Problem Verification''' see [[Change to Enable -clinical item- Verification]]<br />
* If set to 'Y' problems will be set to an unverified status when entered by a non-provider user. This information would need to be verified by a provider prior to becoming part of the patient chart.<br />
* If set to 'N' problems will not get set to an unverified status.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: No, this is off and enforced.<br />
<br />
'''Problem resolved date equals today'''<br />
* If set to 'Y' the resolved date will default to today when resolving a problem.<br />
* If set to 'N' the resolved date will not default and must be manually entered if desired.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Problem Include in PMH'''<br />
* If set to 'Unchecked' the 'Include in PMHx' option will not be selected by default on the problem detail screen.<br />
* If set to 'Checked for All' the 'Include in PMHx' option will always be selected by default on the problem detail screen.<br />
* If set to 'Checked for Chronic Only' the 'Include in PMHx' option will only be selected by default on the problem detail screen if the problem is classified as a chronic problem.<br />
<br />
Available Options: 'Unchecked', 'Checked for All', 'Checked for Chronic Only'<br />
Recommended Setting: 'Unchecked'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Problem List Review''' - this is currently unused, leave blank.<br />
<br />
'''Problem Post to Encounter'''<br />
* If set to 'Y' the problem will post to the encounter form when assessed. <br />
* If set to 'N' the problem will not post to the encounter form when assessed.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'Y'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Show unverified problems in the ALL view only'''<br />
* If set to 'Y' unverified problems will only appear in the All Problem view. <br />
* If set to 'N' unverified problems will appear in their respective categories.<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''When No Linked V code for PMH''' Added in v11.1.7<br />
<br />
Available Options: 'Show ICD-9 for active problem' or 'Show no ICD-9'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No<br />
<br />
==Results Preferences==<br />
'''Abnormal Result Flag OverrideAllowed'''<br />
* If set to 'Y' users will have the ability to override the abnormal flag sent from a vendor on the results detail screen. <br />
* If set to 'N' users will not have the ability to override the abnormal flag sent from a vendor. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Default Vitals - <10 years old'''<br />
* This is a free text field that defined the default vitals panel used for children under 10 years old. This value must be equal to the exact name of the vital sign picklist and is case sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by deault and should be explained during training.<br />
<br />
'''Default Vitals - 3 year old and younger'''<br />
* This is a free text field that defined the default vitals panel used for children 3 years old and younger. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Default Vitals - Female 10 years old or older'''<br />
* This is a free text field that defined the default vitals panel used for female patients 10 years old and older. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group and gender.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Default Vitals - Male 10 years old or older'''<br />
* This is a free text field that defined the default vitals panel used for male patients 10 years old and older. This value must be equal to the exact name of the vital sign picklist and is Case Sensitive. <br />
<br />
Available Options: Free text field that must be the exact name of a vitals picklist. This is case sensitive.<br />
Recommended Setting: set to a vitals picklist designed for this age group and gender.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Disable QVerify All and Verify All''' Added in v11.1.7<br />
* If set to 'Y' this will disable the use of Qverify All and Verify All<br />
* If set to 'N' this will enable the use of Qverify All and Verify All<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: Y<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: N/A<br />
<br />
'''Hide Grid Header from Result Display in Worklist''' Added in v11.1.7<br />
Determines if the grid header is hidden or not from the result display in the Worklist.<br />
* If set to 'Y' this will hide the grid header from the display in the Worklist<br />
* If set to 'N' this will not hide the grid header from the display in the Worklist<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization<br />
User can Override: Optional<br />
<br />
'''HMP Vitals Units'''<br />
* If set to 'US' the vitals flowsheet on the Health Management Screen will display in US units.<br />
* If set to 'Metric' the vitals flowsheet on the Health Management Screen will display in Metric units.<br />
* If set to 'As Entered' the vitals flowsheet on the Health Management Screen will display in the units that the vitals were entered as.<br />
<br />
Available Options: 'US', 'Metric', 'As Entered'<br />
Recommended Setting: 'US'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be explained during training.<br />
<br />
'''Number of Days of Results to include in Clinical Exchange Document'''<br />
* This is a numeric value that determines the number of days in the past that the Clinical Exchange Document will obtain results when created. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 3<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off by default.<br />
<br />
'''Number of Days of Vital Signs to include in Clinical Exchange Document'''<br />
* This is a numeric value that determines the number of days in the past that the Clinical Exchange Document will obtain vitals data when created. <br />
<br />
Available Options: Numeric Value<br />
Recommended Setting: 3<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off by default.<br />
<br />
'''Result Verification Append Staff Message to Staff Comment''' Added in v11.1.7<br />
Determines the default value for Append Staff Message to Task Comment checkbox.<br />
* When set to 'Y' the system checks the Copy Message to Staff to the Task Comment checkbox by default. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting:<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Result Verification Disable To/CC Button''' Added in v11.1.7<br />
Determines if the To/CC button is disabled on the Results Verification page. <br />
* If set to 'Y' this will disable the To/CC Button on the Results Verification page<br />
* If set to 'N' this will enable the To/CC Button on the Results Verification page<br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: <br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Optional<br />
<br />
'''Result Verification If Did Not Order'''<br />
Determines system response when the user that is verifying the result is not the ordering provider.<br />
* If set to 'Prevent' a provider will not be allowed to verify results that they did not order.<br />
* If set to 'Warn' a provider will be notified that they are attempting to verify results that they did not order.<br />
* If set to 'Do Not Warn' a provider will not get notified if attempting to verify results that they did not order.<br />
<br />
Available Options: 'Prevent', 'Warn', 'Do Not Warn'<br />
Recommended Setting: 'Warn'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Navigation After QVerify'''<br />
Determines the navigation path after the user clicks QVerify or QVerify All<br />
* If set to 'Go To Note' the provider will be brought to the Note when selecting QVerify during the results verification process.<br />
* If set to 'Go To Next Patient' the provider will remain in the patient worklist screen and the next patient with worklist items defined in their current view will be brought into context.<br />
* If set to 'Stay on Worklist' the provider will remain in the worklist on the current patient. <br />
<br />
Available Options: 'Go To Note', 'Go To Next Patient', 'Stay on Worklist'<br />
Recommended Setting: Depends on desired workflow, set the best default and train users to select their preference.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Note Type for QVerify''' Modified in v11.1.7<br />
* This is a drop down of all available note types in the system. The selection will default as the note type to use when performing a results verification workflow that requires a note. This also defines the note type used for QVerify.<br />
<br />
Available Options: Any note type in the document type dictionary that is valid (v10 or v11 note)<br />
Recommended Setting: Results Verification note type designed for this workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Note Type for Verify''' Added in v11.1.7<br />
* This is a drop down of all available note types in the system. The selection will default as the note type to use when performing a results verification workflow that requires a note. This also defines the note type used for Verify.<br />
<br />
Available Options: Any note type in the document type dictionary that is valid (v10 or v11 note)<br />
Recommended Setting: Results Verification note type designed for this workflow<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Note Use - For QVerify''' Modified in v11.1.7<br />
This preference determines the default note use value for the QVerify action. <br />
* If set to 'Create New Note' the user will default to creating a new note on the results verification screen. This will also define the default behavior when using QVerify.<br />
* If set to 'No Note' the results verification screen will not be set to use a note by default. This would also set the behavior of QVerify.<br />
* If set to 'Select Note' the results verification screen will be setup to use a note, but the user will need to select the note type they want to use.<br />
<br />
Available Options: 'Create New Note', 'No Note', 'Select Note'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Note Use - For Verify''' Added in v11.1.7<br />
This preference determines the default note use value for the QVerify action. <br />
* If set to 'Create New Note' the user will default to creating a new note on the results verification screen. This will also define the default behavior when using Verify.<br />
* If set to 'No Note' the results verification screen will not be set to use a note by default. This would also set the behavior of Verify.<br />
* If set to 'Select Note' the results verification screen will be setup to use a note, but the user will need to select the note type they want to use.<br />
<br />
Available Options: 'Create New Note', 'No Note', 'Select Note'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Patient Communication Methods for QVerify''' Added in v11.1.7<br />
This preference determines the default communication method for QVerify. <br />
* If set to 'Call Patient with Results' the 'Call Pt with Results' option will be selected by default on the Results Verification Screen. This option creates a 'Call Patient with Results' task and requires a note.<br />
* If set to 'Discussed Results With Patient' the 'Discussed results with patient' option is selected by default on the Results Verification Screen. This option does not require a note and it is noted in the Results communication details that this option was selected.<br />
* If set to 'Mail Results to Patient' the 'Mail Results to Patient' option is selected by default on the Results Verification Screen. This requires a note.<br />
* If set to 'No Patient Communication Needed at this Time' the 'No Patient communication needed at this time' option is selected by default. If used, this option is noted in the results communication details within the results details. <br />
* If set to 'Schedule Appointment to Discuss Results' the 'Schedule Results F/U' option is selected by default. This action creates a 'Schedule Results follow up task and does not require a note. <br />
<br />
Available Options: 'Call Patient with Results', 'Discussed Results With Patient', 'Mail Results to Patient', <br />
'No Patient Communication Needed at this Time','Schedule Appointment to Discuss Results'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Patient Communication Methods for Verify''' Added in v11.1.7<br />
This preference determines the default communication method for Verify. <br />
* If set to 'Call Patient with Results' the 'Call Pt with Results' option will be selected by default on the Results Verification Screen. This option creates a 'Call Patient with Results' task and requires a note.<br />
* If set to 'Discussed Results With Patient' the 'Discussed results with patient' option is selected by default on the Results Verification Screen. This option does not require a note and it is noted in the Results communication details that this option was selected.<br />
* If set to 'Mail Results to Patient' the 'Mail Results to Patient' option is selected by default on the Results Verification Screen. This requires a note.<br />
* If set to 'No Patient Communication Needed at this Time' the 'No Patient communication needed at this time' option is selected by default. If used, this option is noted in the results communication details within the results details. <br />
* If set to 'Schedule Appointment to Discuss Results' the 'Schedule Results F/U' option is selected by default. This action creates a 'Schedule Results follow up task and does not require a note. <br />
<br />
Available Options: 'Call Patient with Results', 'Discussed Results With Patient', 'Mail Results to Patient', <br />
'No Patient Communication Needed at this Time', 'Schedule Appointment to Discuss Results'<br />
Recommended Setting: Determined by workflow. Set to the best default and alert users of this preference during training.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Result Verification Task Assignment'''<br />
Determines the default value for the assignment of delegated ResultsVerification tasks. <br />
* If set to 'Current User' the user entering the result will be assigned the Results Verification task.<br />
* If set to 'Ordering Provider' the provider defined as the Ordering Provider will receive the Results Verification Task.<br />
<br />
Available Options: 'Current User'. 'Ordering Provider' <br />
Recommended Setting: 'Ordering Provider'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.<br />
<br />
'''Results Verification Required'''<br />
Determines the if results verification is required. <br />
* If set to 'Y' the 'Verification Required' field on the Order Details screen will be selected by default. This specifically pertains to manually entered results. Interfaced results will be set based on the interface definition and is in no way altered with this setting. If a manual result is entered and this option is selected, a Results Verification task will be created and assigned to the user based on the 'Result Verification Task Assignment' setting. <br />
* If set to 'N' the 'Verification Required' field will not be selected by default. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No, this is off and enforced<br />
<br />
'''Results Verification Shows Verified Results in Results Document - For QVerify''' Modified in v11.1.7<br />
Determines if the verified results should display on the Results Document for QVerify action. <br />
* If set to 'Y' the 'Show Verified Results in Result Document' option will be selected by default on the Result Verification Screen. Having this option selected automatically posts the verified results to the note created in the verification process.<br />
* If set to 'N' the 'Show verified results in Result Document' option will not be selected by default on the Result Verification screen.<br />
* If set to 'As Per Post to Note Icon' the 'Show verified results in Result Document' option will be selected by default if the users post to note option is on at the time. <br />
<br />
Available Options: 'Y', 'N', 'As Per Post to Note Icon'<br />
Recommended Setting: 'As Per Post to Note Icon'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training.<br />
<br />
'''Results Verification Shows Verified Results in Results Document - For Verify...''' Addedin v11.1.7<br />
Determines if the verified results should display on the Results Document for a Verify action. <br />
* If set to 'Y' the 'Show Verified Results in Result Document' option will be selected by default on the Result Verification Screen. Having this option selected automatically posts the verified results to the note created in the verification process.<br />
* If set to 'N' the 'Show verified results in Result Document' option will not be selected by default on the Result Verification screen.<br />
* If set to 'As Per Post to Note Icon' the 'Show verified results in Result Document' option will be selected by default if the users post to note option is on at the time. <br />
<br />
Available Options: 'Y', 'N', 'As Per Post to Note Icon'<br />
Recommended Setting: 'As Per Post to Note Icon'<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described in training.<br />
<br />
'''Require Abnormal Flag for Results Entry'''<br />
* If set to 'Y' the Abnormal flag will be required for all resultable items with an order. If you have an Order with many resultable items, the user will be required to select an abnormal flag for all values even if those values are not being reported. This applies to manually entered results only. <br />
* If set to 'N' the user will not be required to specify the abnormal flag when manually entering results. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No this is off and enforced.<br />
<br />
'''Use UAI Vital Signs Integration'''<br />
* If set to 'Y' the user will have the ability to capture vital signs using the UAI tool. This requires extra setup and the UAI module. This product allows you to capture and import vitals using a 3rd party device such as a Welch Alyn device.<br />
* If set to 'N' the user will not have the option to capture vital signs using the UAI tool. <br />
<br />
Available Options: 'Y' or 'N'<br />
Recommended Setting: 'N'<br />
Can be set on these levels: Enterprise, Organization<br />
User Can Override: No this is off and enforced.<br />
<br />
'''Vitals Picklist'''<br />
* This is a drop down list that defines the default Vitals Picklist to be used. This picklist defines the Vital Sign Views available to the end user.<br />
<br />
Available Options: Drop down list of valid Vital Sign Picklists defined in your OID dictionary.<br />
Recommended Setting: Use the preferred vital signs picklist defined by your organization.<br />
Can be set on these levels: Enterprise, Organization, User<br />
User Can Override: Yes, this is on by default and should be described during training.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=V11_Specialty_Favorites&diff=9385V11 Specialty Favorites2010-09-23T18:03:32Z<p>Troy.Forcier: /* What are Specialty favorites */</p>
<hr />
<div>=='''What are Specialty favorites'''==<br />
<br />
A new feature of AE-EHR in V11 is specialty favorites. This is a pre-loaded list of items frequently used by a specialty. The following dictionaries can have favorite items loaded for each specialty:<br />
<br />
'''Editable via Phys Admin > Favorites'''<br />
*Allergen HX<br />
*Allergen Med<br />
*Active Problems<br />
*Family History (FHx)<br />
*Past Medical History (PMH)<br />
*Past Surgical History (PSH)<br />
*Social History (PH)<br />
<br />
*User (example: assign task to user)<br />
*Provider (example: assign task to provider)<br />
*Schedulable Provider (example: assign appointment to provider)<br />
*Billing Provider (Charge > Encounter Form)<br />
*Referring Provider (Charge > Encounter Form)<br />
*Diagnosis (Charge > Diagnosis)<br />
*Procedure Charge<br />
*Visit Charge<br />
<br />
'''Editable via SSMT only'''<br />
*Immunizations<br />
*Order Immunizations<br />
*Order Med Admin<br />
*Orderable Item Rx<br />
*Medication HX<br />
<br />
'''Orderable Items favorites via SSMT OR in the PAT Admin workspace'''<br />
In 11.1.5 (perhaps earlier versions) and SSMT released on 1/27/09, Orderable items favorites can be loaded via SSMT at a specialty and user level.<br />
<br />
The benefit of having the pre-loaded specialty lists is that it dramatically decreases loading time when searching for items from the clinical desktop.<br />
<br />
=='''Best Practice'''==<br />
*'''Review''': The best practice for loading specialty favorites with an upgrade client is to have the client review the pre-delivered specialty favorites and then decide to either load the pre-delivered specialty favorites or not load the pre-delivered specialty favorites.<br />
<br />
*'''Check''': If the client will be using the Order module, the OCD-OID mapping must be completed before loading the Specialty Favorites from Allscripts.<br />
<br />
*'''Load''': Specialty Favorites are loaded via [[SSMT]] into the test environment.<br />
<br />
*'''Edit''': The client then can use the [[PAT]] Physician Administration Tool to Add/Delete favorites from the delivered lists.<br />
<br />
==Quicklists==<br />
Quicklists are an even more specific list of commonly used items, like items used on a daily basis. The Quicklists can be entered manually or, as of 11.1.5, can be entered by SSMT. The column labeled 'TopFavoriteFlag' is populated by Y or N. When 'Y', this row is added to the Quicklist as well as the Favorites.<br />
<br />
=='''Use the Physician Admin Tool to Edit Favorites'''==<br />
<br />
To edit favorites in the Physician Administration tool,<br />
*Login as TwAdmin<br />
*Navigate to the Physician Admin Menu by using the drop-down in the top right hand corner of the screen<br />
<br />
[[Image:Patpref1.jpg]]<br />
<br />
*Expand the “By Category” Menu<br />
<br />
[[Image:Patpref2.jpg]]<br />
<br />
*Select Favorites<br />
<br />
[[Image:Patpref3.jpg]]<br />
<br />
*Select the specialty that you want to edit favorites for<br />
<br />
[[Image:Patpref4.jpg]]<br />
<br />
*select the favorites that you want to edit (in this example we will look at pediatric diagnosis)<br />
<br />
[[Image:Patpref5.jpg]]<br />
<br />
*type in the beginning of the item you are looking for in the field next to the go button<br />
<br />
[[Image:Patpref6.jpg]]<br />
<br />
*Click on Go. The window below the word View will populate with items that match your search<br />
<br />
[[Image:Patpref7.jpg]]<br />
<br />
*select the diagnoses that you would like to include in your specialty favorites list, and they will populate in the right hand window.<br />
<br />
[[Image:Patpref8.jpg]]<br />
<br />
*To remove items from Specialty Favorites highlight the item(s) and click 'Remove'<br />
<br />
*When you have the ones that you would like, click on save.<br />
<br />
*Saved Successfully will appear in the upper right hand corner of your screen.<br />
<br />
[[Image:Patpref9.jpg]]<br />
<br />
==Changing Specialty Deletes Personal Favorites==<br />
<br />
Personal Favorites are now tied to specialty and if you change a provider’s specialty, all of their personal favorites will disappear. In the future, if you adjust a provider’s specialty, you must also plan to extract all of their favorites via SSMT and reload them with the appropriate specialty.<br><br />
A script exists to update this that can be run during the upgrade weekend once all provider specialties are set. This will ensure everyone has viewable specialties on Go-Live Monday, but going forward it will require the SSMT activities if adjusting a provider specialty.<br />
<br />
Related Tasks:<br />
<br />
[[Edit Personal Favorites - SSMT]]<br />
<br />
[[Copy Specialty Favorites to Personal Favorites]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Suggested_IE_Settings_-_V11&diff=9384Suggested IE Settings - V112010-09-23T17:56:52Z<p>Troy.Forcier: </p>
<hr />
<div>===Configuring General Internet Explorer Options===<br />
*Allscripts recommended settings<br />
#Open Internet Explorer, Select: Tools > Internet Options<br />
#On General tab > Temporary Internet files: <br />
##click Settings (located under browsing history for IE7) <br />
##set the option for “Check for newer versions of stored pages:” to “Automatic”<br />
#Save your new configuration by clicking Apply and OK<br />
#Install the ActiveX controls for AE-EHR per your preferred method – '''Push Technology''' strongly suggested<br />
<br />
==Configuring Advanced Internet Explorer Options==<br />
#Open Internet Explorer, Select: Tools > Internet Options<br />
#On Advanced tab, click Restore Defaults<br />
#Ensure “Enable third-party browser extensions” is checked<br />
#Ensure “Use smooth scrolling” is unchecked (for performance reasons)<br />
#Uncheck "Do not save encrypted pages to disk"<br />
#Optional:<br />
##Uncheck “Disable script debugging”<br />
##Uncheck “Show friendly HTTP error messages”<br />
''Note:'' Optional settings are helpful in troubleshooting problems/errors within AE-EHR<br />
<br />
==Add AE-EHR URL(s) to Trusted Sites==<br />
#Open Internet Explorer, Select: Tools > Internet Options<br />
#Click on the Security Tab and select Trusted Sites<br />
#Click Sites<br />
#Type in your AE-EHR URL and click Add<br />
#Click Close</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=9383Acronyms, Abbreviations & Other Definitions2010-09-23T17:52:51Z<p>Troy.Forcier: /* A */</p>
<hr />
<div>__TOC__<br />
==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or form the real term to a page with that information.<br />
===A===<br />
*AHIMA - American Health Information Management Association<br />
<br />
*ACI - Add Clinical Item<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*AE-EHR - Allscripts Enterprise EHR<br />
<br />
*[[AHSVOEService]]<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA - American Medical Association<br />
<br />
[[#top|Top]]<br />
<br />
===B===<br />
*BW - Build Workbook. Allscripts terminology; is a workbook provided to clients to assist and organize v11 data collection and build activities.<br />
<br />
[[#top|Top]]<br />
===C===<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*[[CDA]] - Clinical Document Architecture<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*[[CCI]]- Correct Coding Initiative http://www.cms.gov/NationalCorrectCodInitEd<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CPOE - Computerized Physician Order Entry, industry term. The electronic entry by a physician of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CDT - Clinical Desktop<br />
<br />
[[#top|Top]]<br />
===D===<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
[[#top|Top]]<br />
===E===<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
[[#top|Top]]<br />
===F===<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
<br />
<br />
[[#top|Top]]<br />
===G===<br />
*GUI - Graphic User Interface<br />
<br />
[[#top|Top]]<br />
===H===<br />
*[[HCPCS]]- Healthcare procedural coding system.<br />
<br />
*HEDIS - The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] Health Information Exchange<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*[[HIT]]- Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information ususally contained in a patients chart on a computer, rather than on paper <br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*HL7 - Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HTB]] – Horizontal Tool Bar the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
[[#top|Top]]<br />
===I===<br />
*ICD9 - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] Integrating the Healthcare Enterprise<br />
<br />
*IPA - Independent Practice Association-consists of a network of physicians in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the physicians in the IPA.<br />
<br />
*ISO - International Organization for Standarization<br />
<br />
[[#top|Top]]<br />
===J===<br />
*JCAHO - Joint Commission on Accreditation of Healthcare Organizations<br />
<br />
[[#top|Top]]<br />
===K===<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users.<br />
<br />
*KPI - Key Performance Indicator; business term. Can include common measures and statistics aggregated from the EHR in order to assess compliance, meaningful use, or work flow consistency.<br />
<br />
[[#top|Top]]<br />
<br />
===L===<br />
*LAN - Local Area Network<br />
<br />
*LIS - Laboratory Information System. A general term often used to reference an internal or external laboratory system.<br />
<br />
*LMRP - Local Medical Review Policy<br />
<br />
[[#top|Top]]<br />
===M===<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MDM - Medical Document Management<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
[[#top|Top]]<br />
===N===<br />
*[[NAW]] - Note Authoring Workspace<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance<br />
<br />
*[[NDC]]-National Drug Code<br />
<br />
*NPI - National Provider Identifier<br />
<br />
[[#top|Top]]<br />
<br />
===O===<br />
*OBR - Observation Request Segment<br />
<br />
*OCD – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*OID – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
[[#top|Top]]<br />
<br />
===P===<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*PAT – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCP- Primary Care Provider<br />
<br />
*PHI - Personally Identifiable Health Information<br />
<br />
*PHR – Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*[[PMS]] - Practice Management System <br />
<br />
*[[PQRI]]- Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
[[#top|Top]]<br />
<br />
===R===<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*[[RID|RID – Resultable Item Dictionary]]<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RLS - Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*ROI – Return on Investment or Release of Information, when used by medical records staff<br />
<br />
*RTI - Real Time Intervention<br />
<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
[[#top|Top]]<br />
<br />
===S===<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SQL - Structured Query Language; technical term. The primary DBMS and programming language for Enterprise EHR.<br />
<br />
*SSMT – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
[[#top|Top]]<br />
<br />
===T===<br />
*TCP/IP - Transfer Communication Protocol/Internet Protocol. http://en.wikipedia.org/wiki/TCP/IP<br />
<br />
*TIU - [[Text Input Utility]] - this is the Word integrated transcription tool for typing and submitted transcriptions in the EHR<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
[[#top|Top]]<br />
<br />
===V===<br />
*VPN –Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
[[#top|Top]]<br />
<br />
===W===<br />
*WAD - Working As Designed<br />
<br />
[[#top|Top]]<br />
===X===<br />
*XML - Extensible Markup Language, a computer term.<br />
<br />
[[#top|Top]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Allscripts_Enterprise_EHR_Database&diff=9167Allscripts Enterprise EHR Database2010-09-01T17:51:07Z<p>Troy.Forcier: Created page with 'TouchWorks Database is a server role with Allscripts Enterprise EHR. This roles serves to primarily store clinical data for access by the TouchWorks Web Server.'</p>
<hr />
<div>TouchWorks Database is a server role with Allscripts Enterprise EHR. This roles serves to primarily store clinical data for access by the TouchWorks Web Server.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=TouchWorks_PM&diff=9166TouchWorks PM2010-09-01T17:47:48Z<p>Troy.Forcier: Created page with 'Allscripts Enterprise PM (formerly TouchWorks PM) is a practice managment application. This application is primarily used for scheduling appointments, which are fed into AE-EHR …'</p>
<hr />
<div>Allscripts Enterprise PM (formerly TouchWorks PM) is a practice managment application. This application is primarily used for scheduling appointments, which are fed into AE-EHR using an interface.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=TouchWorks_Print_Server&diff=9165TouchWorks Print Server2010-09-01T17:33:18Z<p>Troy.Forcier: Created page with 'TouchWorks Print (or Message) Server is used for managing the following types of jobs: *Print *Fax *Eligibility *Scripts This server role often serves as the location for the D…'</p>
<hr />
<div>TouchWorks Print (or Message) Server is used for managing the following types of jobs:<br />
<br />
*Print<br />
*Fax<br />
*Eligibility<br />
*Scripts<br />
<br />
This server role often serves as the location for the Delta Service, and MedFusion.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=V11_Upgrade_Introduction&diff=8258V11 Upgrade Introduction2010-05-06T12:11:12Z<p>Troy.Forcier: /* Helpful Links */</p>
<hr />
<div>'''V11 Upgrade Introduction and Overview'''<br />
<br />
<br />
The upgrade of a system from Touchworks V10.x to Touchworks V11.x (Allscripts EHR 11.x) is not only a big change in the look and feel of the software itself, it is also a a large undertaking for your organization. The upgrade to V11 is a process can take as long as six to seven months from beginning to end. The Upgrade process begins with your team and your Allscripts Account manager working together to initiate the process, complete prerequisites and a health check of your system. <br />
<br />
<br />
After the health check is complete and your system has the green light to move forward, you are connected with your Upgrade team which may be provided by Allscripts, by Galen or a team with resources from both. The Upgrade team will consist of a Project Manager, an Upgrade Consultant, an Upgrade Tech and an Interface Tech. This team will be connected to your upgrade through the entire process and will help to support your organization's team in making a smooth transition to V11. <br />
<br />
<br />
Your organization will also have to pull together your own team to support the upgrade. Your team should include: a Project manager, a Technical Analyst/Manager, Systems Analysts, Training Coordinators, Physician Champions and Clinical Super Users. This team will work together with the Galen/Allscripts Upgrade team throughout the process of the upgrade. <br />
<br />
<br />
The Galen/Allscripts team will have knowledge and experience working with V11 Upgrades in a variety of settings from single organization settings to large MSOs. Your team will provide critical information about how you utilize the system, your clinical needs and how your practice setting will influence the build of the system. We will work together to make the upgrade a success and configure the system to best meet the needs of your users.<br />
<br />
==Helpful Links==<br />
*[[Upgrade Documents Guide]] This page is a guide to documents that you may have received from your Account Manager or Upgrade Consultant as attachments to emails in the early weeks of getting ready for your upgrade<br />
*[[Upgrade Timeline and Dependencies]]<br />
*[[System Administrator Resources]]<br />
*[[Allscripts Resources]] Describes the recorded trainings and other online resources and where to find them. Should be reviewed prior to test upgrade and can be used to augment the Galen wiki during the build. If you have a question, please check the wiki BW article first as we will place any new developments there.<br />
*[[Getting ready for Upgrade]] outlines tasks to complete before your onsite visit<br />
*[[Upgrade Interface Enablement and Validation]]<br />
*[[Keeping the Test and Live Environments in Sync]]<br />
*[[Create Role-Based Test Users]]<br />
*[[V11 Build Workbook (BW)]] Has an article for each task in the build / configuration<br />
*[[Issue Reporting for v11 Upgrade]]<br />
*[[Sample Issue Submission Form]]<br />
*[[End User Training]] shows you where to find the end user training materials mentioned in your contract<br />
*[[Provider Schedule Reduction]]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=File:CHM.jpg&diff=8241File:CHM.jpg2010-05-05T14:10:05Z<p>Troy.Forcier: </p>
<hr />
<div></div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Acronyms,_Abbreviations_%26_Other_Definitions&diff=6797Acronyms, Abbreviations & Other Definitions2009-05-04T17:40:57Z<p>Troy.Forcier: /* Acronyms */</p>
<hr />
<div>==Acronyms==<br />
Brief definitions are listed below. If there is more detailed information available or needed about a particular item, then there will be a link either from the acronym or form the real term to a page with that information.<br />
<br />
*AHIMA- American Health Information Management Association<br />
<br />
*ACI - Add Clinical Item<br />
<br />
*ADT - Admission, Discharge, Transfer<br />
<br />
*ALC - [[Allscripts Learning Center]]<br />
<br />
*AMA -American Medical Association<br />
<br />
*[[CCD]] - Continuity of Care Document<br />
<br />
*[[CDA]] - Clinical Document Architecture<br />
<br />
*[[CCR]] - Continuity of Care Record<br />
<br />
*[[CED]] - Clinical Exchange Document<br />
<br />
*[[CCI]]- Correct Coding Initiative<br />
<br />
*CG [[CareGuides]] - A large set of templates created by Allscripts for Touchworks for common medical conditions including diseases, injuries and health maintenance. <br />
<br />
*CIS - Clinical Information System, industry word. Generic term used to describe the software programs designed to capture manage and analyze health care data.<br />
<br />
*CLR - Common Language Runtime. It is Microsoft's implementation of the Common Language Infrastructure (CLI) standard, which defines an execution environment for program code. http://en.wikipedia.org/wiki/Common_Language_Runtime<br />
<br />
*CPOE - Computerized Physician Order Entry, industry term. The electronic entry by a physician of treatment instructions for patients under his or her care. These orders are communicated over a computer network to medical staff or departments responsible for fulfilling the order. http://en.wikipedia.org/wiki/CPOE<br />
<br />
*CMS - Centers for Medicare and Medicaid. Their home page http://www.cms.hhs.gov/ and more information http://en.wikipedia.org/wiki/Centers_for_Medicare_and_Medicaid_Services<br />
<br />
*[[CPT4]] - Current Procedural Terminology, 4th Edition, medical term. A standardized set of codes established by the American Medical Association to identify medical procedures performed and for billing purposes.<br />
<br />
*CDT - Clinical Desktop<br />
<br />
*[[DEA]] - Drug Enforcement Agency<br />
<br />
*[[DUR]] - Drug Utilization Review- <br />
<br />
*[[EHR]] – Electronic Health Record, industry term. A patient’s medical record in a digital format. Owned and controlled by the provider.<br />
<br />
*[[EMAR]] - Electronic Medication Administration Record<br />
<br />
*EMR – Electronic Medical Record, industry term. A patient’s medical record in a digital format.<br />
<br />
*ETL - Extract, Transform, Load<br />
<br />
*FTP – File Transfer Protocol, computer term. A network protocol for transferring files over the internet. http://en.wikipedia.org/wiki/Ftp<br />
<br />
*GUI- Graphic User Interface<br />
<br />
*[[HCPCS]]- Healthcare procedural coding system.<br />
<br />
*HEDIS- The Healthcare Effectiveness Data and Information Set-Tool used to measure performance on important dimensions of care and services.<br />
<br />
*[http://en.wikipedia.org/wiki/Health_information_exchange_(HIE) HIE] Health Information Exchange<br />
<br />
*[[HIPAA]] – Health Insurance Portability and Accountability Act, legal and medical term. Relates to the legal act of 1996. <br />
<br />
*[[HIT]]- Health Information Technology-used to improve the efficiency and quality of health care that patients receive. System where medical professionals store information ususally contained in a patients chart on a computer, rather than on paper <br />
<br />
*[[HMP]] – Health Management Plan, Allscripts Term – this is a component of the [[Clinical Desktop]] within [[Touchworks]]. It is a workspace for reviewing current orders, meds, order reminders, alerts and results for active problems <br />
<br />
*HL7- Health Level Seven - a standard development organization that supports the development and maintenance of a health data exchange protocol.<br />
<br />
*[[HTB]] – Horizontal Tool Bar the menu bar that appears horizontally across the screen.<br />
<br />
*Hx - is used in medical shorthand to mean "history"<br />
<br />
*ICD9 - International Statistical Classification of Diseases and Related Health Problems<br />
<br />
*[http://wiki.ihe.net/index.php?title=Main_Page IHE] Integrating the Healthcare Enterprise<br />
<br />
*ISO- International Organization for Standarization<br />
<br />
*IPA- Independent Practice Association-consists of a network of physicians in a region or community who agree to participate in an association to contract with health maintenance organizations, other managed care plans, and also vendors for the benefit of each of the physicians in the IPA. <br />
<br />
*KB – Allscripts Knowledge Base, Allscripts term – the knowledge base is an online resource created by Allscripts as a resource tool to support Touchworks users. <br />
<br />
*LAN-Local Area Network<br />
<br />
*LMRP - Local Medical Review Policy<br />
<br />
*[[MAR]] - Medication Administration Record<br />
<br />
*MPI - Master Patient Index - Used Interchangeably with Patient Master Index (PMI). An index that contains a unique identifier for every patient in the enterprise<br />
<br />
*[[MSO]] - Managed Services Organization or Medical Services Organization<br />
<br />
*NAW - Note Authoring Workspace<br />
<br />
*[[NDC]]-National Drug Code<br />
<br />
*[[NCQA]] - National Committee for Quality Assurance <br />
<br />
*OBR - Observation Request Segment<br />
<br />
*OCD – Orderable Concept Dictionary, Allscripts term – This is a dictionary that comes with Touchworks that is a consistent dictionary of orders and results. This was created to deal with differences in medical terminology in different locations and with different vendors. <br />
<br />
*OID – Orderable Item Dictionary, Allscripts term – This is the dictionary of things that can be ordered, received or recorded as results. These terms can vary from hospital to hospital, and are therefore mapped to items in the orderable concept dictionary for consistency. <br />
<br />
*ORM - Observation Result Messages<br />
<br />
*ORU - Observation Result Unsolicited<br />
<br />
*PACS – Picture Archiving and Communication System – used to exchange medical images over a network (X-rays, ultrasound etc.)<br />
<br />
*PAT – Physician Administration tool <br />
<br />
*PBM - Pharmacy Benefit Manager<br />
<br />
*PCP- Primary Care Provider<br />
<br />
*PHI-Personally Identifiable Health Information<br />
<br />
*PHR –Personal Health Record –owned and controlled by the patient <br />
<br />
*PM - [[Practice Management]]<br />
<br />
*[[PMS]] - Practice Management System <br />
<br />
*[[PQRI]]- Physician Quality Reporting Initiative-for 2009 consists of 153 quality measures and 7 measure groups<br />
<br />
*[[RHIO]] - A [[Regional Health Information Organization]]<br />
<br />
*RID – Resultable Item Dictionary<br />
<br />
*RIS - Radiology Information System<br />
<br />
*RCD – [[Results Concept Dictionary]]<br />
<br />
*RLS -Record Locator Service - An index that lets clinicians find out where the patient information they seek is stored so that they can request it directly from its source.<br />
<br />
*RTI- Real Time Intervention<br />
<br />
*ROI – Return on Investment<br />
*[[RX+]] – a module of Touchworks that allows clinical staff to manage their patients' medications, as well as provides tools for prescribing utilizing [[DUR]] checking and plan-specific formularies<br />
<br />
*SIG – From the Latin “Signa”, meaning to write. This is a medical abbreviation used when writing prescriptions meant to mean “write the following instructions on the label” <br />
<br />
*SIU - Schedule Information Unsolicited (message)<br />
<br />
*SSMT – Starter Set Migration Tool – this is a tool used to move items from test to live<br />
<br />
*TW – [[Touchworks]]<br />
<br />
*TWPM – Touchworks Practice Management<br />
<br />
*VPN –Virtual Private Network<br />
<br />
*[[VTB]] – Vertical Tool Bar – The tool Bar that runs up and down the screen, usually on the left hand side<br />
<br />
*WAD - Working As Designed<br />
<br />
*XML - Extensible Markup Language, a computer term.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=WEB-key&diff=6331WEB-key2009-03-16T19:43:47Z<p>Troy.Forcier: </p>
<hr />
<div>== Overview ==<br />
WEB-key is a biometrics software package from BIO-Key (www.bio-key.com) that integrates with the Allscripts Enterprise EHR.<br />
<br />
== Migrating the WEB-key database server ==<br />
# You must stop the WEB-key service and update the location<br />
# Open the WEB-key service from its System Tray icon<br>[[Image:WEB-key Config 1.jpg]]<br />
# Click Stop<br />
# Click the WEB-key DB button<br>[[Image:WEB-key Config 2.jpg]]<br />
# Specify the new database server name/IP, and any other things that changed (e.g. DB name, user, etc).<br>[[Image:WEB-key Config 3.jpg]]<br />
# Click OK<br />
# If you're done, click Start<br />
<br />
== Updating the WEB-key database type (e.g. SQL 2000 -> 2005)==<br />
# Open the WEB-key service from its System Tray icon<br />
# Click Stop<br />
# Click Uninstall - this does NOT uninstall the WEB-key software, but rather unlocks it so you can edit certain settings <br>[[Image:WEB-key Config 4.jpg]]<br />
# Select the updated database type from the Database drop down menu<br>[[Image:WEB-key Config 5.jpg]]<br />
# Click Install<br />
# Click Start, if necessary - if the Start-up Type is automatic, this step is unnecessary</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=NCQA&diff=6221NCQA2009-03-11T15:54:58Z<p>Troy.Forcier: New page: The National Committee for Quality Assurance is a private, 501(c)(3) not-for-profit organization dedicated to improving health care quality. [http://www.ncqa.org/tabid/675/Default.aspx M...</p>
<hr />
<div>The National Committee for Quality Assurance is a private, 501(c)(3) not-for-profit organization dedicated to improving health care quality. <br />
<br />
[http://www.ncqa.org/tabid/675/Default.aspx More Information]</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Q:_Does_loading_Specialty_Favorites_affect_how_favorites_are_populated_for_new_users%3F&diff=6030Q: Does loading Specialty Favorites affect how favorites are populated for new users?2009-03-04T18:11:02Z<p>Troy.Forcier: </p>
<hr />
<div>'''Q: Does loading Specialty Favorites affect how favorites are populated for new users?'''<br />
<br />
Yes. In v11, if you have no favorites but your specialty does, the first time you add a favorite, it takes in all of the favorites from the specialty and loads them into your personal "My Favorites" and then adds the one favorite you had selected. You can reference KB article 3621, p. 5 to see exactly how it works with screenshots. This should be a benefit to the provider because the specialty favorites should be populated with items that they would use frequently.</div>Troy.Forcierhttps://wiki.galenhealthcare.com/index.php?title=Q:_Who_will_be_loading_the_Specialty-specific_Favorites_into_V11.1.1_-_The_Allscripts/Galen_Upgrade_Team_or_us%3F&diff=6029Q: Who will be loading the Specialty-specific Favorites into V11.1.1 - The Allscripts/Galen Upgrade Team or us?2009-03-04T18:09:30Z<p>Troy.Forcier: </p>
<hr />
<div>Q: Who will be loading the Specialty-specific Favorites into V11.1.1 - The Allscripts/Galen Upgrade Team or us?<br />
<br />
V11 Specialty Favorites come delivered with 11.1.1 for more information see [[V11 Specialty Favorites]]<br />
<br />
The best practice for loading specialty favorites with an upgrade client is to first have the client review the pre-delivered specialty favorites and then decide to either (have Allscripts/Galen) load the pre-delivered specialty favorites and edit them in test, or to not (have Allscripts/Galen) load the pre-delivered specialty favorites and to build their own favorites lists by specialty.</div>Troy.Forcier