SMS Reminder setup help
Hi,
I have a few questions relating to setting up SMS reminders. I’ve read the notes and Maggie and I have had a chat, and a few areas are still unclear. Mainly around ‘purpose reminder’ and if it trumps everything as we were still unsure. Would you mind answering the questions below so that I can get this clear in my head?
- If SMS is ticked in the reminder type template and the client has purpose reminder set against a phone number on their file, but ‘Allow SMS’ is NOT ticked on the client file. How will they receive this reminder?
- If SMS is ticked in the reminder type template and the client has no purpose reminder set against any contacts on their file, but ‘Allow SMS’ is NOT ticked on the client file. How will they receive this reminder?
- What if SMS is NOT ticked in the Reminder Type Template, but their mobile number has purpose reminder and ‘Allow SMS’ is ticked on the client file. How will they get this reminder?
- What if SMS is NOT ticked in the Reminder Type Template, but their mobile number has purpose reminder and ‘Allow SMS’ is NOT ticked on the client file. How will they this reminder?
Re: SMS Reminder setup help
Running through the logic in the "Post, Email, SMS, List or Export?" section of http://www.openvpms.org/documentation/csh/1.9/reporting/reminder we have:
Fails bullet 2 which says:
so falls thru then bullet 3 operates:
so the reminder is listed.
Use bullet 4:
NOTE that since the first contact found is then used (and this could be a phone, email or address) then the reminder could be processed as List, Email, or Post respectively. HENCE it is important to have one and only one contact with purpose Reminder if you want to have precise control of what is happening.
Note that in preparation to switching to using emailed reminders I have had to do a lot of cleanup in our system of reminder purposes. I used a set of sql statements to do the following:
/* delete all reminder purposes from all customer contacts */
/* set purpose Reminder for all preferred email contacts for active customers*/
/* set purpose Reminder on the phone contact(s) for those active customers who do not have any contacts with purpose Reminder*/
/* set purpose Reminder on the preferred phone contact(s) for those who do not have a preferred email address*/
/* set purpose Reminder on the NOT preferred phone contact(s) for those who do not have a preferred email address*/
If you want the block of sql, please yell.
Fails bullet 2, so falls into bullet 3, but since SMS is not ticked on the template, gets processed as List
Same logic as above - will be List'ed
NOTE: you might guess from the sql that we do not intend to use SMS reminders - because there is simply not enough power in the system and available characters in the SMS message to enable one to create a useful reminder via SMS. We have also held off going to email reminders because one cannot get the reminder information (ie patient name, reminder type) into the email message body.
In 2.0 the situation gets better because the reminder system is far more powerful and flexible - AND one can have multi-part SMS messages (ie longer than the 160 character limit.
Regards, Tim G
Re: SMS Reminder setup help
Hi Tim,
Thanks for all that information. It would be great if we could get the sql block.
We will wait for version 2.0, do you have any idea of a release date for this?
Sandra.
Re: SMS Reminder setup help
Sandra:
a) see attached file. (It has been renamed to reminderPurpose.txt from reminderPurpose.sql so I could upload it - you might want to rename it back to .sql) You will find that this contains a number of different sql statements, some for getting information, some for doing the updates. Note also that the 2nd one is used to find the lookup-id for the purpose Reminder. In our system this is 137 - in yours it will almost certaily be different. If yours is say 123, then you need to change 137 to 123 in the other statements.
b) 2.0 availablity date: currently 2.0 is in alpha test stage and is not deemed 'production ready'. At some stage it will be deemed 'beta test/production ready' and at that stage if one is brave and wants the available new features badly enough then you could install it in production. Tim A has control of this date. My personal hope is that this will occur in August and will include the multi-site clinician/worklist/printer/customer facility as well as the currently added features listed in http://www.openvpms.org/documentation/csh/2.0/new-features
As for the final release date - my guess is Jan/Feb 2018 - but that is a function of what other features will be added.
Note that there are significant risks/impacts of using a pre-production release and that if you do so, you need a good friendly cheap integrator (because you are going to be installing new snapshots every couple of weeks) and it is almost mandatory to run a test system that you can install a new snapshot on and play with it before installing on production. In our case we try to run two stage testing: my latop, then the amazon test system (so the staff can play), then finally amazon production.
You also have a resposibility to report any problems found.
Regards, Tim G