Difference between revisions of "Verify RX Actions"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
__TOC__
 +
 
== Description ==
 
== Description ==
  
Line 15: Line 17:
 
Click '''''Communication Method''''' from the Dictionary drop down menu.  
 
Click '''''Communication Method''''' from the Dictionary drop down menu.  
  
Review, note write down the existing Action Statuses of the RX settings.
+
Review and note the existing Action Statuses of the RX settings.
  
  
Line 26: Line 28:
 
Click '''''Communication Method''''' from the Dictionary drop down menu.  
 
Click '''''Communication Method''''' from the Dictionary drop down menu.  
  
Using the note from step one, confirm the RX Action Status's are what they were before the upgrade.
+
Using the note from step one, confirm the RX Action Status settings are as they were before the upgrade.
  
Update Status's if applies.
+
Update any Status as needed.
  
 
Click Save.
 
Click Save.
 +
 +
 +
==Links==
 +
Back to [[Application Troubleshooting]]

Latest revision as of 16:31, 30 April 2018

Description

This page was designed to show the user how to verify the RX Settings after an upgrade. Often during an upgrade the RX Settings "Dispense RX and "Dispense Sample" revert back to the default setting and must be set back to what the client prefers and requires.

Verify RX Actions are correct

Before the Upgrade

Login to TouchWorks as TWAdmin.

Click on Dictionaries from the Vertical Tool Bar (VTB).

Click Communication Method from the Dictionary drop down menu.

Review and note the existing Action Statuses of the RX settings.


After the Upgrade

Login to TouchWorks as TWAdmin.

Click on Dictionaries from the Vertical Tool Bar (VTB).

Click Communication Method from the Dictionary drop down menu.

Using the note from step one, confirm the RX Action Status settings are as they were before the upgrade.

Update any Status as needed.

Click Save.


Links

Back to Application Troubleshooting