Difference between revisions of "Q: Can you change what task type the document interface triggers for those documents that are electronic signature (or part of the electronic workflow)?"
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
'''Requirements:'''<br> | '''Requirements:'''<br> | ||
− | • | + | • The ability to create a task for those documents that come into Enterprise EHR via a document interface, but not the Sign Note task. In place of the standard Sign Note/Verify Doc task would be a client defined task added to the [[Task Name]] dictionary.<br> |
− | • | + | • The ability for someone other than the document owner to decide if the document needs a carbon copy and can handle that cc routing with faxing or tasking.<br> |
− | • | + | • The ability to handle these carbon copy situations efficiently even though the users are not yet using note.<br> |
− | • | + | • The ability to efficiently route or cc the information even though the transcription vendor does not have the ability to send us cc information electronically.<br> |
− | • | + | • The ability to generate a task type that can be manually completed by clicking "Done" once it is determined if a carbon copy is needed.<br> |
'''Approach:'''<br> | '''Approach:'''<br> | ||
− | 1. Utilize the Override Task Flag field in the interface mapping to cancel tasking to the owner<br> | + | 1. Utilize the Override Task Flag field in the interface mapping to cancel tasking to the owner.<br> |
2. Utilize the [[Routing List]] field in the interface mapping to send a Verify Doc task to those on the list (could be to a team as well).<br> | 2. Utilize the [[Routing List]] field in the interface mapping to send a Verify Doc task to those on the list (could be to a team as well).<br> |
Latest revision as of 21:50, 21 June 2012
Requirements:
• The ability to create a task for those documents that come into Enterprise EHR via a document interface, but not the Sign Note task. In place of the standard Sign Note/Verify Doc task would be a client defined task added to the Task Name dictionary.
• The ability for someone other than the document owner to decide if the document needs a carbon copy and can handle that cc routing with faxing or tasking.
• The ability to handle these carbon copy situations efficiently even though the users are not yet using note.
• The ability to efficiently route or cc the information even though the transcription vendor does not have the ability to send us cc information electronically.
• The ability to generate a task type that can be manually completed by clicking "Done" once it is determined if a carbon copy is needed.
Approach:
1. Utilize the Override Task Flag field in the interface mapping to cancel tasking to the owner.
2. Utilize the Routing List field in the interface mapping to send a Verify Doc task to those on the list (could be to a team as well).