This is page to define a strategy for the use of mobile technologies in openIMIS. It’s foundations lie in a report on the potential of mobile technologies in openIMIS by Nils Kaiser but is intended to be a collaborative process among the openIMIS community. This strategy should serve as guidance for some of the software development efforts within openIMIS.
Background
Current developments/situation
Functions/Business processes supported through mobile use (current and future)
Beneficiary Management
Enrolment
Renewals
Update
Claims Management
Claims Entry
Claims review
Data Analytics
System Administration
Insure portal
Technologies to be used
Android
Java/Kotlin
PWA
SMS / USSD …
Technology | Requirement | Supported interaction | Applicable?YES MAYBE NO | Use case | User groups | Existing? | Prerequisite? | Priority HIGH MEDIUM LOW | Notes |
|---|---|---|---|---|---|---|---|---|---|
SMS | Basic phone, 2G, Literacy. Shortcode to ensure free SMS | Basic interactions, Notifications. No limit on number of steps for dialogue, but gets cumbersome above 5-10 steps. | YES |
| SMS costs are quite high. Implementers/Users need to be aware | ||||
IVR | Basic phone, 2G, Phone familiarity. Shortcode to ensure free calls. | Very basic interaction but doesn’t require literacy (except “Press 5”). Can record messages and allows transfer to a real agent in urgent cases or as fallback. | MAYBE |
| |||||
USSD | Basic phone, 2G Literacy. Aggregator. | Basic interactions. Can support longer interactions Potential timeouts (USSD is like a call). | |||||||
Mobile Web | Smartphone, 3G/4G, Smartphone familiarity. Web server/ domain required | Complex interactions. Limited offline capabilities are available. Progressive web apps can be installed on a home screen and receive notifications, thus mirroring a lot of native functionality. However, progressive web apps have longer initial load times - though much faster in subsequent loads - and require the development of an app according to specific technologies. | |||||||
Mobile App | Smartphone, 2G or 3G/4G, Smartphone familiarity Web server / domain required. | Complex interactions. Offline-mode is available with syncing data upon the availability of network connection. |
Roadmap Strategy
Priorities for new development
Mobile-first? (for some functionality? eg. enrolment - most of the use now and in future will be done through the mobile interface - does it make sense in the re-design to have UI/functionality that serves the mobile interface better if a choice has to be made between mobile/browser?)
Improve exiting functionality? Which ones?
Develop new functionality? (eg. client portal)
Strategic orientation
Develop openIMIS specific apps? One app for everyone? OR template app for every implementation to customize?
Build ‘modules’ in existing global goods - eg. ODK?
Integrate other global goods with similar functionality? (eg. Meso-health - now open source at: github.com/meso-health )?
The strategy around mobile money
Technologies?
Standards?
Non-functional requirements
offline capable
themeable
Requirements Solutions
table should include
Solution title “USSD-based inquiry” or “mobile app for insurees”
Target users
Usecases / Covered business processes
Prerequisites
Decision criteria
Requested by implementers
complexity
maintenance
development
does it allow to reuse existing Infrastructure, API, Mobile code…
New development language yes / no
Access with back-end
Robustness of the connection
Robustness (deal with complex data)
Synchronization
implementation / deployment
training & version management
Running costs
Strategy
Use of standards
Supported by or other eHealth solutions
Roadmap
Immediate action (within the scope of the current contracts)
Avail the App on Google Play for Demo
Verify that Google Play account is an official openIMIS Account
Privacy Policy for Google Play
Server Strings point to demo server
Upload to Google Play
Avail the App on Google Play as Generic App (e.g. via config file)
config file for
server string (url, password etc)
(additional attributes - low hanging fruits)
quick guide in Installation and Country Localisation
Mid-term action (needs new funding)
Avail the App on Google Play per Implementations (will be in the responsibility of the implementer)
Privacy Policy as template Mobile Applications Privacy Policy
Enable flavoured builds by implementing organisations
Step-by-step guide Installation and Country Localisation
Warning about later upgrades: publishing in Google Play doesn’t mean people have it installed (latest version) on their mobile.
‘Corporate’ world use to rely on ‘User Endpoint Management solutions’ such as mobileiron, , Microsoft Intune, etc. Additional costs might be required.
Long-term Vision
Questions to be answered:
Design of the mobile applications UX/UI
Combination of the functionalities in only one app: modular mobile application
Web/native solution: Android vs PWA
Client mobile app