SMS Appointment reminders (Automated)

Changes applied in revision 6840

New and updated documentation:

• http://www.openvpms.org/documentation/csh/1.9/admin/template/SMSAppointment

• http://www.openvpms.org/documentation/csh/1.9/admin/organisation/appointmentReminder

• http://www.openvpms.org/documentation/csh/1.9/admin/organisation/schedule

• http://www.openvpms.org/documentation/csh/1.9/admin/organisation/mail

• http://www.openvpms.org/documentation/csh/1.9/admin/organisation/location

• http://www.openvpms.org/documentation/csh/1.9/admin/organisation/practice

• http://www.openvpms.org/documentation/csh/1.9/reference/setup/sms

• http://www.openvpms.org/documentation/csh/1.9/workflow/scheduling/edit

• http://www.openvpms.org/documentation/csh/1.9/workflow/scheduling

• http://www.openvpms.org/documentation/csh/1.9/how/appointmentReminder

• http://www.openvpms.org/documentation/csh/1.9/new-features

updated JIRA to reflect project spec

This would require the following changes to:

• party.organisationPractice to add the nodes:

  • appointmentSMS - enables/disables appointment reminders by SMS

  • appointmentSMSInterval - the no. of hours, days, or minutes prior to an appointment when reminders should be sent

  • appointmentSMSUnits - determines the units of appointmentSMSInterval

  • appointmentSMSExpression - xpath expression used to generate SMS text. E.g., default could be "concat('You have a veterinary appointment for ', openvpms:get('patient.entity.name'), ' at ', /startTime)"

• act.patientReminder to add the nodes:

  • sms - indicates that SMS reminders may be sent for the appointment. Defaults to "true"

  • smsLastSentDate - indicates if an SMS reminder has been sent. This is to avoid sending duplicate reminders if the server restarts

• the appointment editor to:

  • display the "sms" flag if the party.organisationPractice appointmentSMS flag is true.

  • display a hint regarding the customer's SMS status. i.e if the customer has a contact.telephoneNumber with sms enabled/disabled. Displayed subject to the same criteria as the "sms" flag

• add a scheduler that monitors appointment changes and sends out SMS reminders for those that match have "sms" set true, and whose customer allows SMS reminders.

• the party.organisationPractice editor to add an expression editor for the appointmentSMSExpression node. This would enable the node to be tested against a sample reminder.

• log messages to the messaging workspace if an appointment reminder cannot be sent due to the expression exceeding 160 characters

Notes:

• updates to appointment times would necessitate clearing of the smsLastSentDate so that a new reminder can be sent out (subject to reminder intervals)

• a customer's contact.telephoneNumber sms node can change subsequent to an appointment being made, so all appointments with "sms" set true need to be evaluated against the customer's SMS preferences, rather than solely relying on the act.patientReminder "sms" node. Similarly, the act.patientReminder "sms" node cannot be defaulted to that of the customer's SMS preferences as a customer SMS preferences can be changed.