On the CPOE A&P-CCC form, a problem is selected and documented on. Once the problem is selected, medications for that problem (mostly) populate the documentation in that multi-line edit field. If orders are created using that diagnosis, those orders will populate the multi-line edit field for the problem. And the Commit Assessment button turns yellow, requiring the provider to click the Commit button if they want the documentation to show in the Problem list. Can this Commit Assessment button auto-click?
I have several providers providers who want to have Problems added to the OV to auto populate the Orders added during that visit. Also, when in the CPOE A&P, if the problem is selected, can it also populate the Orders for that visit?
They would also ideally like to see the orders signed without having to click to sign them.
Is this possible? I did re-explain what CPOE means...Is any of this possible?
Thank you,
Possible? Yes, but not within the CPOE encounter form. You would need to create a custom form to do all that you ask.
A good idea? Not all of it. The 'auto commit' notion for the assessment is one rife with issues and prone to instability in the EMR, hence why the commit button is used. This can, however, be reduced to a single button that stores all of the assessments at one time.
The balance of your ideas are doable in a custom form.
I just posted basically this same question before seeing this one.
What are the issues/instability you are speaking of. My thought was a page close handler that would check to see if it was committed and if not it could prompt the user to do so. When you say issues, do you mean that programatically it would be a problem? Does that have to do with modifying assessments after they were committed?
The EMR does not like the mel_add_assessment data symbol as a watcher. Using it as such introduces frequent polling of the data base thereby increasing network overhead. All of this combined causes the EMR to crash when under moderate to heavy load. As the only form in the udpate, it typically will behave, but in a update with a full set of forms, crashes abound.
I have created several versions of a CPOE like encounter form. Using a doc var to feed the data symbol, no go. Using an obsterm to feed the symbol, no go. Using a doc var to global var to feed the symbol, no go. Each time I have tried new approaches to automating the process and each time, I had to revert back to a button styled execution. Since the introduction of ICD10, it has become even more unstable to attempt.
The best one can hope for and remain stable is a single button click along with a close page check., neither of which, unfortunately, can be added to the CCC CPOE...
I just responded to rwilliams similar post. CQIC offers a solution. Check out http://www.clinicalcontent.com/