...
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?
| Use case | User groups | Existing? | Prerequisite? | Priority
| 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. |
|
| 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. |
|
| |||||||||||||||||||||||||||||||||||||||||
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. |
...
The strategy around mobile money
Technologies?
Standards?
Non-functional requirements
offline capable
themeable
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 backend
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