[ https://openvpms.atlassian.net/browse/OVPMS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11951#action_11951 ]

Tim Anderson commented on OVPMS-902: ------------------------------------

60 hours to: * develop interface for SMS messaging * provide implementation of the interface that supports SMS via email * provide archetypes to configure at least 2 email to SMS gateways (e.g clickatell.com, messagenet.com.au') - up to you * provide editor to configure the gateways - this includes support for sending a test SMS through to verify it works * provide SMS button in customer summary to send SMS to default mobile if a customer has one * provide SMS button in phone contacts to send SMS to arbitrary mobile

Can cost on reminder SMSs too if you like.

> SMS integration through an email-sms gateway > -------------------------------------------- > > Key: OVPMS-902 > URL: https://openvpms.atlassian.net/browse/OVPMS-902 > Project: VPMS Web Application > Issue Type: New Feature > Reporter: Matt Costa > Assignee: Tony De Keizer > > The goal is to get SMS communication into the following areas: > 1. Within the Customer summary will contain an SMS button. The button will only be enabled if there is a valid mobile number for the Customer that has an active Customer-Patient relationship. This would pop up a standard compose email dialogue with the email address formatted appropriately for the email-sms provider (eg.i.e 0411999999@smsprovider.com.au ). > 2. The ability to ADD SMS reminders as a method of delivery of reminders from within the Reminder configuration if a Customer has a valid mobile number. > 3. Add SMS email gateway provider to Practice Organisation. > 4. (Optional) Identical functionality and context for Fax sending by utilising email-fax gateway options. Note that this could integrate very well with sites where hylafax may already be operational. > > Forum: www.openvpms.org/forum/sms-project

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf

[ https://openvpms.atlassian.net/browse/OVPMS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11776#action_11776 ]

Tim Anderson commented on OVPMS-902: ------------------------------------

I envisage the default implementation would work as follows: * configuration for the gateway is via a custom entity, with prefix entity.emailSMSGateway * the SMS gateway configuration would be linked to the practice via an entity relationship with target archetype entity.emailSMSGateway* * a practice would have at most 1 entity.emailSMSGateway * an entity.emailSMSGateway would contain at least the following nodes: ** to - this indicates the format of the to address ** body - this indicates the format of the message body ** practice - link to the practice * when generating the message, the implementation would evaluate the to address and body supplied in the configuration using xpath. The following variables would be defined: ** phone - the mobile no ** text - the SMS text

E.g, for clickatell above, there would be an entity.emailSMSGatewayClickATell. This would have the following nodes: * to * body * user * password * api_id * reply

An instance of this might look like: * to = sms@messaging.clickatell.com * body {noformat} concat('user:', openvpms:get(., 'user'),'\n', 'password:', openvpms:get(.,'password'), '\n', 'api_id:', openvpms:get(.,'api_id'), '\n', 'to:', $phone, '\n', 'reply:', party:getEmailAddress(openvpms:get(. 'practice.source')), '\n' 'text:', $text) {noformat}

For messagenet, it would be entity.emailSMSGatewayMessageNet. This would have the following nodes: * to * body * from

An instance of this might look like: * to = concat($phone, '@messagenet.com.au') * body = $text * from = party:getEmailAddress(openvpms:get(. 'practice.source'))

> SMS integration through an email-sms gateway > -------------------------------------------- > > Key: OVPMS-902 > URL: https://openvpms.atlassian.net/browse/OVPMS-902 > Project: VPMS Web Application > Issue Type: New Feature > Reporter: Matt Costa > Assignee: Tony De Keizer > > The goal is to get SMS communication into the following areas: > 1. Within the Customer summary will contain an SMS button. The button will only be enabled if there is a valid mobile number for the Customer that has an active Customer-Patient relationship. This would pop up a standard compose email dialogue with the email address formatted appropriately for the email-sms provider (eg.i.e 0411999999@smsprovider.com.au ). > 2. The ability to ADD SMS reminders as a method of delivery of reminders from within the Reminder configuration if a Customer has a valid mobile number. > 3. Add SMS email gateway provider to Practice Organisation. > 4. (Optional) Identical functionality and context for Fax sending by utilising email-fax gateway options. Note that this could integrate very well with sites where hylafax may already be operational. > > Forum: www.openvpms.org/forum/sms-project

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf