Quantcast
Viewing all articles
Browse latest Browse all 4218

Reasons to Keep .EXE Version?

Hello, we are going to begin transitioning to 11e after a decade of using the .EXE version. My question to you all is this. Are there any workflows, or niche parts of workflows, that your organization continues to use the .EXE simply because the user interface is more conducive to efficiency for that workflow/task?

One example I think I see has to do with our Health Information team and how they process documents that arrive in our Fax Inbox. our policy for REASONS has been to assign a document to a patient’s PCP when possible, not necessarily the name of the provider in the document itself. The problem is that in 11e, when working in the Fax Inbox and attaching a document to a patient, at no point in the workflow can you see the PCP of the patient you are attaching to. Whereas in the .EXE version, this information is just available on the Document Details window’s orange sticky note at the top of the pop-up. So to do this workflow in 11e, we would need to close out the attachment window and look up the patient’s Hub to see the PCP and then go back and attach the document (that or have another window with another instance of 11e open to look up patient PCPs.)

So in summary, for our folks working in the INBOX, I’m leaning toward just keeping them using the .EXE version as it is just so much quicker of a process! I’m just curious if anybody who has made the transition has found other spots in their organization where .EXE still makes sense in some instances.

Thank you!


Viewing all articles
Browse latest Browse all 4218

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>