@sue - I very much welcome your enthusiasm! Let me know if you have any questions. As well, any partners/MoH’s you know that might be interested in this feature, should be ready to upgrade to the FR. This will effectively be upgrading to 3.16.
@Jane_Katanu - so great to hear about different use cases that may not be compatible with our current proposed workflow! It’s good to appreciate differences so we can maybe add revisions in the future to accommodate them. While far from exhaustive, my research didn’t uncover the use case you described. I’d love to hear from others though! Do you know how common the personal SIM use in the deployment you’re thinking of?
While we’re here, so I understand the situation correctly, the CHW’s personal SIM flow might be:
- CHW A inserts their SIM into MoH provided phone, they commence work as a CHW
- CHW A needs to leave work, but there is no connectivity. The supervisor opts to use the offline replace feature
- CHW A removes SIM and gives MoH provided phone to supervisor
- Supervisor finds CHW B as a replacement for CHW A
- The replace user form is filled out by the supervisor, specifying the new number on CHW B’s SIM
- CHW B inserts their SIM into the MoH provided phone
- At some point in the future CHW B synchronizes all of the documents and gets logged out.
- The token login link is sent to to CHW B’s new phone number, they receive and click it
An alternate step might be that the supervisor provides an MoH SIM in step 6, but the work flow would remain unchanged.
I’d love to hear about any other restrictions you’re facing, as well as any non-restrictions! Maybe, for example, you’re only interested in the “CHW Replace” aspect and the “offline” part is not interesting?