Anyone (users in field and module developers) with use cases not documented should let the project team know ASAP so they can try to include them in the design.
SMSlib currently supports two online SMS gateways but they are outbound-only.
JEMBI is very interested in SMS messaging functionality and working on an OpenMRS system for athletes and would like to communicate to them via SMS in some way.
Zeshan discussed OMHE microsyntax. Carl from JEMBI will look at it and see what part of OMHE would be useful to them, and get back to Zeshan.
Carl asked about OpenROSA and how this project relates to it. Zeshan said that larger, complex messages aren't practical over SMS. This project will exist purely on the server side, not phone/client side like OpenROSA.
Tammy Dugan discussed her group's "Pearl Girls" project. They will be giving phones to 30 teenage girls and periodically survey them for high risk behaviors, combining those results with GPS coordinates. They would probably be using a mobile web kind of solution at this point so it would be phone-independent. The survey would have a total of 150-200 total questions, but answers would determine the skip logic that would reduce that number.
Timeline: A working module should be available by March 15 that supports 2-way appointment reminders. (e.g., "Will you make your appointment? Y/N" with an appropriate response.)
Justin has written some messaging service code in core that sends e-mail. Darius suggests using this new module as something that would plug in to or replace this service code in core. The new module is planned to eventually support other short message forms beyond SMS (e.g., Twitter et al).
IU is hosting a development server for the project, and Dieterich has been getting it set up this week. Development will get started today.
The module still needs a name and some ideas were discussed. Paul wants to make sure the name of the module itself is representative of its functionality.
An update on the project is scheduled for next week's meeting.
Conference call logistics
Paul asked if we should reconsider the time for the meeting. We now have some people in the Western US, but also want to try to make it accessible to people in Africa.
Darius stated that due to another call before this one, and the need to respect people in Africa, he felt we should keep the call where it is.
The consensus was to keep the call at the same time for now.
Darius discussed some security topics, such as authentication and forcing users to change their password. A discussion should happen about where in the code these kind of security issues should be handled (core vs. webapp). He would also like to get feedback from Ben and Burke. Darius will set this topic for another meeting.
Any to-do's that come out of code reviews that need discussion the community should be discussed on the developer mailing list.
After-action review & next week's agenda
Everyone agreed the new conference service worked well. It will be used for future meetings.
Pascal will discuss with his colleagues and arrange a time for the JEMBI team to discuss their work and introduce themselves. They will put this down on the agenda for an upcoming meeting soon.