Actions
User Story #974
openEPIC #960: # Patient & Household Registration
# OTP Verification
Status:
To Do
Priority:
low
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
OTP Verification¶
Business Objective¶
Verify that the household's mobile/WhatsApp number is real.
The V3 workflow specifies OTP during first household creation. It is not intended to block treatment; if OTP cannot be completed, the number remains unverified.
Frontend Story¶
US-001-01-09-01-FE
Display OTP verification flow.
States:
OTP Sent
Enter OTP
Wrong OTP
OTP Expired
Resend OTP
Unable to Send
Verified
Skipped / Unverified
Acceptance Criteria¶
- OTP entry is displayed after household creation.
- User can submit OTP.
- Wrong OTP displays an error.
- Expired OTP displays an appropriate message.
- Resend is available according to configured rules.
- Verification success is clearly shown.
- Failure does not prevent patient treatment/registration.
Backend Story¶
US-001-01-09-01-BE
Generate, send and verify OTP.
Acceptance Criteria¶
- OTP is generated securely.
- OTP has expiry.
- OTP cannot be reused after successful verification.
- Incorrect OTP is rejected.
- Verification status is stored.
- Resend is rate-limited.
- External messaging failure does not corrupt household data.
No data to display
Actions