https://wiki.galenhealthcare.com/api.php?action=feedcontributions&user=Jon+hull&feedformat=atomGalen Healthcare Solutions - Allscripts TouchWorks EHR Wiki - User contributions [en]2024-03-29T05:11:51ZUser contributionsMediaWiki 1.35.1https://wiki.galenhealthcare.com/index.php?title=Clinical_Desktop_Configuration&diff=9776Clinical Desktop Configuration2010-12-09T20:51:07Z<p>Jon hull: </p>
<hr />
<div><!--tie this article to the assign views article in order to explain that the delivered CDV and note views are mixed in together and how to use the AHS delivered views--><br />
<!--What are the v11 upgrade AHS delivered views?--><br />
<!--What is the intention of each?--><br />
<!--Should these be used, copied and the copies used or deleted?--><br />
<!--What are each of the “worklist” views for?--><br />
<!--Calling these "worklist" views is confusing. Should they be they be renamed or deleted?--><br />
<br />
The [[Clinical Desktop]] View is a view of all of the patient information the clinician, physician or user needs to be able to care for a patient. With the Allscripts Touchworks v11 [[Clinical Desktop]] each user will have the ability to create their own view(s). <br />
<br />
'''Clinical Desktop View Starter Sets''' - Allscripts provides a standard starter set of Clinical Desktop Views; Organizations can use what’s provided, modify them or build their own view(s). <br />
<br />
'''Security''' - Users must have a security classification containing the “Workspace View Edit” security code assigned to them to be able to create or edit their Clinical Desktop Views. This security clearance will activate the “edit” button in the Clinical Desktop.<br />
<br />
'''Full Screen Display''' – At any time users can view one particular components information all by itself, by checking the box “Open in Full Screen Display”. <!--This same check box may also be used if for any reason you do not like or wish to create a layered view. No need to build layered views. (see a picture of the "Full Screen Display" view at the end of this document.)--> <!--What is the previous sentence trying to say?--><br />
<br />
== Create Clinical Desktop View==<br />
<br />
We'll configure a [[Clinical Desktop]] View using View 4.<br />
<br />
Log in to [[TouchWorks]] as an administrative user.<br />
<br />
Click Work Def Admin from the vertical toolbar.<br />
<br />
[[Image:111.jpg]]<br />
<br />
* Select Enterprise to create a view that can be assigned to users in multiple organizations<br />
* Select a specific organization to create a view that can only be assigned to users in one organization<br />
<!--need more detailed explaination of 'Enterprise/Organization' field and how it effect views that are created--><br />
<br />
From the Workspace Definition Administrations workspace click '''Add/Edit Desktop View''' on the bottom left of workspace.<br />
<br />
[[Image:222.jpg]]<br />
<br />
<br />
The Edit View Dialog window will appear.<br />
Here you’ll see the default view, which in this example is the Pediatric Patient View utilizing View 3. You will also see the 8 Views you can pick from to create a new view. <br />
<br />
[[Image:22A.jpg]]<br />
<br />
<br />
Let’s create a new view named 'Dr Heartbeat' using View 4.<br />
<br />
Click the “'''New'''…” button.<br />
The Create New View box will appear.<br />
Type in a '''New View Name'''<br />
<br />
[[Image:444.jpg]] <br />
<br />
Click '''OK'''<br />
<br />
<br />
Click on the View you’d like to create. <br />
[[Image:555.jpg]] <br />
<br />
<br />
<br />
This example uses View 4, so when chosen, view 4 appears on my screen.<br />
[[Image:666.jpg]] <br />
<br />
<br />
Next, decide which of these Components you want in each workspace. <br />
<br />
[[Image:666b.jpg]]<br />
<br />
<br />
Let’s say we want to view the following Components in the workspace on the left: Allergies, Meds/Orders and Problem. <br />
'''Check the boxes''' associated with Allergies, Meds/Orders and Problem<br />
Click the “'''Add Selected'''” button in the left side workspace.<br />
<br />
[[Image:777A.jpg]] <br />
<br />
<br />
Now I’ll add ''Health Management Plan'' and ''Chart Viewer'' in the top right workspace and ''Encounter'' and ''Patient Worklist'' in the bottom right workspace.<br />
<br />
[[Image:888a.jpg]]<br />
<br />
<br />
'''Note:''' If a Worklist View is assigned to a user, the Worklist View will be accessible from the Clinical Desktop View for that user, even if the checkbox for that view is not selected in Work Def Admin. See: [[Q: Why do Worklist Views that were not selected in Work Def Admin display in the Clinical Desktop view?]]<br />
<br />
<br />
Click '''Apply''' to save the view and stay on this page, or click '''OK''' to save view and return to the main page and Vertical Tool Bar or click '''Cancel''' to cancel the action.<br />
<br />
<br />
== Add or Remove Items from a Component ==<br />
<br />
<br />
Select the component that you would like to Add or Remove Items from by clicking on the tab. In the example I am going to Remove Items from the Health Management Plan.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 3.jpg]]<br />
<br />
<br />
Next, Check or UnCheck the Items you would like to Remove. In the example, I will Remove all Items except FlowSheets, VitalSigns/Findings, and Normative Growth.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 2.jpg]]<br />
<br />
<br />
Click Apply to Save Changes and continue Editing this View.<br />
<br />
<br />
(? add instruction to remane components, set default item, set item sort and edit buttons)<br />
<br />
(? add example how to 'split' a component by addin 2 copies, unchecking items and renaming each)<br />
<br />
(? add instruction on how to set as default view)<br />
<br />
(? add link to assign views to organizational roles)<br />
<br />
(? add link to assign views to individual users)<br />
<br />
== Full Screen Display view ==<br />
<br />
<br />
This view allows you to view one component's information at a time. <br />
Simply, check the "Open in Full SCreen Display" and then click on the component you'd like to open for viewing.<br />
<br />
[[Image:999.jpg]]<br />
<br />
<br />
<br />
== Adding Buttons to Views ==<br />
<br />
Allscripts does a good job at delivering the most useful buttons for each component in the Clinical Desktop. <br><br />
Sometimes you may want to remove or add buttons to the bar to suit your needs. <br />
<br />
[[File:CED.JPG]]<br />
<br />
<br />
<br />
Navigate to Work Def Admin > Add/Edit Desktop View <BR><br />
1) Select the View you want to modify <BR><br />
2) Click on the component you want to modify the buttons for <br><br />
3) Click on Define Buttons<br />
<br />
<br />
[[File:CED2.JPG]]<br />
<br />
<br />
Once in the Customizer you can see all the available commands by going to the Commands tab <BR><br />
In this example we are going to add the Task command to the Chart Viewer <br><br />
<br />
[[File:Commands.JPG]]<br />
<br />
<br />
From the Commands tab click on the Rearrange Commands... button <br><br />
1) Select Toolbar- Button Toolbar<br><br />
2) Click Add... <br><br />
<br />
<br />
[[File:Command2.JPG]]<br />
<br />
<br />
3)Select the Command you want to add <br><br />
4)Click OK <br><br />
<br />
<br />
[[File:Command3.JPG]]<br />
<br />
<br />
5) You can now move the item(s) by selecting them and using the Move Up/Move Down buttons <br><br />
6) When complete click Close <br><br />
<br />
<br />
[[File:Command4.JPG]]<br />
<br />
<br />
7) You will now see your new button added to the toolbar<br><br />
8) Click Close <br><br />
<br />
<br />
[[File:Command5.JPG]]<br />
<br />
<br />
9) '''IMPORTANT''' you must click Apply! <br><br />
<br />
<br />
[[File:Command6.JPG]]<br />
<br />
<br />
10) Log out and back into EEHR to see your new toolbar<br />
<br />
<br />
==Removing Buttons from Views==<br />
<br />
This process is very similar to adding buttons. Follow steps 1-3 above. <br><br />
4) right click the item you want to remove and select Delete <br><br />
5) Click Close<br />
<br />
<br />
[[File:Delete.JPG]]<br />
<br />
<br />
6) '''IMPORTANT''' you must click Apply! <br><br />
<br />
<br />
[[File:Command6.JPG]]<br />
<br />
<br />
7) Log out and back into EEHR to see your new toolbar<br />
<br />
<br />
==How to remove Views==<br />
<br />
To remove a view you created and no longer need<br />
<br />
<br />
'''Important!''' -Both Desktop Views and Note Views populate the list together. If you try to delete a view in the following steps using the Add/Edit Desktop View button, but don't see it in the list then its under Add/Edit Note View.<br />
<br />
<br />
[[Image:Deleteworkspace4.jpg]]<br />
<br />
<br />
First- Select whether the view you want to delete/edit is an Enterprise or Organization view<br />
<br />
[[Image:Deleteworkspace3.jpg]]<br />
<br />
<br />
Next- select the view you wish to delete and make sure it is not assigned to any users <br />
<br />
[[Image:Deleteworkspace5.jpg]]<br />
<br />
<br />
Then- click the Add/Edit Desktop View or Add/Edit Note View depending on which type you wish to delete/edit<br />
<br />
[[Image:Deleteworkspace.JPG]]<br />
<br />
<br />
If you are in the right view editor (Desktop vs. Note), your selected view will be showing in the list- click the delete button to delete<br />
<br />
[[Image:Deleteworkspace2.jpg]]<br />
<br />
Your view is now deleted!</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Delete.JPG&diff=9775File:Delete.JPG2010-12-09T20:49:39Z<p>Jon hull: uploaded a new version of &quot;File:Delete.JPG&quot;</p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Delete.JPG&diff=9774File:Delete.JPG2010-12-09T20:47:18Z<p>Jon hull: uploaded a new version of &quot;File:Delete.JPG&quot;</p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Delete.JPG&diff=9773File:Delete.JPG2010-12-09T20:45:40Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Clinical_Desktop_Configuration&diff=9772Clinical Desktop Configuration2010-12-09T20:40:27Z<p>Jon hull: /* Adding Buttons to Views */</p>
<hr />
<div><!--tie this article to the assign views article in order to explain that the delivered CDV and note views are mixed in together and how to use the AHS delivered views--><br />
<!--What are the v11 upgrade AHS delivered views?--><br />
<!--What is the intention of each?--><br />
<!--Should these be used, copied and the copies used or deleted?--><br />
<!--What are each of the “worklist” views for?--><br />
<!--Calling these "worklist" views is confusing. Should they be they be renamed or deleted?--><br />
<br />
The [[Clinical Desktop]] View is a view of all of the patient information the clinician, physician or user needs to be able to care for a patient. With the Allscripts Touchworks v11 [[Clinical Desktop]] each user will have the ability to create their own view(s). <br />
<br />
'''Clinical Desktop View Starter Sets''' - Allscripts provides a standard starter set of Clinical Desktop Views; Organizations can use what’s provided, modify them or build their own view(s). <br />
<br />
'''Security''' - Users must have a security classification containing the “Workspace View Edit” security code assigned to them to be able to create or edit their Clinical Desktop Views. This security clearance will activate the “edit” button in the Clinical Desktop.<br />
<br />
'''Full Screen Display''' – At any time users can view one particular components information all by itself, by checking the box “Open in Full Screen Display”. <!--This same check box may also be used if for any reason you do not like or wish to create a layered view. No need to build layered views. (see a picture of the "Full Screen Display" view at the end of this document.)--> <!--What is the previous sentence trying to say?--><br />
<br />
== Create Clinical Desktop View==<br />
<br />
We'll configure a [[Clinical Desktop]] View using View 4.<br />
<br />
Log in to [[TouchWorks]] as an administrative user.<br />
<br />
Click Work Def Admin from the vertical toolbar.<br />
<br />
[[Image:111.jpg]]<br />
<br />
* Select Enterprise to create a view that can be assigned to users in multiple organizations<br />
* Select a specific organization to create a view that can only be assigned to users in one organization<br />
<!--need more detailed explaination of 'Enterprise/Organization' field and how it effect views that are created--><br />
<br />
From the Workspace Definition Administrations workspace click '''Add/Edit Desktop View''' on the bottom left of workspace.<br />
<br />
[[Image:222.jpg]]<br />
<br />
<br />
The Edit View Dialog window will appear.<br />
Here you’ll see the default view, which in this example is the Pediatric Patient View utilizing View 3. You will also see the 8 Views you can pick from to create a new view. <br />
<br />
[[Image:22A.jpg]]<br />
<br />
<br />
Let’s create a new view named 'Dr Heartbeat' using View 4.<br />
<br />
Click the “'''New'''…” button.<br />
The Create New View box will appear.<br />
Type in a '''New View Name'''<br />
<br />
[[Image:444.jpg]] <br />
<br />
Click '''OK'''<br />
<br />
<br />
Click on the View you’d like to create. <br />
[[Image:555.jpg]] <br />
<br />
<br />
<br />
This example uses View 4, so when chosen, view 4 appears on my screen.<br />
[[Image:666.jpg]] <br />
<br />
<br />
Next, decide which of these Components you want in each workspace. <br />
<br />
[[Image:666b.jpg]]<br />
<br />
<br />
Let’s say we want to view the following Components in the workspace on the left: Allergies, Meds/Orders and Problem. <br />
'''Check the boxes''' associated with Allergies, Meds/Orders and Problem<br />
Click the “'''Add Selected'''” button in the left side workspace.<br />
<br />
[[Image:777A.jpg]] <br />
<br />
<br />
Now I’ll add ''Health Management Plan'' and ''Chart Viewer'' in the top right workspace and ''Encounter'' and ''Patient Worklist'' in the bottom right workspace.<br />
<br />
[[Image:888a.jpg]]<br />
<br />
<br />
'''Note:''' If a Worklist View is assigned to a user, the Worklist View will be accessible from the Clinical Desktop View for that user, even if the checkbox for that view is not selected in Work Def Admin. See: [[Q: Why do Worklist Views that were not selected in Work Def Admin display in the Clinical Desktop view?]]<br />
<br />
<br />
Click '''Apply''' to save the view and stay on this page, or click '''OK''' to save view and return to the main page and Vertical Tool Bar or click '''Cancel''' to cancel the action.<br />
<br />
<br />
== Add or Remove Items from a Component ==<br />
<br />
<br />
Select the component that you would like to Add or Remove Items from by clicking on the tab. In the example I am going to Remove Items from the Health Management Plan.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 3.jpg]]<br />
<br />
<br />
Next, Check or UnCheck the Items you would like to Remove. In the example, I will Remove all Items except FlowSheets, VitalSigns/Findings, and Normative Growth.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 2.jpg]]<br />
<br />
<br />
Click Apply to Save Changes and continue Editing this View.<br />
<br />
<br />
(? add instruction to remane components, set default item, set item sort and edit buttons)<br />
<br />
(? add example how to 'split' a component by addin 2 copies, unchecking items and renaming each)<br />
<br />
(? add instruction on how to set as default view)<br />
<br />
(? add link to assign views to organizational roles)<br />
<br />
(? add link to assign views to individual users)<br />
<br />
== Full Screen Display view ==<br />
<br />
<br />
This view allows you to view one component's information at a time. <br />
Simply, check the "Open in Full SCreen Display" and then click on the component you'd like to open for viewing.<br />
<br />
[[Image:999.jpg]]<br />
<br />
<br />
<br />
== Adding Buttons to Views ==<br />
<br />
Allscripts does a good job at delivering the most useful buttons for each component in the Clinical Desktop. <br><br />
Sometimes you may want to remove or add buttons to the bar to suit your needs. <br />
<br />
[[File:CED.JPG]]<br />
<br />
<br />
<br />
Navigate to Work Def Admin > Add/Edit Desktop View <BR><br />
1) Select the View you want to modify <BR><br />
2) Click on the component you want to modify the buttons for <br><br />
3) Click on Define Buttons<br />
<br />
<br />
[[File:CED2.JPG]]<br />
<br />
<br />
Once in the Customizer you can see all the available commands by going to the Commands tab <BR><br />
In this example we are going to add the Task command to the Chart Viewer <br><br />
<br />
[[File:Commands.JPG]]<br />
<br />
<br />
From the Commands tab click on the Rearrange Commands... button <br><br />
1) Select Toolbar- Button Toolbar<br><br />
2) Click Add... <br><br />
<br />
<br />
[[File:Command2.JPG]]<br />
<br />
<br />
3)Select the Command you want to add <br><br />
4)Click OK <br><br />
<br />
<br />
[[File:Command3.JPG]]<br />
<br />
<br />
5) You can now move the item(s) by selecting them and using the Move Up/Move Down buttons <br><br />
6) When complete click Close <br><br />
<br />
<br />
[[File:Command4.JPG]]<br />
<br />
<br />
7) You will now see your new button added to the toolbar<br><br />
8) Click Close <br><br />
<br />
<br />
[[File:Command5.JPG]]<br />
<br />
<br />
9) '''IMPORTANT''' you must click Apply <br><br />
<br />
<br />
[[File:Command6.JPG]]<br />
<br />
<br />
10) Log out and back into EEHR to see your new toolbar<br />
<br />
==How to remove Views==<br />
<br />
To remove a view you created and no longer need<br />
<br />
<br />
'''Important!''' -Both Desktop Views and Note Views populate the list together. If you try to delete a view in the following steps using the Add/Edit Desktop View button, but don't see it in the list then its under Add/Edit Note View.<br />
<br />
<br />
[[Image:Deleteworkspace4.jpg]]<br />
<br />
<br />
First- Select whether the view you want to delete/edit is an Enterprise or Organization view<br />
<br />
[[Image:Deleteworkspace3.jpg]]<br />
<br />
<br />
Next- select the view you wish to delete and make sure it is not assigned to any users <br />
<br />
[[Image:Deleteworkspace5.jpg]]<br />
<br />
<br />
Then- click the Add/Edit Desktop View or Add/Edit Note View depending on which type you wish to delete/edit<br />
<br />
[[Image:Deleteworkspace.JPG]]<br />
<br />
<br />
If you are in the right view editor (Desktop vs. Note), your selected view will be showing in the list- click the delete button to delete<br />
<br />
[[Image:Deleteworkspace2.jpg]]<br />
<br />
Your view is now deleted!</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Clinical_Desktop_Configuration&diff=9771Clinical Desktop Configuration2010-12-09T20:39:30Z<p>Jon hull: /* Adding/Removing Buttons from Views */</p>
<hr />
<div><!--tie this article to the assign views article in order to explain that the delivered CDV and note views are mixed in together and how to use the AHS delivered views--><br />
<!--What are the v11 upgrade AHS delivered views?--><br />
<!--What is the intention of each?--><br />
<!--Should these be used, copied and the copies used or deleted?--><br />
<!--What are each of the “worklist” views for?--><br />
<!--Calling these "worklist" views is confusing. Should they be they be renamed or deleted?--><br />
<br />
The [[Clinical Desktop]] View is a view of all of the patient information the clinician, physician or user needs to be able to care for a patient. With the Allscripts Touchworks v11 [[Clinical Desktop]] each user will have the ability to create their own view(s). <br />
<br />
'''Clinical Desktop View Starter Sets''' - Allscripts provides a standard starter set of Clinical Desktop Views; Organizations can use what’s provided, modify them or build their own view(s). <br />
<br />
'''Security''' - Users must have a security classification containing the “Workspace View Edit” security code assigned to them to be able to create or edit their Clinical Desktop Views. This security clearance will activate the “edit” button in the Clinical Desktop.<br />
<br />
'''Full Screen Display''' – At any time users can view one particular components information all by itself, by checking the box “Open in Full Screen Display”. <!--This same check box may also be used if for any reason you do not like or wish to create a layered view. No need to build layered views. (see a picture of the "Full Screen Display" view at the end of this document.)--> <!--What is the previous sentence trying to say?--><br />
<br />
== Create Clinical Desktop View==<br />
<br />
We'll configure a [[Clinical Desktop]] View using View 4.<br />
<br />
Log in to [[TouchWorks]] as an administrative user.<br />
<br />
Click Work Def Admin from the vertical toolbar.<br />
<br />
[[Image:111.jpg]]<br />
<br />
* Select Enterprise to create a view that can be assigned to users in multiple organizations<br />
* Select a specific organization to create a view that can only be assigned to users in one organization<br />
<!--need more detailed explaination of 'Enterprise/Organization' field and how it effect views that are created--><br />
<br />
From the Workspace Definition Administrations workspace click '''Add/Edit Desktop View''' on the bottom left of workspace.<br />
<br />
[[Image:222.jpg]]<br />
<br />
<br />
The Edit View Dialog window will appear.<br />
Here you’ll see the default view, which in this example is the Pediatric Patient View utilizing View 3. You will also see the 8 Views you can pick from to create a new view. <br />
<br />
[[Image:22A.jpg]]<br />
<br />
<br />
Let’s create a new view named 'Dr Heartbeat' using View 4.<br />
<br />
Click the “'''New'''…” button.<br />
The Create New View box will appear.<br />
Type in a '''New View Name'''<br />
<br />
[[Image:444.jpg]] <br />
<br />
Click '''OK'''<br />
<br />
<br />
Click on the View you’d like to create. <br />
[[Image:555.jpg]] <br />
<br />
<br />
<br />
This example uses View 4, so when chosen, view 4 appears on my screen.<br />
[[Image:666.jpg]] <br />
<br />
<br />
Next, decide which of these Components you want in each workspace. <br />
<br />
[[Image:666b.jpg]]<br />
<br />
<br />
Let’s say we want to view the following Components in the workspace on the left: Allergies, Meds/Orders and Problem. <br />
'''Check the boxes''' associated with Allergies, Meds/Orders and Problem<br />
Click the “'''Add Selected'''” button in the left side workspace.<br />
<br />
[[Image:777A.jpg]] <br />
<br />
<br />
Now I’ll add ''Health Management Plan'' and ''Chart Viewer'' in the top right workspace and ''Encounter'' and ''Patient Worklist'' in the bottom right workspace.<br />
<br />
[[Image:888a.jpg]]<br />
<br />
<br />
'''Note:''' If a Worklist View is assigned to a user, the Worklist View will be accessible from the Clinical Desktop View for that user, even if the checkbox for that view is not selected in Work Def Admin. See: [[Q: Why do Worklist Views that were not selected in Work Def Admin display in the Clinical Desktop view?]]<br />
<br />
<br />
Click '''Apply''' to save the view and stay on this page, or click '''OK''' to save view and return to the main page and Vertical Tool Bar or click '''Cancel''' to cancel the action.<br />
<br />
<br />
== Add or Remove Items from a Component ==<br />
<br />
<br />
Select the component that you would like to Add or Remove Items from by clicking on the tab. In the example I am going to Remove Items from the Health Management Plan.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 3.jpg]]<br />
<br />
<br />
Next, Check or UnCheck the Items you would like to Remove. In the example, I will Remove all Items except FlowSheets, VitalSigns/Findings, and Normative Growth.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 2.jpg]]<br />
<br />
<br />
Click Apply to Save Changes and continue Editing this View.<br />
<br />
<br />
(? add instruction to remane components, set default item, set item sort and edit buttons)<br />
<br />
(? add example how to 'split' a component by addin 2 copies, unchecking items and renaming each)<br />
<br />
(? add instruction on how to set as default view)<br />
<br />
(? add link to assign views to organizational roles)<br />
<br />
(? add link to assign views to individual users)<br />
<br />
== Full Screen Display view ==<br />
<br />
<br />
This view allows you to view one component's information at a time. <br />
Simply, check the "Open in Full SCreen Display" and then click on the component you'd like to open for viewing.<br />
<br />
[[Image:999.jpg]]<br />
<br />
<br />
<br />
== Adding Buttons to Views ==<br />
<br />
Allscripts does a good job at delivering the most useful buttons for each component in the Clinical Desktop. <br><br />
Sometimes you may want to remove or add buttons to the bar to suit your needs. <br />
<br />
[[File:CED.JPG]]<br />
<br />
<br />
<br />
Navigate to Work Def Admin > Add/Edit Desktop View <BR><br />
1) Select the View you want to modify <BR><br />
2) Click on the component you want to modify the buttons for <br><br />
3) Click on Define Buttons<br />
<br />
<br />
[[File:CED2.JPG]]<br />
<br />
<br />
Once in the Customizer you can see all the available commands by going to the Commands tab <BR><br />
In this example we are going to add the Task command to the Chart Viewer <br><br />
<br />
[[File:Commands.JPG]]<br />
<br />
<br />
From the Commands tab click on the Rearrange Commands... button <br><br />
1) Select Toolbar- Button Toolbar<br><br />
2) Click Add... <br><br />
<br />
<br />
[[File:Command2.JPG]]<br />
<br />
<br />
3)Select the Command you want to add <br><br />
4)Click OK <br><br />
<br />
<br />
[[File:Command3.JPG]]<br />
<br />
<br />
5) You can now move the item(s) by selecting them and using the Move Up/Move Down buttons <br><br />
6) When complete click Close <br><br />
<br />
<br />
[[File:Command4.JPG]]<br />
<br />
<br />
7) You will now see your new button added to the toolbar<br><br />
8) Click Close <br><br />
<br />
<br />
[[File:Command5.JPG]]<br />
<br />
<br />
9) '''IMPORTANT''' you must click Apply <br><br />
10) Log out and back into EEHR to see your new toolbar<br />
<br />
==How to remove Views==<br />
<br />
To remove a view you created and no longer need<br />
<br />
<br />
'''Important!''' -Both Desktop Views and Note Views populate the list together. If you try to delete a view in the following steps using the Add/Edit Desktop View button, but don't see it in the list then its under Add/Edit Note View.<br />
<br />
<br />
[[Image:Deleteworkspace4.jpg]]<br />
<br />
<br />
First- Select whether the view you want to delete/edit is an Enterprise or Organization view<br />
<br />
[[Image:Deleteworkspace3.jpg]]<br />
<br />
<br />
Next- select the view you wish to delete and make sure it is not assigned to any users <br />
<br />
[[Image:Deleteworkspace5.jpg]]<br />
<br />
<br />
Then- click the Add/Edit Desktop View or Add/Edit Note View depending on which type you wish to delete/edit<br />
<br />
[[Image:Deleteworkspace.JPG]]<br />
<br />
<br />
If you are in the right view editor (Desktop vs. Note), your selected view will be showing in the list- click the delete button to delete<br />
<br />
[[Image:Deleteworkspace2.jpg]]<br />
<br />
Your view is now deleted!</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Command6.JPG&diff=9770File:Command6.JPG2010-12-09T20:38:40Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Command5.JPG&diff=9769File:Command5.JPG2010-12-09T20:36:03Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Command4.JPG&diff=9768File:Command4.JPG2010-12-09T20:33:13Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Clinical_Desktop_Configuration&diff=9767Clinical Desktop Configuration2010-12-09T20:23:26Z<p>Jon hull: /* Adding/Removing Buttons from Views */</p>
<hr />
<div><!--tie this article to the assign views article in order to explain that the delivered CDV and note views are mixed in together and how to use the AHS delivered views--><br />
<!--What are the v11 upgrade AHS delivered views?--><br />
<!--What is the intention of each?--><br />
<!--Should these be used, copied and the copies used or deleted?--><br />
<!--What are each of the “worklist” views for?--><br />
<!--Calling these "worklist" views is confusing. Should they be they be renamed or deleted?--><br />
<br />
The [[Clinical Desktop]] View is a view of all of the patient information the clinician, physician or user needs to be able to care for a patient. With the Allscripts Touchworks v11 [[Clinical Desktop]] each user will have the ability to create their own view(s). <br />
<br />
'''Clinical Desktop View Starter Sets''' - Allscripts provides a standard starter set of Clinical Desktop Views; Organizations can use what’s provided, modify them or build their own view(s). <br />
<br />
'''Security''' - Users must have a security classification containing the “Workspace View Edit” security code assigned to them to be able to create or edit their Clinical Desktop Views. This security clearance will activate the “edit” button in the Clinical Desktop.<br />
<br />
'''Full Screen Display''' – At any time users can view one particular components information all by itself, by checking the box “Open in Full Screen Display”. <!--This same check box may also be used if for any reason you do not like or wish to create a layered view. No need to build layered views. (see a picture of the "Full Screen Display" view at the end of this document.)--> <!--What is the previous sentence trying to say?--><br />
<br />
== Create Clinical Desktop View==<br />
<br />
We'll configure a [[Clinical Desktop]] View using View 4.<br />
<br />
Log in to [[TouchWorks]] as an administrative user.<br />
<br />
Click Work Def Admin from the vertical toolbar.<br />
<br />
[[Image:111.jpg]]<br />
<br />
* Select Enterprise to create a view that can be assigned to users in multiple organizations<br />
* Select a specific organization to create a view that can only be assigned to users in one organization<br />
<!--need more detailed explaination of 'Enterprise/Organization' field and how it effect views that are created--><br />
<br />
From the Workspace Definition Administrations workspace click '''Add/Edit Desktop View''' on the bottom left of workspace.<br />
<br />
[[Image:222.jpg]]<br />
<br />
<br />
The Edit View Dialog window will appear.<br />
Here you’ll see the default view, which in this example is the Pediatric Patient View utilizing View 3. You will also see the 8 Views you can pick from to create a new view. <br />
<br />
[[Image:22A.jpg]]<br />
<br />
<br />
Let’s create a new view named 'Dr Heartbeat' using View 4.<br />
<br />
Click the “'''New'''…” button.<br />
The Create New View box will appear.<br />
Type in a '''New View Name'''<br />
<br />
[[Image:444.jpg]] <br />
<br />
Click '''OK'''<br />
<br />
<br />
Click on the View you’d like to create. <br />
[[Image:555.jpg]] <br />
<br />
<br />
<br />
This example uses View 4, so when chosen, view 4 appears on my screen.<br />
[[Image:666.jpg]] <br />
<br />
<br />
Next, decide which of these Components you want in each workspace. <br />
<br />
[[Image:666b.jpg]]<br />
<br />
<br />
Let’s say we want to view the following Components in the workspace on the left: Allergies, Meds/Orders and Problem. <br />
'''Check the boxes''' associated with Allergies, Meds/Orders and Problem<br />
Click the “'''Add Selected'''” button in the left side workspace.<br />
<br />
[[Image:777A.jpg]] <br />
<br />
<br />
Now I’ll add ''Health Management Plan'' and ''Chart Viewer'' in the top right workspace and ''Encounter'' and ''Patient Worklist'' in the bottom right workspace.<br />
<br />
[[Image:888a.jpg]]<br />
<br />
<br />
'''Note:''' If a Worklist View is assigned to a user, the Worklist View will be accessible from the Clinical Desktop View for that user, even if the checkbox for that view is not selected in Work Def Admin. See: [[Q: Why do Worklist Views that were not selected in Work Def Admin display in the Clinical Desktop view?]]<br />
<br />
<br />
Click '''Apply''' to save the view and stay on this page, or click '''OK''' to save view and return to the main page and Vertical Tool Bar or click '''Cancel''' to cancel the action.<br />
<br />
<br />
== Add or Remove Items from a Component ==<br />
<br />
<br />
Select the component that you would like to Add or Remove Items from by clicking on the tab. In the example I am going to Remove Items from the Health Management Plan.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 3.jpg]]<br />
<br />
<br />
Next, Check or UnCheck the Items you would like to Remove. In the example, I will Remove all Items except FlowSheets, VitalSigns/Findings, and Normative Growth.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 2.jpg]]<br />
<br />
<br />
Click Apply to Save Changes and continue Editing this View.<br />
<br />
<br />
(? add instruction to remane components, set default item, set item sort and edit buttons)<br />
<br />
(? add example how to 'split' a component by addin 2 copies, unchecking items and renaming each)<br />
<br />
(? add instruction on how to set as default view)<br />
<br />
(? add link to assign views to organizational roles)<br />
<br />
(? add link to assign views to individual users)<br />
<br />
== Full Screen Display view ==<br />
<br />
<br />
This view allows you to view one component's information at a time. <br />
Simply, check the "Open in Full SCreen Display" and then click on the component you'd like to open for viewing.<br />
<br />
[[Image:999.jpg]]<br />
<br />
<br />
<br />
== Adding/Removing Buttons from Views ==<br />
<br />
Allscripts does a good job at delivering the most useful buttons for each component in the Clinical Desktop. <br><br />
Sometimes you may want to remove or add buttons to the bar to suit your needs. <br />
<br />
[[File:CED.JPG]]<br />
<br />
<br />
<br />
Navigate to Work Def Admin > Add/Edit Desktop View <BR><br />
1) Select the View you want to modify <BR><br />
2) Click on the component you want to modify the buttons for <br><br />
3) Click on Define Buttons<br />
<br />
<br />
[[File:CED2.JPG]]<br />
<br />
<br />
Once in the Customizer you can see all the available commands by going to the Commands tab <BR><br />
In this example we are going to add the Task command to the Chart Viewer <br><br />
<br />
[[File:Commands.JPG]]<br />
<br />
<br />
From the Commands tab click on the Rearrange Commands... button <br><br />
1) Select Toolbar- Button Toolbar<br><br />
2) Click Add... <br><br />
<br />
<br />
[[File:Command2.JPG]]<br />
<br />
<br />
3)Select the Command you want to add <br><br />
4)Click OK<br />
<br />
<br />
[[File:Command3.JPG]]<br />
<br />
==How to remove Views==<br />
<br />
To remove a view you created and no longer need<br />
<br />
<br />
'''Important!''' -Both Desktop Views and Note Views populate the list together. If you try to delete a view in the following steps using the Add/Edit Desktop View button, but don't see it in the list then its under Add/Edit Note View.<br />
<br />
<br />
[[Image:Deleteworkspace4.jpg]]<br />
<br />
<br />
First- Select whether the view you want to delete/edit is an Enterprise or Organization view<br />
<br />
[[Image:Deleteworkspace3.jpg]]<br />
<br />
<br />
Next- select the view you wish to delete and make sure it is not assigned to any users <br />
<br />
[[Image:Deleteworkspace5.jpg]]<br />
<br />
<br />
Then- click the Add/Edit Desktop View or Add/Edit Note View depending on which type you wish to delete/edit<br />
<br />
[[Image:Deleteworkspace.JPG]]<br />
<br />
<br />
If you are in the right view editor (Desktop vs. Note), your selected view will be showing in the list- click the delete button to delete<br />
<br />
[[Image:Deleteworkspace2.jpg]]<br />
<br />
Your view is now deleted!</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Command3.JPG&diff=9766File:Command3.JPG2010-12-09T20:23:12Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Command2.JPG&diff=9765File:Command2.JPG2010-12-09T20:20:59Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Commands.JPG&diff=9764File:Commands.JPG2010-12-09T20:17:09Z<p>Jon hull: uploaded a new version of &quot;File:Commands.JPG&quot;</p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Clinical_Desktop_Configuration&diff=9763Clinical Desktop Configuration2010-12-09T20:15:07Z<p>Jon hull: /* Adding/Removing Buttons from Views */</p>
<hr />
<div><!--tie this article to the assign views article in order to explain that the delivered CDV and note views are mixed in together and how to use the AHS delivered views--><br />
<!--What are the v11 upgrade AHS delivered views?--><br />
<!--What is the intention of each?--><br />
<!--Should these be used, copied and the copies used or deleted?--><br />
<!--What are each of the “worklist” views for?--><br />
<!--Calling these "worklist" views is confusing. Should they be they be renamed or deleted?--><br />
<br />
The [[Clinical Desktop]] View is a view of all of the patient information the clinician, physician or user needs to be able to care for a patient. With the Allscripts Touchworks v11 [[Clinical Desktop]] each user will have the ability to create their own view(s). <br />
<br />
'''Clinical Desktop View Starter Sets''' - Allscripts provides a standard starter set of Clinical Desktop Views; Organizations can use what’s provided, modify them or build their own view(s). <br />
<br />
'''Security''' - Users must have a security classification containing the “Workspace View Edit” security code assigned to them to be able to create or edit their Clinical Desktop Views. This security clearance will activate the “edit” button in the Clinical Desktop.<br />
<br />
'''Full Screen Display''' – At any time users can view one particular components information all by itself, by checking the box “Open in Full Screen Display”. <!--This same check box may also be used if for any reason you do not like or wish to create a layered view. No need to build layered views. (see a picture of the "Full Screen Display" view at the end of this document.)--> <!--What is the previous sentence trying to say?--><br />
<br />
== Create Clinical Desktop View==<br />
<br />
We'll configure a [[Clinical Desktop]] View using View 4.<br />
<br />
Log in to [[TouchWorks]] as an administrative user.<br />
<br />
Click Work Def Admin from the vertical toolbar.<br />
<br />
[[Image:111.jpg]]<br />
<br />
* Select Enterprise to create a view that can be assigned to users in multiple organizations<br />
* Select a specific organization to create a view that can only be assigned to users in one organization<br />
<!--need more detailed explaination of 'Enterprise/Organization' field and how it effect views that are created--><br />
<br />
From the Workspace Definition Administrations workspace click '''Add/Edit Desktop View''' on the bottom left of workspace.<br />
<br />
[[Image:222.jpg]]<br />
<br />
<br />
The Edit View Dialog window will appear.<br />
Here you’ll see the default view, which in this example is the Pediatric Patient View utilizing View 3. You will also see the 8 Views you can pick from to create a new view. <br />
<br />
[[Image:22A.jpg]]<br />
<br />
<br />
Let’s create a new view named 'Dr Heartbeat' using View 4.<br />
<br />
Click the “'''New'''…” button.<br />
The Create New View box will appear.<br />
Type in a '''New View Name'''<br />
<br />
[[Image:444.jpg]] <br />
<br />
Click '''OK'''<br />
<br />
<br />
Click on the View you’d like to create. <br />
[[Image:555.jpg]] <br />
<br />
<br />
<br />
This example uses View 4, so when chosen, view 4 appears on my screen.<br />
[[Image:666.jpg]] <br />
<br />
<br />
Next, decide which of these Components you want in each workspace. <br />
<br />
[[Image:666b.jpg]]<br />
<br />
<br />
Let’s say we want to view the following Components in the workspace on the left: Allergies, Meds/Orders and Problem. <br />
'''Check the boxes''' associated with Allergies, Meds/Orders and Problem<br />
Click the “'''Add Selected'''” button in the left side workspace.<br />
<br />
[[Image:777A.jpg]] <br />
<br />
<br />
Now I’ll add ''Health Management Plan'' and ''Chart Viewer'' in the top right workspace and ''Encounter'' and ''Patient Worklist'' in the bottom right workspace.<br />
<br />
[[Image:888a.jpg]]<br />
<br />
<br />
'''Note:''' If a Worklist View is assigned to a user, the Worklist View will be accessible from the Clinical Desktop View for that user, even if the checkbox for that view is not selected in Work Def Admin. See: [[Q: Why do Worklist Views that were not selected in Work Def Admin display in the Clinical Desktop view?]]<br />
<br />
<br />
Click '''Apply''' to save the view and stay on this page, or click '''OK''' to save view and return to the main page and Vertical Tool Bar or click '''Cancel''' to cancel the action.<br />
<br />
<br />
== Add or Remove Items from a Component ==<br />
<br />
<br />
Select the component that you would like to Add or Remove Items from by clicking on the tab. In the example I am going to Remove Items from the Health Management Plan.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 3.jpg]]<br />
<br />
<br />
Next, Check or UnCheck the Items you would like to Remove. In the example, I will Remove all Items except FlowSheets, VitalSigns/Findings, and Normative Growth.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 2.jpg]]<br />
<br />
<br />
Click Apply to Save Changes and continue Editing this View.<br />
<br />
<br />
(? add instruction to remane components, set default item, set item sort and edit buttons)<br />
<br />
(? add example how to 'split' a component by addin 2 copies, unchecking items and renaming each)<br />
<br />
(? add instruction on how to set as default view)<br />
<br />
(? add link to assign views to organizational roles)<br />
<br />
(? add link to assign views to individual users)<br />
<br />
== Full Screen Display view ==<br />
<br />
<br />
This view allows you to view one component's information at a time. <br />
Simply, check the "Open in Full SCreen Display" and then click on the component you'd like to open for viewing.<br />
<br />
[[Image:999.jpg]]<br />
<br />
<br />
<br />
== Adding/Removing Buttons from Views ==<br />
<br />
Allscripts does a good job at delivering the most useful buttons for each component in the Clinical Desktop. <br><br />
Sometimes you may want to remove or add buttons to the bar to suit your needs. <br />
<br />
[[File:CED.JPG]]<br />
<br />
<br />
<br />
Navigate to Work Def Admin > Add/Edit Desktop View <BR><br />
1) Select the View you want to modify <BR><br />
2) Click on the component you want to modify the buttons for <br><br />
3) Click on Define Buttons<br />
<br />
<br />
[[File:CED2.JPG]]<br />
<br />
<br />
Once in the Customizer you can see all the available commands by going to the Commands tab <BR><br />
In this example we are going to add the Task command to the Chart Viewer <br><br />
<br />
[[File:COMMAND.JPG]]<br />
<br />
==How to remove Views==<br />
<br />
To remove a view you created and no longer need<br />
<br />
<br />
'''Important!''' -Both Desktop Views and Note Views populate the list together. If you try to delete a view in the following steps using the Add/Edit Desktop View button, but don't see it in the list then its under Add/Edit Note View.<br />
<br />
<br />
[[Image:Deleteworkspace4.jpg]]<br />
<br />
<br />
First- Select whether the view you want to delete/edit is an Enterprise or Organization view<br />
<br />
[[Image:Deleteworkspace3.jpg]]<br />
<br />
<br />
Next- select the view you wish to delete and make sure it is not assigned to any users <br />
<br />
[[Image:Deleteworkspace5.jpg]]<br />
<br />
<br />
Then- click the Add/Edit Desktop View or Add/Edit Note View depending on which type you wish to delete/edit<br />
<br />
[[Image:Deleteworkspace.JPG]]<br />
<br />
<br />
If you are in the right view editor (Desktop vs. Note), your selected view will be showing in the list- click the delete button to delete<br />
<br />
[[Image:Deleteworkspace2.jpg]]<br />
<br />
Your view is now deleted!</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Clinical_Desktop_Configuration&diff=9762Clinical Desktop Configuration2010-12-09T20:14:13Z<p>Jon hull: </p>
<hr />
<div><!--tie this article to the assign views article in order to explain that the delivered CDV and note views are mixed in together and how to use the AHS delivered views--><br />
<!--What are the v11 upgrade AHS delivered views?--><br />
<!--What is the intention of each?--><br />
<!--Should these be used, copied and the copies used or deleted?--><br />
<!--What are each of the “worklist” views for?--><br />
<!--Calling these "worklist" views is confusing. Should they be they be renamed or deleted?--><br />
<br />
The [[Clinical Desktop]] View is a view of all of the patient information the clinician, physician or user needs to be able to care for a patient. With the Allscripts Touchworks v11 [[Clinical Desktop]] each user will have the ability to create their own view(s). <br />
<br />
'''Clinical Desktop View Starter Sets''' - Allscripts provides a standard starter set of Clinical Desktop Views; Organizations can use what’s provided, modify them or build their own view(s). <br />
<br />
'''Security''' - Users must have a security classification containing the “Workspace View Edit” security code assigned to them to be able to create or edit their Clinical Desktop Views. This security clearance will activate the “edit” button in the Clinical Desktop.<br />
<br />
'''Full Screen Display''' – At any time users can view one particular components information all by itself, by checking the box “Open in Full Screen Display”. <!--This same check box may also be used if for any reason you do not like or wish to create a layered view. No need to build layered views. (see a picture of the "Full Screen Display" view at the end of this document.)--> <!--What is the previous sentence trying to say?--><br />
<br />
== Create Clinical Desktop View==<br />
<br />
We'll configure a [[Clinical Desktop]] View using View 4.<br />
<br />
Log in to [[TouchWorks]] as an administrative user.<br />
<br />
Click Work Def Admin from the vertical toolbar.<br />
<br />
[[Image:111.jpg]]<br />
<br />
* Select Enterprise to create a view that can be assigned to users in multiple organizations<br />
* Select a specific organization to create a view that can only be assigned to users in one organization<br />
<!--need more detailed explaination of 'Enterprise/Organization' field and how it effect views that are created--><br />
<br />
From the Workspace Definition Administrations workspace click '''Add/Edit Desktop View''' on the bottom left of workspace.<br />
<br />
[[Image:222.jpg]]<br />
<br />
<br />
The Edit View Dialog window will appear.<br />
Here you’ll see the default view, which in this example is the Pediatric Patient View utilizing View 3. You will also see the 8 Views you can pick from to create a new view. <br />
<br />
[[Image:22A.jpg]]<br />
<br />
<br />
Let’s create a new view named 'Dr Heartbeat' using View 4.<br />
<br />
Click the “'''New'''…” button.<br />
The Create New View box will appear.<br />
Type in a '''New View Name'''<br />
<br />
[[Image:444.jpg]] <br />
<br />
Click '''OK'''<br />
<br />
<br />
Click on the View you’d like to create. <br />
[[Image:555.jpg]] <br />
<br />
<br />
<br />
This example uses View 4, so when chosen, view 4 appears on my screen.<br />
[[Image:666.jpg]] <br />
<br />
<br />
Next, decide which of these Components you want in each workspace. <br />
<br />
[[Image:666b.jpg]]<br />
<br />
<br />
Let’s say we want to view the following Components in the workspace on the left: Allergies, Meds/Orders and Problem. <br />
'''Check the boxes''' associated with Allergies, Meds/Orders and Problem<br />
Click the “'''Add Selected'''” button in the left side workspace.<br />
<br />
[[Image:777A.jpg]] <br />
<br />
<br />
Now I’ll add ''Health Management Plan'' and ''Chart Viewer'' in the top right workspace and ''Encounter'' and ''Patient Worklist'' in the bottom right workspace.<br />
<br />
[[Image:888a.jpg]]<br />
<br />
<br />
'''Note:''' If a Worklist View is assigned to a user, the Worklist View will be accessible from the Clinical Desktop View for that user, even if the checkbox for that view is not selected in Work Def Admin. See: [[Q: Why do Worklist Views that were not selected in Work Def Admin display in the Clinical Desktop view?]]<br />
<br />
<br />
Click '''Apply''' to save the view and stay on this page, or click '''OK''' to save view and return to the main page and Vertical Tool Bar or click '''Cancel''' to cancel the action.<br />
<br />
<br />
== Add or Remove Items from a Component ==<br />
<br />
<br />
Select the component that you would like to Add or Remove Items from by clicking on the tab. In the example I am going to Remove Items from the Health Management Plan.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 3.jpg]]<br />
<br />
<br />
Next, Check or UnCheck the Items you would like to Remove. In the example, I will Remove all Items except FlowSheets, VitalSigns/Findings, and Normative Growth.<br />
<br />
<br />
[[Image:Clinical Desktop Add Remove Items 2.jpg]]<br />
<br />
<br />
Click Apply to Save Changes and continue Editing this View.<br />
<br />
<br />
(? add instruction to remane components, set default item, set item sort and edit buttons)<br />
<br />
(? add example how to 'split' a component by addin 2 copies, unchecking items and renaming each)<br />
<br />
(? add instruction on how to set as default view)<br />
<br />
(? add link to assign views to organizational roles)<br />
<br />
(? add link to assign views to individual users)<br />
<br />
== Full Screen Display view ==<br />
<br />
<br />
This view allows you to view one component's information at a time. <br />
Simply, check the "Open in Full SCreen Display" and then click on the component you'd like to open for viewing.<br />
<br />
[[Image:999.jpg]]<br />
<br />
<br />
<br />
== Adding/Removing Buttons from Views ==<br />
<br />
Allscripts does a good job at delivering the most useful buttons for each component in the Clinical Desktop. Sometimes you may want to remove or add buttons to the bar to suit your needs. <br />
<br />
[[File:CED.JPG]]<br />
<br />
<br />
<br />
Navigate to Work Def Admin > Add/Edit Desktop View <BR><br />
1) Select the View you want to modify <BR><br />
2) Click on the component you want to modify the buttons for <br><br />
3) Click on Define Buttons<br />
<br />
<br />
[[File:CED2.JPG]]<br />
<br />
<br />
Once in the Customizer you can see all the available commands by going to the Commands tab <BR><br />
In this example we are going to add the Task command to the Chart Viewer <br><br />
<br />
[[File:Command.JPG]]<br />
<br />
<br />
<br />
<br />
==How to remove Views==<br />
<br />
To remove a view you created and no longer need<br />
<br />
<br />
'''Important!''' -Both Desktop Views and Note Views populate the list together. If you try to delete a view in the following steps using the Add/Edit Desktop View button, but don't see it in the list then its under Add/Edit Note View.<br />
<br />
<br />
[[Image:Deleteworkspace4.jpg]]<br />
<br />
<br />
First- Select whether the view you want to delete/edit is an Enterprise or Organization view<br />
<br />
[[Image:Deleteworkspace3.jpg]]<br />
<br />
<br />
Next- select the view you wish to delete and make sure it is not assigned to any users <br />
<br />
[[Image:Deleteworkspace5.jpg]]<br />
<br />
<br />
Then- click the Add/Edit Desktop View or Add/Edit Note View depending on which type you wish to delete/edit<br />
<br />
[[Image:Deleteworkspace.JPG]]<br />
<br />
<br />
If you are in the right view editor (Desktop vs. Note), your selected view will be showing in the list- click the delete button to delete<br />
<br />
[[Image:Deleteworkspace2.jpg]]<br />
<br />
Your view is now deleted!</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Commands.JPG&diff=9761File:Commands.JPG2010-12-09T20:13:28Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:CED2.JPG&diff=9760File:CED2.JPG2010-12-09T20:08:13Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:CED.JPG&diff=9759File:CED.JPG2010-12-09T20:02:13Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=EEHR_displays_wrong_time&diff=9673EEHR displays wrong time2010-11-23T15:44:02Z<p>Jon hull: Created page with 'EEHR is capable of working across multiple timezones. This allows for proper auditing and scheduling times. <br> For this to work properly some System Preferences need to be set.…'</p>
<hr />
<div>EEHR is capable of working across multiple timezones. This allows for proper auditing and scheduling times. <br><br />
For this to work properly some System Preferences need to be set.<br />
<br />
'''Note: This requires access to the Admin workplace to complete.''' <br><br />
'''Caution must be used when in the Admin WP as the system can be rendered inoperable.'''<br><br />
'''Do not modify settings unless you know what you are doing.'''<br />
<br><br><br />
<br />
* Login as Admin (some TWAdmin logins have this WP available to select)<br />
* Select "Systems"<br />
* Select the System you need to modify. <br />
** In this case the system is generically called TouchWorks. Yours might have a real name.<br />
** Do not select the IDX or Phychan systems<br />
** Multi-Org setups might have multiple systems that need to be configured.<br />
<br />
[[File:System.JPG]]<br />
<br />
* Once in the system, select the Preferences tab<br />
* Change the value to the appropriate value for the three preferences below.<br />
** ClientTimeZone<br />
** ServerTimeZone - servers might reside in different timezone than clients!<br />
** ClientSTDTZ</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:System.JPG&diff=9672File:System.JPG2010-11-23T15:39:18Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Technical_Troubleshooting&diff=9671Technical Troubleshooting2010-11-23T15:30:14Z<p>Jon hull: </p>
<hr />
<div>*[[Ack Messages]]<br />
*[[Connecting to Servers using Terminal Services]]<br />
*[[Cluster Troubleshooting]]<br />
*[[Errors]]<br />
*[[Error message: The Web Framework's container]]<br />
*[[Problem Views]]<br />
*[[Problem list not searchable]]<br />
*[[SQL Server Performance Flag]]<br />
*[[Spell Check Control Error]]<br />
*[[TouchWorks Failure Points]]<br />
*[[TouchWorks Session Timeouts]]<br />
*[[Transcribe Error]]<br />
*[[Tricks to prevent excessive table locks]]<br />
*[[Twpm]]<br />
*[[Recycling IIS services]]<br />
*[[Copying Large Files]]<br />
*[[DEP Boot.ini Considerations]]<br />
*[[EEHR displays wrong time]]</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=SSMT:_Users_/_Providers&diff=9158SSMT: Users / Providers2010-08-31T18:06:39Z<p>Jon hull: </p>
<hr />
<div>==Description==<br />
The User / Provider spreadsheet is used with the [[SSMT 101: How to Load and Extract using SSMT|SSMT]] tool to load and manage user accounts in the TouchWorks application. This is based on version 11.0.1.<br />
<br />
Stored Procedures used:<br />
*Extracting data: ImpGetUsers<br />
*Loading data: ImpSetUsers<br />
<br />
==Column Listing and Description==<br />
<br />
* '''Title''' - It allows you to store the persons title. This is optional, but can hold titles such as Dr., Mrs., Mr.<br />
<br />
Storage Location: Works.dbo.Person_Other.TitleName <br />
Data Type: VarChar(20)<br />
Possible Values: Free Text<br />
<br />
* '''User_Provider''' - This allows you to specify the type of user you want to create. User means that you are creating a standard user account. User/Provider means that you are creating a User that is also a provider. This is typically defined as any user that is scheduable or billable. Provider allows you to establish a provider account that will not need to log into the system. This is typically a non-human resource such as a Lab Schedule.<br />
<br />
Possible Values - User, User/Provider, Provider<br />
<br />
* '''LastName''' - This is where you would specify the provider or users last name. <br />
<br />
Storage Location: Works.dbo.Person.LastName, IDXwf.dbo.Users.Name (combined with firstname and middle)<br />
Data Type: VarChar(35)<br />
Possible Values: Free Text<br />
<br />
* '''FirstName''' - This is where you would specify the provider or users first name. <br />
<br />
Storage Location: Works.dbo.Person.FirstName, IDXwf.dbo.Users.Name (combined with lastname and middle)<br />
Data Type: VarChar(18)<br />
Possible Values: Free Text<br />
<br />
* '''Middle''' - This is where you would specify the provider or users middle name or initial. <br />
<br />
Storage Location: Works.dbo.Person.MiddleName, IDXwf.dbo.Users.Name (combined with lastname and firstname)<br />
Data Type: VarChar(18)<br />
Possible Values: Free Text<br />
<br />
* '''OrgName''' - This value should be the name of the Organization that your user or provider belongs to. In most cases, the system is setup as a single org system, so all Org Names will be the same. This value is being translated to the internal Organization ID. <br />
<br />
Storage Location: Works.dbo.IDX_User.PrimaryIntOrgID (ID that is gathered from translated Org Name)<br />
Data Type: VarChar(255)<br />
Possible Values: Free Text, but needs to match the Entry Name in the Organization Dictionary.<br />
<br />
* '''Email''' - This is where you would specify the provider or users email address. If not added here, the user will be required to submit it upon their first login on the User Registration Screen. <br />
<br />
Storage Location: Works.dbo.Person_Other.EmailAddress, IDXwf.dbo.Users.Email<br />
Data Type: VarChar(60)<br />
Possible Values: Free Text<br />
<br />
* '''User_Inactive''' - This is a "Y/N" parameter that determines if the "Person" Entry is active or not. If set to 'Y', the Person entry is set to inactive. If set to 'N' the person entry will be Active. Basically, if you want the account to be usable, this should be 'N'<br />
<br />
Storage Location: Works.dbo.Person.IsInactiveFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''Provider_Inactive''' - This is a "Y/N" parameter that determines if the Provider, User, and Resource entries are active or not. <br />
<br />
'''Only applicable to provider or user/provider account types'''<br />
Storage Location: Works.dbo.IDX_User.IsInactiveFLAG, Works.dbo.Resource_DE.IsInactiveFLAG, Works.dbo.Provider.IsInactiveFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
--need to figure out where the IDXwf flag is set. <br />
<br />
* '''Username''' - This is the username or login for the account. <br />
<br />
Storage Location: Works.dbo.IDX_User.Ausername, IDXwf.dbo.users.ID<br />
<br />
* '''Password''' - This is the users password that will be set in the system. When extracted, this will be encrypted if the user has logged in. You cannot update the password using SSMT. The passowrd can only be set when creating a new user account. This is done for security purposes. <br />
<br />
Storage Location: IDXwf.dbo.Users.Password<br />
Data Type: VarChar(30)<br />
Possible Values: Free Text<br />
<br />
* '''DefaultSiteName''' - This is the Site name the user is associated with in the system. If the name in this column does not match the system site exactly, you will receive the following error in SSMT "No site Record Found".<br />
<br />
Storage Location: Works.dbo.User_Preference.TextString This is stored for the user in this table where the Section column is equal to 'SITE'<br />
The value is stored as text, but is equivalent to the ID in Site_DE<br />
Data Type: VarChar(255)<br />
Possible Values: Free Text but has to exist in the Site Dictionary<br />
<br />
* '''Profession''' - This is the name from the Occupation dictionary that the user or provider needs to be assigned to. This value must exist prior to loading. The value is being translated to the internal ID for storage purposes.<br />
<br />
Storage Location: Works.dbo.Person_Other.OccupationDE(ID that is gathered from translated Profession)<br />
Data Type: VarChar(255)<br />
Possible Values: Free Text, but needs to match the Entry Name in the Occupation Dictionary.<br />
<br />
* '''EmployeeNumber''' - This is not used by TouchWorks, but can house informational data for a provider or user.<br />
<br />
Storage Location: Works.dbo.IDX_User.EmployeeNumber<br />
Data Type: VarChar(20)<br />
Possible Values: Free Text<br />
<br />
* '''OwnershipAuthority''' - This specifies the level of ownership authority that a user or provider would have for notes or documents. If for example, this were set to Level 7, the user or provider would be able to own a document or note that has a level of 7 or lower. This entryname value is translated to the ID from Signature_Authority_DE.<br />
<br />
Storage Location: Works.dbo.User_Signature_Authority.OwnershipAuthorityDE<br />
Data Type: VarChar(255)<br />
Possible Values: Level 1, Level 2, Level 3, Level 4, Level 5, Level 6, Level 7, Level 8, Level 9, Level 10<br />
<br />
* '''Force_PW_Change''' - This specified whether the user will be forced to change their password upon login or not. In most cases you would want to set this to 'Y' the first time you create users so they are forced to establish their own password. If set to 'N', it will not force them to change their password. <br />
<br />
Storage Location: Master.dbo.IDX_Login.ForcePasswordChangeFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''PHB''' - This specifies whether a provider or user should have access to Physician Homebase (PHB).<br />
<br />
Storage Location: IDXwf.dbo.UserRight - This adds a row with the rightproductid = 'Works' and rightapplicationid = 0 and rightid = 'HomeBaseUser' if<br />
set to 'Y'. <br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''System''' - This is the Framework system that the user is going to be assigned to. <br />
<br />
Storage Location: IDXwf.dbo.Users.DefaultSystemID<br />
Data Type: VarChar(255)<br />
Possible Values: Free Text, but the system must exist in the Framework.<br />
<br />
* '''Reg_System''' - This is the Registration System that the user is tied to. This is typically the System ID and the type of scheduling product in use. This is found easiest by extracting data first and reviewing the current entries. An example of what it looks like is <System ID>^IDXM, or <System ID>^GPMS, or <System ID>^Other. This value is used to determine the organization ID that the provider or user belongs to. <br />
<br />
Data Type: VarChar(80)<br />
Possible Values: Free Text, but the value must exist in Reg_System_Map<br />
<br />
* '''Framework_DB''' - This needs to be set to the name of the IDXwf database. This tells the filing routine what database name to use when adding information to the framework database. <br />
<br />
Data Type: VarChar(255)<br />
Possible Values: Free Text, but the database name must exist.<br />
<br />
* '''Finalization Authority''' - This specifies the level of finalization authority that a user or provider would have for notes or documents. If for example, this were set to Level 7, the user or provider would be able to finalize a document or note that has a level of 7 or lower. This entryname value is translated to the ID from Signature_Authority_DE.<br />
<br />
Storage Location: Works.dbo.User_Signature_Authority.SignatureAuthorityDE<br />
Data Type: VarChar(255)<br />
Possible Values: Level 1, Level 2, Level 3, Level 4, Level 5, Level 6, Level 7, Level 8, Level 9, Level 10<br />
<br />
* '''Electronic_Workflow''' - This value specifies whether a physician is setup as electronic workflow or not. This is used in conjunction with the electronic workflow setting within the document type dictionary. If this value is set to 'Y' and the document type is setup as electronic signature or electronic verification, the provide would receive tasks when a document is filed through the interface. <br />
<br />
Storage Location: Works.dbo.User_Signature_Authority.IsElectronicWorkflowFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''Provider_Code''' - This value should be set to the provider code from the practice management system. This is usually know as their scheduling code and can be used for various matching purposes.<br />
<br />
Storage Location: Works.dbo.Provider.EntryCode<br />
Data Type: varchar(32)<br />
Possible Values: Free text<br />
<br />
* '''Provider_Mnemonic''' - This value should be set to the provider's mnemonic from the practice management system. This can be used for other identification purposes if the entry mnemonic from the PMS system is the same as the entrycode or if there is another identifier that needs to be stored. <br />
<br />
Storage Location: Works.dbo.Provider.EntryMnemonic<br />
Data Type: varchar(10)<br />
Possible Values: Free text<br />
<br />
* '''CME_Pilot_Number''' - This was meant to store the physicians CME number, but it is for informational purposes only. This is rarely used, but can be used to house other identifiers if needed. <br />
<br />
Storage Location: Works.dbo.Provider.CMEPilotNumber<br />
Data Type: varchar(10)<br />
Possible Values: Free text<br />
<br />
* '''Ordering_Authority''' - This establishes the ordering authority for the user or provider. This is primarily used for non-medication orders. Based on the required ordering authority on an item in the [[Order Item Dictionary]] it will specify whether an order needs to be authorized by a provider or not. This should be entered as the number of the authority that you desire. <br />
<br />
Storage Location: Works.dbo.Provider.OrderingAuthorityDE (the input value is translated to the actual ID)<br />
Data Type: varchar(1)<br />
Possible Values: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10<br />
<br />
* '''Credentials''' - This column allows you to specify the credentials for the user or provider. It is based on the Credentials dictionary and must contain the Entrycode from that dictionary.<br />
<br />
Storage Location: Works.dbo.Provider_Credentials.CredentialDE (Entrycode gets translated to ID)<br />
Data Type: code<br />
Possible Values: free text, but must exist in the credentials dictionary<br />
<br />
* '''PrimSpecialty''' - This allows you to specify the provider's primary specialty. This will tell the system which specialty favorites to default to. This must be set to an entry name that exists in the specialty dictionary. The value is translated to an internal ID for storage purposes. <br />
<br />
Storage Location: Works.dbo.Provider.SpecialtyDE (Entryname gets translated to ID)<br />
Data Type: varchar(255)<br />
Possible Values: free text, but must exist in the specialty dictionary<br />
<br />
* '''SecSpecialty''' - This allows you to specify the provider's secondary specialty. This will tell the system which specialty favorites to default to. This must be set to an entry name that exists in the specialty dictionary. The value is translated to an internal ID for storage purposes. <br />
<br />
Storage Location: Works.dbo.Provider.Specialty2DE (Entryname gets translated to ID)<br />
Data Type: varchar(255)<br />
Possible Values: free text, but must exist in the specialty dictionary<br />
<br />
* '''DEA_Number''' - This believe it or not houses the provider's DEA number. <br />
<br />
Storage Location: Works.dbo.Provider.DEANumber<br />
Data Type: varchar(30)<br />
Possible Values: free text<br />
<br />
* '''DEA_Exp_Date''' - This allows you to set the DEA expiration date for the provider. It must be provided in a valid date format. <br />
<br />
Storage Location: Works.dbo.Provider.ExpirationDT<br />
Data Type: DateTime<br />
Possible Values: Date format<br />
<br />
* '''Billing_Provider''' - This specifies whether or not the provider is a billing provider. If set to 'Y' it will allow the provider to be chosen on the encounter form. If this is set to 'N' the provider will not be selectable from within the encounter form drop down. <br />
<br />
Storage Location: Works.dbo.Provider.IsBillingProviderFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''Scheduling_Provider''' - This specifies whether a provider has a schedule or not. If set to Y it tells the system that they will receive schedule data within the system. This created an entry in the Resource_DE table within TouchWorks and links the provider to their assigned resource code.<br />
<br />
Storage Location: Works.dbo.Provider.ResourceDE (stored created Resource Entry ID if filed as a Y)<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''Secure_Schedule''' - This sepcifies whether or not the provider schedule should be secure. If set to Y, it will hide the schedule from users that don't have the appropriate security code assigned to them. When this files as a Y, the system creates a new entry in the security code dictionary that is named based on the provider name and entrycode. <br />
<br />
Storage Location: Works.dbo.Provider.SecurityCodeDE (set to the ID of the created security code if this is set to Y)<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''PCP''' - This specifies whether or not the provider can be set as a Primary Care Physician for a patient. <br />
<br />
Storage Location: Works.dbo.Provider.IsPCPFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''DontGenerate_SendChargeTasks''' - This field specifies whehter the physicain will receive send charge tasks. If this is set to Y, the feature is disabled for the user. If this is set to N, the feature is turned on. If on everytime a physician has a scheduled appointment arrived on their shcedule, a task will be created reminding them that they need to create a task for the encounter. The task is automatically removed if the physician submits an encounter form. This is a great way to create a reminder or worklist for the provider, although it is typically not used. Most people will use the indicator on the schedule screen to tell them what's left for the day.<br />
<br />
Storage Location: Works.dbo.Provider.DisableSendChargeFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''Show_Optional_Clinical_Msgs''' - This is not used at this time. <br />
<br />
Storage Location: Works.dbo.Provider.ClinicalMsgFLAG<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''DEA_II''' - This specifies whether the user can prescribe schedule II medications. They must also have the proper security codes assigned to their user account to create a new RX.<br />
<br />
Storage Location: Works.dbo.Provider.SCHED_C_II_IND<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
<br />
* '''DEA_III''' - This specifies whether the user can prescribe schedule III medications. They must also have the proper security codes assigned to their user account to create a new RX.<br />
<br />
Storage Location: Works.dbo.Provider.SCHED_C_III_IND<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
<br />
* '''DEA_IV''' - This specifies whether the user can prescribe schedule IV medications. They must also have the proper security codes assigned to their user account to create a new RX.<br />
<br />
Storage Location: Works.dbo.Provider.SCHED_C_IV_IND<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
<br />
* '''DEA_V''' - This specifies whether the user can prescribe schedule V medications. They must also have the proper security codes assigned to their user account to create a new RX.<br />
<br />
Storage Location: Works.dbo.Provider.SCHED_C_V_IND<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
<br />
<br />
* '''RX_Supervision''' - This defines whether the provider requires RX supervision of not. If set to Y, it will prompt the provider to select their supervising provider when prescribing a medicaiton.<br />
<br />
Storage Location: Works.dbo.Provider.RxSupervisionRequired<br />
Data Type: Bool<br />
Possible Values: 'Y' or 'N'<br />
<br />
* '''StateLicense1''' - This is where you would specify the state of the primary license for the provider. This is the two character code for the state. <br />
<br />
Storage Location: Works.dbo.Prescriber_License.STATE_OF_LIC<br />
Data Type: char(2)<br />
Possible Values: any two character state code<br />
<br />
* '''LicenseNumber1''' - This is where you would specify the prescribing license number for the provider's primary license. <br />
<br />
Storage Location: Works.dbo.Prescriber_License.LIC_NO<br />
Data Type: varchar(14)<br />
Possible Values: Free text license number<br />
<br />
* '''LicExpDate1''' - This is where you would specify the prescribing license expiration date for the provider's primary license. This needs to be a date in the future for the provider to have the ability to prescribe in the defined state.<br />
<br />
Storage Location: Works.dbo.Prescriber_License.LIC_EXP_DT<br />
Data Type: DateTime<br />
Possible Values: Valid Date<br />
<br />
* '''StateLicense2''' - This is where you would specify the state of the secondary license for the provider. This is the two character code for the state. <br />
<br />
Storage Location: Works.dbo.Prescriber_License.STATE_OF_LIC<br />
Data Type: char(2)<br />
Possible Values: any two character state code<br />
<br />
* '''LicenseNumber2''' - This is where you would specify the prescribing license number for the provider's secondary license. <br />
<br />
Storage Location: Works.dbo.Prescriber_License.LIC_NO<br />
Data Type: varchar(14)<br />
Possible Values: Free text license number<br />
<br />
* '''LicExpDate2''' - This is where you would specify the prescribing license expiration date for the provider's secondary license. This needs to be a date in the future for the provider to have the ability to prescribe in the defined state.<br />
<br />
Storage Location: Works.dbo.Prescriber_License.LIC_EXP_DT<br />
Data Type: DateTime<br />
Possible Values: Valid Date<br />
<br />
* '''StateLicense3''' - This is where you would specify the state of the tertiary license for the provider. This is the two character code for the state. <br />
<br />
Storage Location: Works.dbo.Prescriber_License.STATE_OF_LIC<br />
Data Type: char(2)<br />
Possible Values: any two character state code<br />
<br />
* '''LicenseNumber3''' - This is where you would specify the prescribing license number for the provider's tertiary license. <br />
<br />
Storage Location: Works.dbo.Prescriber_License.LIC_NO<br />
Data Type: varchar(14)<br />
Possible Values: Free text license number<br />
<br />
* '''LicExpDate3''' - This is where you would specify the prescribing license expiration date for the provider's tertiary license. This needs to be a date in the future for the provider to have the ability to prescribe in the defined state.<br />
<br />
Storage Location: Works.dbo.Prescriber_License.LIC_EXP_DT<br />
Data Type: DateTime<br />
Possible Values: Valid Date<br />
<br />
* '''Outbound_Dictate_ID''' - This is where you would define the outbound dictate id that is sent with dictations from the TouchWorks system. This can only be added if you have purchased dicatation licenses. <br />
<br />
Storage Location: Works.dbo.Provider.OutboundDictateID<br />
Data Type: varchar(12)<br />
Possible Values: Free text dictate ID<br />
<br />
* '''RecordingFormat''' - This will specify the recording format for the provider. This is typically best to leave blank since the default value is typically the best setting. If you have found that another format is needed for your organization you would specify that here. <br />
<br />
Storage Location: Works.dbo.Provider.RecordingFormatDE (The entryname entered is translated to the internal ID value)<br />
Data Type: varchar(255)<br />
Possible Values: Free text, must be a valid format, they are:<br />
GSM<br />
PCM, 16 Bit, 11025 Hz<br />
PCM, 16 Bit, 22050 Hz<br />
PCM, 16 Bit, 4000 Hz<br />
PCM, 16 Bit, 44100 Hz<br />
PCM, 16 Bit, 8000 Hz<br />
PCM, 8 Bit, 11025 Hz<br />
PCM, 8 Bit, 22050 Hz<br />
PCM, 8 Bit, 4000 Hz<br />
PCM, 8 Bit, 44100 Hz<br />
PCM, 8 Bit, 8000 Hz<br />
<br />
* '''Transcribe Difficulty''' - This allows you to specify the transcribe difficulty within TouchWorks. This is usually used with the [[Winscribe]] application to define the level of difficulty to transcribe for the particular provider. This factor may be increased due items such as specialty difficulty or accents. This is used as a way to ensure that transcriptionists are being fairly reimbursed for more difficult dictations. This value must be set to 1.0 at the very least.<br />
<br />
Storage Location: Works.dbo.Provider.DifficultyFactor<br />
Data Type: float<br />
Possible Values: must be 1.0 or greater.<br />
<br />
* '''AlternateLicense''' - This is a placeholder for the provider's alternate license number. <br />
<br />
Storage Location: Works.dbo.Provider.AlternateLicense<br />
Data Type: varchar(30)<br />
Possible Values: Free text<br />
<br />
* '''UPIN''' - This is a placeholder for the provider's [[UPIN]] number<br />
<br />
Storage Location: Works.dbo.Provider.UPINNumber<br />
Data Type: varchar(20)<br />
Possible Values: Free text<br />
<br />
* '''Def CC Method''' - This is used to specify the providers default communication method when creating carbon copies for other providers. This defines whether it defaults to Printing, Faxing, or tasking. <br />
<br />
Storage Location: Works.dbo.Provider.DistributionTypeDE (The name is translated to the internal ID)<br />
Data Type: varchar(255)<br />
Possible Values: Free text, the possible values are:<br />
<br />
Envelope<br />
Fax<br />
Print<br />
Review Task<br />
<br />
* '''NPI''' - This is a placeholder for the provider's [[NPI]] number<br />
<br />
Storage Location: Works.dbo.Provider.NPI<br />
Data Type: varchar(20)<br />
Possible Values: Free text<br />
<br />
* '''WorkPlace''' - This allows you to establish the default workplace menu for the user or provider. This must be sent as the ID of the menu from the framework database. This can be found within the Admin/menus section of the framework.<br />
<br />
Storage Location: IDXwf.dbo.UserSystem.MenuID<br />
Data Type: varchar(600)<br />
Possible Values: Free text, must be a valid menu ID<br />
<br />
* '''Def Clinical Desktop View''' - This allows you to specify the default clinical desktop view for the user or provider. This must be the name of a valid Clinical Desktop view.<br />
<br />
Storage Location: Works.dbo.WorkspaceLayout_UserDefault.WorkspaceLayoutID (This ID is found by translating the provided name)<br />
Data Type: varchar(255)<br />
Possible Values: Free text, must be a valid clinical desktop name<br />
<br />
* '''IDXMLogin''' - This is used for GE Groupcast or Flowcast users only. When specified it allows them to authenticate to the GE system and will provide metrics on the Physician Homebase page of TouchWorks. If desired, this would be the users login id for the GE application.<br />
<br />
Storage Location: IDXwf.dbo.UserSystemApplication.Username<br />
Data Type: varchar(255)<br />
Possible Values: Free text<br />
<br />
* '''IDXMPassword''' - This is used for GE Groupcast or Flowcast users only. When specified it allows them to authenticate to the GE system and will provide metrics on the Physician Homebase page of TouchWorks. If desired, this would be the users password for the GE application.<br />
<br />
Storage Location: IDXwf.dbo.UserSystemApplication.Password<br />
Data Type: varchar(255)<br />
Possible Values: Free text<br />
<br />
* '''Practice_Department''' - This is used for GE Groupcast or Flowcast users only. This specifies the department the user or provider belongs to. <br />
<br />
* '''PaIPreferredCommMethod''' - This is currently not used<br />
<br />
* '''LinkWithExistingProvider'''<br />
C = Create New Entry ie To upgrade an existing User or Provider to User/Provider<br />
Y = To Link an Existing User to existing Provider<br />
N = Make Updates to Entry.<br />
<br />
'''back to [[SSMT]] main page'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Patient_banner&diff=8352Patient banner2010-05-12T15:01:20Z<p>Jon hull: </p>
<hr />
<div>'''Problem''' <br />
<br />
Patient Banner configuration is inconsistent between users.<br />
<br />
To the user, it appears that some users see a different banner configuration that others. For example, one user may see the field name 'DOB' in the banner, and another user would not see this field name.<br />
<br />
<br />
'''Cause'''<br />
<br />
When using multiple web servers, it is possible for the patient banner configuration to be out of synch.<br />
<br />
<br />
<br />
'''Solution'''<br />
<br />
Using TWAdmin, login directly to each web servers dedicated IP address or name (e.g ASWEB1 and ASWEB2 instead of the virtual name 'ASWEB' and configure the banner as it should appear.<br />
<br />
<br />
<br />
'''Issue'''<br />
<br />
I would like the patient banner fields to display something different, for example Other2 to say C Phone<br />
<br />
'''Solution'''<br />
<br />
Navigate to the folder C:\Program Files\Allscripts Healthcare Solutions\TouchWorks Web\Works\Working\CustomBanner.xml <br />
<br />
Open the file with a program that will allow you to edit the xml. <br />
<br />
Change the value inbetween the <label> </label> tags to whatever you want. For example Other2 to Cellphone.<br />
<br />
'''Note: This file must be copied to each web server! It may also get overwritten with upgrades so keep a backup of the XML file handy to reapply.'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Change_to_Enable_-clinical_item-_Verification&diff=8012Change to Enable -clinical item- Verification2010-04-01T14:08:31Z<p>Jon hull: </p>
<hr />
<div>Prior to 11.1.6 the .NET preferences 'Enable -clinical item- verification' meant to require verification for all clinical items of the given type entered by a user who was not also a provider.<br />
<br />
The 3 preferences are:<br />
* Enable Allergy Verification<br />
* Enable Rx-Orders Verification <br />
* Enable Problem Verification <br />
<br />
An enhancement in 11.1.6 changed the meaning entirely. If you set it to 'Y' for the enterprise it requires verification for all items of the given type entered by any User OR User/Provider not explicitly exempted by having his/her user level pref for this set to 'N'. Unfortunately, before 11.1.6, clients who wanted to use this capability set it to 'Y' for the enterprise, and that was the end of it. When they upgraded to 11.1.6, all items were entered as unverified by all Users and User/Providers. This also removes the ability for a Provider to right click and Verify the item to be correct for the patient.<br />
<br />
<br />
Our recommendation is to set these preferences to 'N' for the enterprise and all of its groups, and to set it to 'Y' for anyone to whom it should apply.<br />
<br />
<br />
'''Organizations upgrading from releases prior to 11.1.6 should take this change into account when upgrading.'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7611V11 Go Live Weekend Overview2009-12-11T16:17:46Z<p>Jon hull: </p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen over the v11 Live system<br> <br />
upgrade weekend. During an upgrade weekend, the system will be totally '''UNAVAILABLE!''' If you have weekend clinics, <br> arrangements will need to be made for a "View Only" system, printed charts or access to Patient charts using a product <br><br />
such as Galen's [http://http://vitalcenter.galenhealthcare.com/ VitalCenter] system.<br />
<br />
'''Please note:''' This is a high level overview. This process will be discussed in greater detail during regular upgrade meetings.<br />
<br><br><br />
<br />
<br />
'''Friday Night approx 5:00-6:00 PM the system is shut down and Backups started'''<br><br />
The system must be brought down at this time to ensure enough time for backups and upgrade work.<br />
* All users must be logged out or risk being kicked out and losing data!<br />
* The Clients IT team will stop IIS and Interfaces to ensure that data cannot be entered into the system.<br />
* The IT team will then begin backing up all databases.<br />
** It's critical that the backups be available to the upgrade technician if needed.<br />
** It's also critical that copies of the backups be written off to a second, secure location.<br />
'''Depending on file sizes, hardware and backup strategy this can take several hours to complete.'''<br />
* Upon completion of the backups, the client will notify the Upgrade Technician<br />
<br><br />
'''Friday Night approx 9:00 - 11:00 PM the Upgrade Technician begins the Upgrade Process'''<br />
* The upgrade starts with upgrading the Web Framework to at least version 4.09.x if not already done.<br />
* The v11 Upgrade is then started on the Databases. <br />
'''This process requires hundreds of scripts to be run, potentially taking 4-12 (or more) hours!!'''<br />
* Some of the scripts are updates to SQL Stored Procedures while others move Clinical data within the system.<br />
** Note: There are NO changes that occur to SQL itself. All changes reside in the AHS databases.<br />
* While database scripts are processing, the other servers are upgraded.<br />
* Web servers will be upgraded to v11 code.<br />
** Framework will be upgraded, along with Java as well as enabling .Net 2.0 functionality.<br />
* Print and Fax centers will receive upgrade.<br />
** Any client maintained customized reports using AHS delivered report names will be overwritten! Please have backups!<br />
* Impact and Forms MD server will be upgraded to latest service pack.<br />
** This will require updates on end user machines.<br />
** The images within the Scan Warehouses are NOT modified in any way.<br />
* Interfaces will have their message definitions upgraded to be v11 compliant.<br />
* Dictation/Winscribe will need to be updated if not version 3.7<br />
* Analytics will be updated post Go-Live by the AHS Analytics team.<br />
<br><br />
'''Saturday Morning approx 12:00 - 6:00 AM after the database upgrade is complete.'''<br />
* Once the main upgrade is complete the Upgrade tech will apply any necessary Hot Fixes.<br />
* If not already done, an update to Medcin may be required.<br />
** This can add an hour or two to the upgrade. It's recommended clients be on the correct version prior to upgrade.<br />
* Upgrade Technician will make Post Upgrade/Pre-Configuration backups.<br />
** Depending on space, Friday nights backups may need to be overwritten, for this reason it is recommended to copy backups to another location.<br />
* Once all upgrades are complete and backups taken, Upgrade Tech will perform quick system test to validate upgrade.<br />
* The system will be then be turned over to the Upgrade Consultant.<br />
<br><br />
'''Saturday Morning approx 7:00 AM - 1:00 PM Upgrade Consultant and Client will commence configuration.'''<br />
* Once the UC feels the system is ready they will work with the client to begin configuration.<br />
* Configuration of the system will be moved from the test system to the Live system using SSMT and CMT.<br />
** Most configuration can be moved with the tools, however, some pieces may need to be manually rebuilt in Live.<br />
'''There are several factors that determine the speed of this process, however, it can take from 4-8 hours to complete.'''<br />
<br><br><br />
'''Saturday Afternoon approx 1:00 - 4:00 PM Configuration is complete and testing can begin.'''<br />
* Client is responsible for testing all aspects of the application.<br />
** This includes testing of ALL workflows.<br />
* Any issues that arise that where not previously noted will be sent to UC and Tech for troubleshooting. <br />
'''Depending on testing team size and time it takes to resolve issues, testing may proceed for 4+ hours on Saturday'''<br />
<br><br><br />
'''Sunday Morning approx 8:00 AM - 12:00 PM Finalization of testing and Go/No Go call.'''<br />
* Sunday morning is reserved for final testing of resolved/outstanding issues if needed.<br />
* At Noon (or sooner)the Go or Rollback decision would be made.<br />
** A Rollback decision (unlikely) would require reverting the system back using Friday nights backups.<br />
** This would be extremely difficult to accomplish if server level backups of the Web, Print, Scan servers are unavailable.<br />
* Immediatly following the GO decision the client IT team will start the Controls Push for the new Web Controls on end user PCs.<br />
* Once the controls are loaded, it is recommended as many end user machines as possible get validated for correct controls.<br />
'''Failed controls installs are the most common cause of application errors on Monday of Go-Live!'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7444V11 Go Live Weekend Overview2009-09-03T15:50:58Z<p>Jon hull: </p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen over the v11 Live system<br> <br />
upgrade weekend. During an upgrade weekend, the system will be totally '''UNAVAILABLE!''' If you have weekend clinics, <br> arrangements will need to be made for a "View Only" system, printed charts or access to Patient charts using a product <br><br />
such as Galen's [http://http://vitalcenter.galenhealthcare.com/ VitalCenter] system.<br />
<br />
'''Please note:''' This is a high level overview. This process will be discussed in high detail during regular upgrade meetings.<br />
<br><br><br />
<br />
<br />
'''Friday Night approx 5:00-6:00 PM the system is shut down and Backups started'''<br><br />
The system must be brought down at this time to ensure enough time for backups and upgrade work.<br />
* All users must be logged out or risk being kicked out and losing data!<br />
* The Clients IT team will stop IIS and Interfaces to ensure that data cannot be entered into the system.<br />
* The IT team with then begin backing up all databases.<br />
** It's critical that the backups be available to the upgrade technician if needed.<br />
** It's also critical that copies of the backups be written off to a second, secure location.<br />
'''Depending on file sizes, hardware and backup strategy this can take several hours to complete.'''<br />
* Upon completion of the backups, the client will notify the Upgrade Technician<br />
<br><br />
'''Friday Night approx 9:00 - 11:00 PM the Upgrade Technician begins the Upgrade Process'''<br />
* The upgrade starts with upgrading the Web Framework to at least version 4.09.x if not already done.<br />
* The v11 Upgrade is then started on the Databases. <br />
'''This process requires hundreds of scripts to be run, potentially taking 4-12 (or more) hours!!'''<br />
* Some of the scripts are updates to SQL Store Procedures while others move Clinical data within the system.<br />
** Note: There are NO changes that occur to SQL itself. All changes reside in the AHS databases.<br />
* While database scripts are processing, the other servers are upgraded.<br />
* Web servers will be upgraded to v11 code.<br />
** Framework will be upgraded, along with Java as well as enabling .Net 2.0 functionality.<br />
* Print and Fax centers will receive upgrade.<br />
** Any client maintained customized reports using AHS delivered report names will be overwritten! Please have backups!<br />
* Impact and Forms MD server will be upgraded to latest service pack.<br />
** This will require updates on end user machines.<br />
** The images within the Scan Warehouses are NOT modified in any way.<br />
* Interfaces will have their message definitions upgraded to be v11 compliant.<br />
* Dictation/Winscribe will need to be updated if not version 3.7<br />
* Analytics will be updated post Go-Live by the AHS Analytics team.<br />
<br><br />
'''Saturday Morning approx 12:00 - 6:00 AM after the database upgrade is complete.'''<br />
* Once the main upgrade is complete the Upgrade tech will apply any necessary Hot Fixes.<br />
* If not already done, an update to Medcin may be required.<br />
** This can add an hour or two to the upgrade. It's recommended clients be on the correct version prior to upgrade.<br />
* Upgrade Technician will make Post Upgrade/Pre-Configuration backups.<br />
** Depending on space, Friday nights backups may need to be overwritten, hence why its recommended to copy backups to another location.<br />
* Once all upgrades complete and backups taken, Upgrade Tech will perform quick system test to validate upgrade.<br />
* The system will be then be turned over to Upgrade Consultant.<br />
<br><br />
'''Saturday Morning approx 7:00 - 8:00 AM Upgrade Consultant will Smoke Test system and prepare for configuration.'''<br />
* Once UC feels system is ready they will work with client to begin configuration.<br />
* Configuration of the system will be moved from the test system to the Live system using SSMT and CMT.<br />
** Most configuration can be moved with the tools, however, some pieces may need to be manually rebuilt in Live.<br />
'''There are several factors that determine the speed of this process, however, it can take from 4-8 hours to complete.'''<br />
<br><br><br />
'''Saturday Afternoon approx 1:00 - 4:00 PM Configuration is complete and testing can commence.'''<br />
* Client is responsible for testing all aspects of the application.<br />
** This includes testing of ALL workflows.<br />
* Any issues that arise that where not previously noted will be sent to UC and Tech for troubleshooting. <br />
'''Depending on testing team size and time it takes to resolve issues, testing may proceed for 4+ hours on Saturday'''<br />
<br><br><br />
'''Sunday Morning approx 8:00 AM - 12:00 PM Finalization of testing and Go/No Go call.'''<br />
* Sunday morning is used for final testing of resolved/outstanding issues if needed.<br />
* At Noon (or sooner)the Go or Rollback decision would be made.<br />
** A Rollback decision (unlikely) would require reverting the system back using Friday nights backups.<br />
** This would be extremely difficult to accomplish if server level backups of the Web, Print, Scan servers is unavailable.<br />
* A GO decision would require the IT team to commence the Controls Push for the new Web Controls on end user PCs.<br />
* Once the controls are loaded, its recommended as many end user machines as possible get validated for correct controls.<br />
'''Failed controls installs are the largest cause of application errors on Monday of Go-Live!'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7443V11 Go Live Weekend Overview2009-09-03T15:49:49Z<p>Jon hull: </p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen over the v11 Live system<br> <br />
upgrade weekend. During an upgrade weekend, the system will be totally '''UNAVAILABLE!''' If you have weekend clinics, <br> arrangements will need to be made for a "View Only" system, printed charts or access to Patient charts using a product <br><br />
such as Galen's [http://http://vitalcenter.galenhealthcare.com/ VitalCenter] system.<br />
<br />
'''Please note:''' This is a high level overview. This process will be discussed in high detail during regular upgrade meetings.<br />
<br><br><br />
<br />
<br />
'''Friday Night approx 5:00-6:00 PM the system is shut down and Backups started'''<br><br />
The system must be brought down at this time to ensure enough time for backups and upgrade work.<br />
* All users must be logged out or risk being kicked out and losing data!<br />
* The Clients IT team will stop IIS and Interfaces to ensure that data cannot be entered into the system.<br />
* The IT team with then begin backing up all databases.<br />
** It's critical that the backups be available to the upgrade technician if needed.<br />
** It's also critical that copies of the backups be written off to a second, secure location.<br />
'''Depending on file sizes, hardware and backup strategy this can take several hours to complete.'''<br />
* Upon completion of the backups, the client will notify the Upgrade Technician<br />
<br><br />
'''Friday Night approx 9:00 - 11:00 PM the Upgrade Technician begins the Upgrade Process'''<br />
* The upgrade starts with upgrading the Web Framework to at least version 4.09.x if not already done.<br />
* The v11 Upgrade is then started on the Databases. <br />
'''This process requires hundreds of scripts to be run, potentially taking 4-12 (or more) hours!!'''<br />
* Some of the scripts are updates to SQL Store Procedures while others move Clinical data within the system.<br />
** Note: There are NO changes that occur to SQL itself. All changes reside in the AHS databases.<br />
* While database scripts are processing, the other servers are upgraded.<br />
* Web servers will be upgraded to v11 code.<br />
** Framework will be upgraded, along with Java as well as enabling .Net 2.0 functionality.<br />
* Print and Fax centers will receive upgrade.<br />
** Any client maintained customized reports using AHS delivered report names will be overwritten! Please have backups!<br />
* Impact and Forms MD server will be upgraded to latest service pack.<br />
** This will require updates on end user machines.<br />
** The images within the Scan Warehouses are NOT modified in any way.<br />
* Interfaces will have their message definitions upgraded to be v11 compliant.<br />
* Dictation/Winscribe will need to be updated if not version 3.7<br />
* Analytics will be updated post Go-Live by the AHS Analytics team.<br />
<br><br />
'''Saturday Morning approx 12:00 - 6:00 AM after the database upgrade is complete.'''<br />
* Once the main upgrade is complete the Upgrade tech will apply any necessary Hot Fixes.<br />
* If not already done, an update to Medcin may be required.<br />
** This can add an hour or two to the upgrade. It's recommended clients be on the correct version prior to upgrade.<br />
* Upgrade Technician will make Post Upgrade/Pre-Configuration backups.<br />
** Depending on space, Friday nights backups may need to be overwritten, hence why its recommended to copy backups to another location.<br />
* Once all upgrades complete and backups taken, Upgrade Tech will perform quick system test to validate upgrade.<br />
* The system will be then be turned over to Upgrade Consultant.<br />
<br><br />
'''Saturday Morning approx 7:00 - 8:00 AM Upgrade Consultant will Smoke Test system and prepare for configuration.'''<br />
* Once UC feels system is ready they will work with client to begin configuration.<br />
* Configuration of the system will be moved from the test system to the Live system using SSMT and CMT.<br />
** Most configuration can be moved with the tools, however, some pieces may need to be manually rebuilt in Live.<br />
'''There are several factors that determine the speed of this process, however, it can take from 4-8 hours to complete.'''<br />
<br><br><br />
'''Saturday Afternoon approx 1:00 - 4:00 PM Configuration is complete and testing can commence.'''<br />
* Client is responsible for testing all aspects of the application.<br />
** This includes testing of ALL workflows.<br />
* Any issues that arise that where not previously noted will be sent to UC and Tech for troubleshooting. <br />
'''Depending on testing speed and time it takes to resolve issues, testing may proceed for 4+ hours on Saturday'''<br />
<br><br><br />
'''Sunday Morning approx 8:00 AM - 12:00 PM Finalization of testing and Go/No Go call.'''<br />
* Sunday morning is used for final testing of resolved/outstanding issues if needed.<br />
* At Noon (or sooner)the Go or Rollback decision would be made.<br />
** A Rollback decision (unlikely) would require reverting the system back using Friday nights backups.<br />
** This would be extremely difficult to accomplish if server level backups of the Web, Print, Scan servers is unavailable.<br />
* A GO decision would require the IT team to commence the Controls Push for the new Web Controls on end user PCs.<br />
* Once the controls are loaded, its recommended as many end user machines as possible get validated for correct controls.<br />
'''Failed controls installs are the largest cause of application errors on Monday of Go-Live!'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7442V11 Go Live Weekend Overview2009-09-03T15:48:12Z<p>Jon hull: </p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen over the v11 Live system<br> <br />
upgrade weekend. During an upgrade weekend, the system will be totally '''UNAVAILABLE!''' If you have weekend clinics, <br> arrangements will need to be made for a "View Only" system, printed charts or access to Patient charts using a product <br><br />
such as Galen's [http://http://vitalcenter.galenhealthcare.com/ VitalCenter] system.<br />
<br />
'''Please note:''' This is a high level overview. This process will be discussed in high detail during regular upgrade meetings.<br />
<br><br><br />
<br />
<br />
'''Friday Night approx 5:00-6:00 PM the system is shut down and Backups started'''<br><br />
The system must be brought down at this time to ensure enough time for backups and upgrade work.<br />
* All users must be logged out or risk being kicked out and losing data!<br />
* The Clients IT team will stop IIS and Interfaces to ensure that data cannot be entered into the system.<br />
* The IT team with then begin backing up all databases.<br />
** It's critical that the backups be available to the upgrade technician if needed.<br />
** It's also critical that copies of the backups be written off to a second, secure location.<br />
'''Depending on file sizes, hardware and backup strategy this can take several hours to complete.'''<br />
* Upon completion of the backups, the client will notify the Upgrade Technician<br />
<br><br />
'''Friday Night approx 9:00 - 11:00 PM the Upgrade Technician begins the Upgrade Process'''<br />
* The upgrade starts with upgrading the Web Framework to at least version 4.09.x if not already done.<br />
* The v11 Upgrade is then started on the Databases. <br />
'''This process requires hundreds of scripts to be run, potentially taking 4-12 (or more) hours!!'''<br />
* Some of the scripts are updates to SQL Store Procedures while others move Clinical data within the system.<br />
** Note: There are NO changes that occur to SQL itself. All changes reside in the AHS databases.<br />
* While database scripts are processing, the other servers are upgraded.<br />
* Web servers will be upgraded to v11 code.<br />
** Framework will be upgraded, along with Java as well as enabling .Net 2.0 functionality.<br />
* Print and Fax centers will receive upgrade.<br />
** Any client maintained customized reports using AHS delivered report names will be overwritten! Please have backups!<br />
* Impact and Forms MD server will be upgraded to latest service pack.<br />
** This will require updates on end user machines.<br />
** The images within the Scan Warehouses are NOT modified in any way.<br />
* Interfaces will have their message definitions upgraded to be v11 compliant.<br />
* Dictation/Winscribe will need to be updated if not version 3.7<br />
* Analytics will be updated post Go-Live by the AHS Analytics team.<br />
<br><br />
'''Saturday Morning approx 12:00 - 6:00 AM after the database upgrade is complete.'''<br />
* Once the main upgrade is complete the Upgrade tech will apply any necessary Hot Fixes.<br />
* If not already done, an update to Medcin may be required.<br />
** This can add an hour or two to the upgrade. It's recommended clients be on the correct version prior to upgrade.<br />
* Upgrade Technician will make Post Upgrade/Pre-Configuration backups.<br />
** Depending on space, Friday nights backups may need to be overwritten, hence why its recommended to copy backups to another location.<br />
* Once all upgrades complete and backups taken, Upgrade Tech will perform quick system test to validate upgrade.<br />
* The system will be then be turned over to Upgrade Consultant.<br />
<br><br />
'''Saturday Morning approx 7:00 - 8:00 AM Upgrade Consultant will Smoke Test system and prepare for configuration.'''<br />
* Once UC feels system is ready they will work with client to begin configuration.<br />
* Configuration of the system will be moved from the test system to the Live system using SSMT and CMT.<br />
** Most configuration can be moved with the tools, however, some pieces may need to be manually rebuilt in Live.<br />
'''There are several factors that determine the speed of this process, however, it can take from 4-8 hours to complete.'''<br />
<br><br />
'''Saturday Afternoon approx 1:00 - 4:00 PM Configuration is complete and testing can commence.'''<br />
* Client is responsible for testing all aspects of the application.<br />
** This includes testing of ALL workflows.<br />
* Any issues that arise that where not previously noted will be sent to UC and Tech for troubleshooting. <br />
'''Depending on testing speed and time it takes to resolve issues, testing may proceed for 4+ hours on Saturday'''<br />
<br><br />
'''Sunday Morning approx 8:00 AM - 12:00 PM Finalization of testing and Go/No Go call.'''<br />
* Sunday morning is used for final testing of resolved/outstanding issues if needed.<br />
* At Noon (or sooner)the Go or Rollback decision would be made.<br />
** A Rollback decision (unlikely) would require reverting the system back using Friday nights backups.<br />
** This would be extremely difficult to accomplish if server level backups of the Web, Print, Scan servers is unavailable.<br />
* A GO decision would require the IT team to commence the Controls Push for the new Web Controls on end user PCs.<br />
* Once the controls are loaded, its recommended as many end user machines as possible get validated for correct controls.<br />
'''Failed controls installs are the largest cause of application errors on Monday of Go-Live!'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7441V11 Go Live Weekend Overview2009-09-03T15:20:12Z<p>Jon hull: </p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen over the v11 Live system<br> <br />
upgrade weekend. During an upgrade weekend, the system will be totally '''UNAVAILABLE!''' If you have weekend clinics, <br> arrangements will need to be made for a "View Only" system, printed charts or access to Patient charts using a product <br><br />
such as Galen's [http://http://vitalcenter.galenhealthcare.com/ VitalCenter] system.<br />
<br />
'''Please note:''' This is a high level overview. This process will be discussed in high detail during regular upgrade meetings.<br />
<br><br><br />
<br />
<br />
'''Friday Night approx 5:00-6:00 PM the system is shut down and Backups started'''<br><br />
The system must be brought down at this time to ensure enough time for backups and upgrade work.<br />
* All users must be logged out or risk being kicked out and losing data!<br />
* The Clients IT team will stop IIS and Interfaces to ensure that data cannot be entered into the system.<br />
* The IT team with then begin backing up all databases.<br />
** It's critical that the backups be available to the upgrade technician if needed.<br />
** It's also critical that copies of the backups be written off to a second, secure location.<br />
'''Depending on file sizes, hardware and backup strategy this can take several hours to complete.'''<br />
* Upon completion of the backups, the client will notify the Upgrade Technician<br />
<br><br />
'''Friday Night approx 9:00 - 11:00 PM the Upgrade Technician begins the Upgrade Process'''<br />
* The upgrade starts with upgrading the Web Framework to at least version 4.09.x if not already done.<br />
* The v11 Upgrade is then started on the Databases. <br />
'''This process requires hundreds of scripts to be run, potentially taking 4-12 (or more) hours!!'''<br />
* Some of the scripts are updates to SQL Store Procedures while others move Clinical data within the system.<br />
** Note: There are NO changes that occur to SQL itself. All changes reside in the AHS databases.<br />
* While database scripts are processing, the other servers are upgraded.<br />
* Web servers will be upgraded to v11 code.<br />
** Framework will be upgraded, along with Java as well as enabling .Net 2.0 functionality.<br />
* Print and Fax centers will receive upgrade.<br />
** Any client maintained customized reports using AHS delivered report names will be overwritten! Please have backups!<br />
* Impact and Forms MD server will be upgraded to latest service pack.<br />
** This will require updates on end user machines.<br />
* Interfaces will have their message definitions upgraded to be v11 compliant.<br />
* Dictation/Winscribe will need to be updated if not version 3.7<br />
* Analytics will be updated post Go-Live by the AHS Analytics team.<br />
<br><br />
'''Saturday Morning approx 12:00 - 6:00 AM after the database upgrade is complete'''<br />
* Once the main upgrade is complete the Upgrade tech will apply any necessary Hot Fixes.<br />
* If not already done, an update to Medcin may be required.<br />
** This can add an hour or two to the upgrade. It's recommended clients be on the correct version prior to upgrade.<br />
* Upgrade Technician will make Post Upgrade/Pre-Configuration backups.<br />
** Depending on space, Friday nights backups may need to be overwritten, hence why its recommended to copy backups to another location.</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7440V11 Go Live Weekend Overview2009-09-03T15:00:49Z<p>Jon hull: </p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen over the v11 Live system<br> <br />
upgrade weekend. During an upgrade weekend, the system will be totally '''UNAVAILABLE!''' If you have weekend clinics, <br> arrangements will need to be made for a "View Only" system, printed charts or access to Patient charts using a product <br><br />
such as Galen's [http://http://vitalcenter.galenhealthcare.com/ VitalCenter] system.<br />
<br />
'''Please note:''' that this is a high level overview. This process will be discussed in high detail during regular upgrade meetings.<br />
<br><br><br />
<br />
<br />
'''Friday Night approx 5:00-6:00 PM the system is shut down and Backups started'''<br><br />
The system must be brought down at this time to ensure enough time for backups and upgrade work.<br />
* All users must be logged out or risk being kicked out and losing data!<br />
* The Clients IT team will stop IIS and Interfaces to ensure that data cannot be entered into the system.<br />
* The IT team with then begin backing up all databases.<br />
** It's critical that the backups be available to the upgrade technician if needed.<br />
** It's also critical that copies of the backups be written off to a second, secure location.<br />
'''Depending on file sizes, hardware and backup strategy this can take several hours to complete.'''<br />
* Upon completion of the backups, the client will notify the Upgrade Technician<br />
<br><br />
'''Friday Night approx 9:00 - 11:00 PM the Upgrade Technician begins the Upgrade Process'''<br />
* The upgrade starts with upgrading the Web Framework to at least version 4.09.x if not already done.<br />
* The v11 Upgrade is then started on the Databases. <br />
'''This process requires hundreds of scripts to be run, potentially taking 4-12 plus hours!'''<br />
* Some of the scripts are updates to SQL Store Procedures while others move Clinical data within the system.<br />
** Note: There are NO changes that occur to SQL itself. All changes reside in the AHS databases.</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7413V11 Go Live Weekend Overview2009-09-01T16:27:17Z<p>Jon hull: </p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen over the v11 Live system<br> <br />
upgrade weekend. During an upgrade weekend, the system will be totally '''UNAVAILABLE!''' If you have weekend clinics, <br> arrangements will need to be made for a "View Only" system, printed charts or access to Patient charts using a product <br><br />
such as Galen's [http://http://vitalcenter.galenhealthcare.com/ VitalCenter] system.<br />
<br />
'''Please note:''' that this is a high level overview. This process will be discussed in high detail during regular upgrade meetings.<br />
<br><br><br />
<br />
<br />
'''Friday Night approx 5:00-6:00 PM the system is shut down and Backups started'''<br><br />
The system must be brought down at this time to ensure enough time for backups and upgrade work.<br />
* All users must be logged out or risk being kicked out and losing data!<br />
*</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=V11_Go_Live_Weekend_Overview&diff=7411V11 Go Live Weekend Overview2009-09-01T15:59:14Z<p>Jon hull: Created page with 'The purpose of this article is to give Upgrade Clients a peek into the events that will happen <br> over the v11 Live system upgrade weekend. <br><br> '''Please note:''' that th…'</p>
<hr />
<div>The purpose of this article is to give Upgrade Clients a peek into the events that will happen <br><br />
over the v11 Live system upgrade weekend. <br><br><br />
<br />
'''Please note:''' that this is a high level overview. This process will be discussed in high detail during regular upgrade meetings.</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7346Troubleshooting Allscripts Web Controls2009-08-24T20:08:09Z<p>Jon hull: </p>
<hr />
<div>__TOC__<br />
<br />
==Description==<br />
This article if for assisting IT personnel with troubleshooting controls issues<br />
<br />
==IMPORTANT NOTE==<br />
'''All controls need to be installed using ADMINISTRATIVE RIGHTS! Most organizations do not have Admin rights assigned <br><br />
to their end users. Be sure to keep this in mind when attempting to install/modify controls!'''<br />
<br />
==Controls Installation Problems==<br />
<br />
* Upon running the TWWebcontrols.msi you receive the following error. <br><br />
[[File:Controlerror.jpg]]<br />
<br />
**Make sure the VC++ Redistributable is installed<br />
**From a command line run- '''<nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki>'''<br />
<br />
==Controls Uninstall Problems==<br />
There is a known issue with some newer v10 versions (10.2.5 - 10.2.7) where some of the web controls <br><br />
may actually be newer than those delivered with v11. There are occasions where the uninstaller leaves some <br><br />
controls behind and because they are newer the v11 Webcontrols wont overwrite them. This can cause numerous <br><br />
issues within the application.<br />
<br />
<br>'''If you are on a newer version of v10'''<br />
*Make a manual removal script part of your push package that will remove all TW controls that may be left behind.<br />
*Ask your AHS or Galen tech resource for more information and sample script.<br />
<br />
==Controls Issues within the Application==<br />
This section will show you some errors that correspond to improperly installed or damaged controls.<br />
<br />
===Spell Check Control Issues===<br />
<br />
[[File:Controlerror2.jpg]]<br />
<br />
Check C:\WINDOWS\Downloaded Program Files for WSpell Spelling Checker Control<br />
*As of the writing of the article the correct version is 5,13,5,0<br />
<BR><br />
If the control is there run the following in a command line (must be an administrator). <BR><br />
'''<nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki>'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7345Troubleshooting Allscripts Web Controls2009-08-24T19:19:55Z<p>Jon hull: /* Spell Check Control Issues */</p>
<hr />
<div>__TOC__<br />
<br />
==Description==<br />
This article if for assisting IT personnel with troubleshooting controls issues<br />
<br />
==Controls Installation Problems==<br />
<br />
* Upon running the TWWebcontrols.msi you receive the following error. <br><br />
[[File:Controlerror.jpg]]<br />
<br />
**Make sure the VC++ Redistributable is installed<br />
**From a command line run- '''<nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki>'''<br />
<br />
==Controls Uninstall Problems==<br />
There is a known issue with some newer v10 versions (10.2.5 - 10.2.7) where some of the web controls <br><br />
may actually be newer than those delivered with v11. There are occasions where the uninstaller leaves some <br><br />
controls behind and because they are newer the v11 Webcontrols wont overwrite them. This can cause numerous <br><br />
issues within the application.<br />
<br />
<br>'''If you are on a newer version of v10'''<br />
*Make a manual removal script part of your push package that will remove all TW controls that may be left behind.<br />
*Ask your AHS or Galen tech resource for more information and sample script.<br />
<br />
==Controls Issues within the Application==<br />
This section will show you some errors that correspond to improperly installed or damaged controls.<br />
<br />
===Spell Check Control Issues===<br />
<br />
[[File:Controlerror2.jpg]]<br />
<br />
Check C:\WINDOWS\Downloaded Program Files for WSpell Spelling Checker Control<br />
*As of the writing of the article the correct version is 5,13,5,0<br />
<BR><br />
If the control is there run the following in a command line (must be an administrator). <BR><br />
'''<nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki>'''</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Controlerror2.jpg&diff=7344File:Controlerror2.jpg2009-08-24T19:14:28Z<p>Jon hull: uploaded a new version of "File:Controlerror2.jpg"</p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7343Troubleshooting Allscripts Web Controls2009-08-24T19:12:44Z<p>Jon hull: /* Controls Installation Problems */</p>
<hr />
<div>__TOC__<br />
<br />
==Description==<br />
This article if for assisting IT personnel with troubleshooting controls issues<br />
<br />
==Controls Installation Problems==<br />
<br />
* Upon running the TWWebcontrols.msi you receive the following error. <br><br />
[[File:Controlerror.jpg]]<br />
<br />
**Make sure the VC++ Redistributable is installed<br />
**From a command line run- '''<nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki>'''<br />
<br />
==Controls Uninstall Problems==<br />
There is a known issue with some newer v10 versions (10.2.5 - 10.2.7) where some of the web controls <br><br />
may actually be newer than those delivered with v11. There are occasions where the uninstaller leaves some <br><br />
controls behind and because they are newer the v11 Webcontrols wont overwrite them. This can cause numerous <br><br />
issues within the application.<br />
<br />
<br>'''If you are on a newer version of v10'''<br />
*Make a manual removal script part of your push package that will remove all TW controls that may be left behind.<br />
*Ask your AHS or Galen tech resource for more information and sample script.<br />
<br />
==Controls Issues within the Application==<br />
This section will show you some errors that correspond to improperly installed or damaged controls.<br />
<br />
===Spell Check Control Issues===<br />
<br />
[[File:Controlerror2.jpg]]</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7342Troubleshooting Allscripts Web Controls2009-08-24T19:11:35Z<p>Jon hull: </p>
<hr />
<div>__TOC__<br />
<br />
==Description==<br />
This article if for assisting IT personnel with troubleshooting controls issues<br />
<br />
==Controls Installation Problems==<br />
<br />
* Upon running the TWWebcontrols.msi you receive the following error. <br><br />
[[File:Controlerror.jpg]]<br />
<br />
**Make sure the VC++ Redistributable is installed<br />
**From a command line run <nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki><br />
<br />
<br />
==Controls Uninstall Problems==<br />
There is a known issue with some newer v10 versions (10.2.5 - 10.2.7) where some of the web controls <br><br />
may actually be newer than those delivered with v11. There are occasions where the uninstaller leaves some <br><br />
controls behind and because they are newer the v11 Webcontrols wont overwrite them. This can cause numerous <br><br />
issues within the application.<br />
<br />
<br>'''If you are on a newer version of v10'''<br />
*Make a manual removal script part of your push package that will remove all TW controls that may be left behind.<br />
*Ask your AHS or Galen tech resource for more information and sample script.<br />
<br />
==Controls Issues within the Application==<br />
This section will show you some errors that correspond to improperly installed or damaged controls.<br />
<br />
===Spell Check Control Issues===<br />
<br />
[[File:Controlerror2.jpg]]</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Controlerror2.jpg&diff=7341File:Controlerror2.jpg2009-08-24T19:09:53Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7340Troubleshooting Allscripts Web Controls2009-08-24T19:02:43Z<p>Jon hull: </p>
<hr />
<div>__TOC__<br />
<br />
==Description==<br />
This article if for assisting IT personnel with troubleshooting controls issues<br />
<br />
==Controls Installation Problems==<br />
<br />
* Upon running the TWWebcontrols.msi you receive the following error. <br><br />
[[File:Controlerror.jpg]]<br />
<br />
**Make sure the VC++ Redistributable is installed<br />
**From a command line run <nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki><br />
<br />
<br />
==Controls Uninstall Problems==<br />
There is a known issue with some newer v10 versions (10.2.5 - 10.2.7) where some of the web controls <br><br />
may actually be newer than those delivered with v11. There are occasions where the uninstaller leaves some <br><br />
controls behind and because they are newer the v11 Webcontrols wont overwrite them. This can cause numerous <br><br />
issues within the application.<br />
<br />
<br>'''If you are on a newer version of v10'''<br />
*Make a manual removal script part of your push package that will remove all TW controls that may be left behind.<br />
*Ask your AHS or Galen tech resource for more information and sample script.</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7339Troubleshooting Allscripts Web Controls2009-08-24T18:52:17Z<p>Jon hull: /* Controls Installation Problems */</p>
<hr />
<div>__TOC__<br />
<br />
==Description==<br />
This article if for assisting IT personnel with troubleshooting controls issues<br />
<br />
==Controls Installation Problems==<br />
<br />
* Upon running the TWWebcontrols.msi you receive the following error. <br><br />
[[File:Controlerror.jpg]]<br />
<br />
**Make sure the VC++ Redistributable is installed<br />
**From a command line run <nowiki>regsvr32 c:\windows\system32\licmgr10.dll</nowiki></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Controlerror.jpg&diff=7338File:Controlerror.jpg2009-08-24T18:50:24Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7337Troubleshooting Allscripts Web Controls2009-08-24T18:45:45Z<p>Jon hull: </p>
<hr />
<div>__TOC__<br />
<br />
==Description==<br />
This article if for assisting IT personnel with troubleshooting controls issues<br />
<br />
==Controls Installation Problems==</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Troubleshooting_Allscripts_Web_Controls&diff=7336Troubleshooting Allscripts Web Controls2009-08-24T18:33:39Z<p>Jon hull: Created page with 'This page will be a repository to help IT teams deal with Controls Related issues.'</p>
<hr />
<div>This page will be a repository to help IT teams deal with Controls Related issues.</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Med_History_Patient_Disable&diff=7330Med History Patient Disable2009-08-20T20:49:36Z<p>Jon hull: </p>
<hr />
<div>'''New in v11.1.6 and later-''' Clients who use Rx Hub to retrieve patients Med History now have the ability to disable retrieval on a patient level if needed to conform with HIPPA.<br />
<br />
<br />
A new symbol has been added to the Patient Banner that indicates that patient consent for Med History retrieval is unknown<br />
<br />
<br />
[[File:Rxhub.JPG]]<br />
<br />
<br />
From the Patient Information screen you can set consent for each patient if desired. <br />
<br />
Setting a status of Declined will stop the system from retrieving the patients Med history in for future encounters.<br />
<br />
<br />
[[File:Rxhub2.JPG]]</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Med_History_Patient_Disable&diff=7329Med History Patient Disable2009-08-20T20:49:06Z<p>Jon hull: </p>
<hr />
<div>'''New in v11.1.6 and later-''' Clients who use Rx Hub to retrieve patients Med History now have the ability to disable retrieval on a patient level if needed to conform with HIPPA.<br />
<br />
<br />
A new symbol has been added to the Patient Banner that indicates that patient consent for Med History retrieval is unknown<br />
<br />
<br />
[[File:Rxhub.JPG]]<br />
<br />
<br />
From the Patient Information screen you can set consent for each patient if desired. <br />
Setting a status of Declined will stop the system from retrieving the patients Med history in for future encounters.<br />
<br />
<br />
[[File:Rxhub2.JPG]]</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=Med_History_Patient_Disable&diff=7328Med History Patient Disable2009-08-20T20:48:06Z<p>Jon hull: Created page with ''''New in v11.1.6 and later-''' Clients who use Rx Hub to retrieve patients Med History now have the ability to disable retrieval on a patient level if needed. A new symbol has…'</p>
<hr />
<div>'''New in v11.1.6 and later-''' Clients who use Rx Hub to retrieve patients Med History now have the ability to disable retrieval on a patient level if needed.<br />
<br />
<br />
A new symbol has been added to the Patient Banner that indicates that patient consent for Med History retrieval is unknown<br />
<br />
<br />
[[File:Rxhub.JPG]]<br />
<br />
<br />
From the Patient Information screen you can set consent for each patient if desired. Setting a status of Declined will stop the system from retrieving the patients Med history in for future encounters.<br />
<br />
<br />
[[File:Rxhub2.JPG]]</div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Rxhub2.JPG&diff=7327File:Rxhub2.JPG2009-08-20T20:45:40Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=File:Rxhub.JPG&diff=7326File:Rxhub.JPG2009-08-20T20:44:26Z<p>Jon hull: </p>
<hr />
<div></div>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=.NET_Preferences&diff=7325.NET Preferences2009-08-20T20:35:08Z<p>Jon hull: /* 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 behaviour 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.<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 />
==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 TouchWorks. 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 TouchWorks 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 TouchWorks 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 />
'''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 TouchWorks 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 />
'''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<br />
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: 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 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 />
'''Enable Allergy 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 />
'''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 Type for Worklist'''<br />
*<br />
<br />
Available Options:<br />
Recommended Setting: <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 />
'''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 TouchWorks.<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 />
'''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 />
'''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 />
'''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 />
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'''<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 />
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'''<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 />
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 />
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 />
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 />
<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 />
'''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<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'''<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 />
'''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 />
==Problem Preferences==<br />
'''Enable Problem 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 />
==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 />
'''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 If Did Not Order'''<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 />
* 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'''<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 />
'''Result Verification Note Use'''<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 Patient Communication Methods'''<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', 'No Patient Communication Needed at this Time', <br />
'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 />
* 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 />
<br />
'''Results Verification 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'''<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>Jon hullhttps://wiki.galenhealthcare.com/index.php?title=.NET_Preferences&diff=7324.NET Preferences2009-08-20T20:29:43Z<p>Jon hull: /* 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 behaviour 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.<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 />
==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 TouchWorks. 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 TouchWorks 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 TouchWorks 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 />
'''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 TouchWorks 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 />
'''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<br />
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: 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 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 />
'''Enable Allergy 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 />
'''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 Type for Worklist'''<br />
*<br />
<br />
Available Options:<br />
Recommended Setting: <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 />
'''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 TouchWorks.<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 />
'''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 />
'''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 />
'''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 />
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'''<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 />
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'''<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 />
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 />
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 />
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 />
<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 />
'''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 />
<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<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'''<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 />
'''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 />
==Problem Preferences==<br />
'''Enable Problem 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 />
==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 />
'''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 If Did Not Order'''<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 />
* 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'''<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 />
'''Result Verification Note Use'''<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 Patient Communication Methods'''<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', 'No Patient Communication Needed at this Time', <br />
'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 />
* 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 />
<br />
'''Results Verification 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'''<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>Jon hull