-
Type:
Story
-
Resolution: Done
-
Priority:
High
-
Affects Version/s: None
-
FLW Sprint 34, FLW Sprint 35
-
FLW Mobile App
-
All
As an ASHA, I want to be able to record leprosy screening details, mark cases as suspected or confirmed, and manage follow-up visits, so that I can ensure timely diagnosis, referral, and monitoring of leprosy cases in the community.
Case Listing
- Show existing line listing of Households under Leprosy Screening
- Add a separate listing line of “Suspected” cases with count on Top.
- Add a separate listing line of “Confirmed ” cases with count on Top{}.
- Provide edit option to:
- Confirm the type of Leprosy (MB/PB)
- Record follow-up details for confirmed cases.
| Field Name | Type | Fields / Logic |
|---|---|---|
| Date of Home Visit | Text Box | Auto-display Today’s Date. Should be non-editable. |
| Leprosy Symptoms Present | Radio button Yes/No |
If “Yes”, automatically set Leprosy Status = Suspected. |
| Visit | label | Visit -1 |
| Leprosy Status | Dropdown | Options: • Screening (Default) • Suspected • Confirmed • Not Confirmed • Treatment Started • Treatment Completed • Recovering • Death |
Rules: - Default = “Screened”.
|
||
| Referred To | Dropdown | Options: PHC / CHC / DH / Medical College Enable only if “Leprosy Status = Suspected”. Partial incentive to be calculated for suspected cases. |
| Suspected Cases | ||
| Type of Leprosy | Radio button | Options: MB (Multibacillary) PB (Paucibacillary) Enable only when “Leprosy Status = Suspected”. if PB or MB is selected then, “Leprosy Status = Confirmed” |
| Treatment Start Date | Date Picker | Enabled only when “Leprosy Status = Confirmed”. |
| Confirmed Cases | for Confirmed Cases, button should be "Follow Up" | |
| Follow-Up Visit Date | Calendar | Frequency of follow up visit is monthly one visit is allowed Enabled only when “Leprosy Status = Confirmed”. Follow-up logic:
|
| MDT Blister Pack Received? | Yes/No | Optional. |
| Treatment Status | Drop Down | Options: Recovering, Cured, Recurrence of Symptoms, Regularly taking medicine, Not regularly taking medicine, Treatment Completed |
| Treatment Complete Date | Date Picker | Enabled when “Treatment Status = Treatment Completed”. |
Acceptance Criteria
| S.No. | Condition | Expected Outcome |
|---|---|---|
| 1 | ASHA opens Leprosy module and enters new screening | “Date of Home Visit” auto-fills with today’s date (non-editable) |
| 2 | ASHA marks “Symptoms Present = Yes” | “Leprosy Status” auto-sets to “Suspected”; referral alert shown |
| 3 | ASHA tries to select “Confirmed” without being “Suspected” first | System prevents selection and shows validation message |
| 4 | ASHA selects “Suspected” | “Referred To” field becomes active; partial incentive triggered |
| 5 | ASHA marks “Confirmed” | “Type of Leprosy” and “Follow-up Visit Date” become active |
| 6 | “Type of Leprosy = PB” | Beneficiary appears in To-Do list for 6 months |
| 7 | “Type of Leprosy = MB” | Beneficiary appears in To-Do list for 12 months |
| 8 | ASHA records multiple follow-ups | System allows multiple entries with date validation |
| 9 | ASHA marks “Treatment Completed” | “Treatment Complete Date” field becomes active |
| 10 | Status flow check | Transitions follow logical sequence without skipping intermediate steps |
- is blocked by
-
AMM-1949 Up Sync & Down Sync API for leprosy
-
- Pending QA
-
- relates to
-
FLW-677 Update logic in CBAC Screening for identification of new leprosy patients
-
- Closed
-
-
FLW-678 Tracking for Leprosy confirmation and type
-
- Closed
-
-
FLW-679 Follow up and tracking of MB and PB leprosy cases
-
- Closed
-
-
FLW-698 Add Leprosy Symptoms Checklist and HWC Referral Flow in Screening Module
-
- Closed
-