I just pushed out the latest changes to this location. I understand being busy. Thanks for your help. I am working on learning the rebase thing but have not figured it out.
I rebased Sherwin’s commits into one commit (I also rebased it into the most current codebase) and placed here for review/testing:
So, let the github review and testing commence
Sherwin, you should grab this branch and begin working on it now, which can be done with the following in commandline git:
git remote add brady git://github.com/bradymiller/openemr.git
git fetch brady
git checkout brady/sherwin-appt-reminder-rebase_1
(ignore the warning)
git checkout -b appt-reminder-rebase_1
(at this point you will now have a appt-reminder-rebase_1 branch with your commit on top of the most recent OpenEMR codebase)
At first glance at Brady’s rebased commit, this doesn’t look like a “clean” commit. There are some acl and layout changes in left_nav that look completely unrelated to reminder system.
Looks like Sherwin was working in an old interface/main/left_nav.php file and then copied it into the development repo. Should be an easy thing for him to fix since it looks like he only made a couple changes in the file.
This is something that can be part of the review (ie. don’t fix this yet Sherwin until after the review and after you learn how to work from the above rebased branch).
It has come down to 8 days left. We were hoping that the community found the project to be worthwhile and support the funding of the project.
I was not going to lobby for the project but let it ride out and I do thank Brady Miller for putting it on the front page of the OpenEMR website. I wanted the project to live or die on it’s own merits rather than being pushed through by us just because it exciting to build applications.
With 8 days left at this point and being over 98% away from the goal of the funding request. It appears this feature is not wanted by the community at large.
If I am wrong, please vote by adding funding to the project.
I have used Asterisk VOIP servers for many years. I even run them at my house to handle all the telemarker calls. I may reboot the box once a year - rock solid opensource software. Less than 0.02 cents a minute or around $8/mo unlimited.
Seems the two, Asterisk and openEMR, should get together nicely. I see there is a commercial Asterisk module for appointment reminders - I’ll look around to see if there is some openSource alternative before trying to integrate this code into the commercial asterisk module. Perhaps the openEMR vendors do this for their clients, but I am looking to do this as opensource for all openEMR users. So if anyone here has done this, including the vendors, rather than state you have done this, it would be nice if you could share your code with the community. It would be greatly appreciated.
We have done this with a simple interface to voicent. It literally just pulls a list of the next two working days appts as csv (using cron) and uploads it to the voicent server which takes over the dialing
Tony,
Thank you (and to the OpenEMR community) for all of your contributions. I think I finally found what I was looking for to use in my OpenEMR v4.2.2 (new install for a new family practice clinic). Other than the script you provided above did you have to manipulate any scripts in the Voicent? To which directory within OpenEMR did you put your voicent reminders cron scripts? Do you mind posting the steps you’ve made that made your cron script flow flawlessly? Thanks.