We have been unfortunately unsuccessful with Weno on any of our builds. We initially started with 7.0.2 (3) up to now 7.0.3 (4). It appears that when updating the pharmacy directory while the script is starting, it never says successful in the log. Yet it reports in the Demographics “Choice” settings as success and even listing the number of pharmacies accumulated in the task. There is a message posted that the configuration is incomplete due to the failure to select a default pharmacy. We were instructed by Kevin to use the test and other options and we are unable to display any pharmacies to provide a default. I am inquiring whether there are any others users of WENO who have encountered any issues as the such above?
We are going to look at Ensora eRx and will schedule a demo to determine if it works. I am aware there are atleast 2 devs here who are involved with the module/app formerly known as Newcrop.
Anyway we are wondering what could be the issue with WENO as we have not had any success with the module what so ever and are frustrated.
Hello Warren-
This is Harley Tuck, with MI-Squared, vendors for Ensora eRx for OpenEMR. If you are committed to using OpenEMR for eRx we are the ones to talk to.
At this time we are the sole vendors for Ensora on OpenEMR so if you want to line up a demo please email me at htuck@mi-squared.com.
I cannot speak to the problems folks have with weno, only that I do see a lot of posts in the forum talking about it not working in one way or another.
Ensora works with any version of OpenEMR, no code modification required. We have a setup routine that configures your OpenEMR instance to communicate with Ensora’s eRx system, and its eRx interface is delivered directly to a dedicated tab in the patient’s display.
Our devs do offer customization of OpenEMR to modify its management of Ensora interactions but that is almost never necessary because all the available capabilities are handled in Ensora and delivered to the dedicated tab. But we can go into those details in your demo.
I’m looking forward to discussing this with you.
Best- Harley
We were able to get Weno rolling with the assistance of Jerry P. He discovered the issue that was preventing successful functionality of Weno for our clinic. I had spoken with a rep in Maryland with Ensora prior to the soultion resolution that was provided by Jerry P, FYI, so I was aware and prepared to go in that direction.
However, due to the incredible solution to our problem with Weno that Jerry was able to resolve, it now works flawlessly and we are so appreciative of the fine work that Jerry P has demonstrated. He’s actually a good guy like you Huck!
I wanted to thank him publically for his involvement in Open EMR as well as you Huck (I know it’s THUCK). Jerry P was able to run down the solution to our inability to properly utilize Weno. It should be noted that Jerry P has contributed a tremendous amout of modules to Open EMR and should be applauded for his contributions!
Thanks to both of you guys for your involvement in Open EMR!
