Difference between revisions of "Declines an Authorize Order"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
What happens if the provider does not approve the Authorize Order task? | What happens if the provider does not approve the Authorize Order task? | ||
| − | |||
| − | + | '''VOID Workflow:''' If the provider right clicks on the prescription, selects annotate -> enters reason for denial then right clicks and selects Void - then a Rejected Rx task is sent to the team. | |
| − | ENTER IN ERROR Workflow: If the provider rick clicks on the prescription, selects annotation -> enters reason for denial he/she would then need to commit before they can right click and enter in error. This workflow does not create a task to the staff for notification purposes. | + | '''Caveat - Rejected Rx would need to be delegated included in all the team views.''' |
| + | |||
| + | |||
| + | '''ENTER IN ERROR Workflow:''' If the provider rick clicks on the prescription, selects annotation -> enters reason for denial he/she would then need to commit before they can right click and enter in error. This workflow does not create a task to the staff for notification purposes. | ||
Latest revision as of 20:01, 5 June 2012
What happens if the provider does not approve the Authorize Order task?
VOID Workflow: If the provider right clicks on the prescription, selects annotate -> enters reason for denial then right clicks and selects Void - then a Rejected Rx task is sent to the team.
Caveat - Rejected Rx would need to be delegated included in all the team views.
ENTER IN ERROR Workflow: If the provider rick clicks on the prescription, selects annotation -> enters reason for denial he/she would then need to commit before they can right click and enter in error. This workflow does not create a task to the staff for notification purposes.