Analysis of high-level checklist (During estimation and when breaking down stories)
Is there a need to check for eligibility checks in the encounters(Example: if the encounter we have this check which is used to restrict the unplanned visit)
Offline dashboards, reports, and inbuilt dashboards(check if we added the custom dashboard is displayed on the home page if no dashboard is added then we have to display the inbuilt dashboard on the home page ).
What user groups will be required (with a high-level understanding of permissions)? Primary and secondary dashboards for user groups.
Check for auto-generated identifiers
Search filter and my dashboard filter configuration
Analysis Story Checklist
Specify mandatory check
Approx Number of locations and hierarchy
Types of User roles and permissions
If it is numeric then provide range and whether negative, decimals are allowed
Date fields are future and past dates allowed
If we have a group subject check for add member, exit member
For phone numbers use the phone number data type
Subject Registration Forms
At what location type should the registration be done.
Group and member subject type configuration
On registration which general encounters are scheduled and their logic
Past and Future registration dates
Custom/Offline dashboard reports
Specify behavior for
exited enrolments
voided data
canceled encounters
encounter date or scheduled date
Program enrolment/exit forms
Whether multiple enrolments are allowed for a program.
On enrolment which encounters are scheduled and their logic
Past and Future enrolment dates
Encounter forms
What should happen on a canceled encounter?
Are unplanned visits allowed?
Past and Future encounter dates
Check for user permission if the new encounter is added in the old organization.
Dev Checklist
All the items in the analysis story checklist are present in the story/doc
If we update the name of the encounter, Subject, or program check the and update the rule according to it.
UAT and Warranty Phase
Check for rule failures
Testing Checklist
After enrolling into the program if the general encounter is scheduled and we edit the enrollment we should not schedule a visit again.
Likewise, we have to handle all visit cases.
We need to handle if we edit the old visit it should not schedule the visit again.
(schedule A date of visit: 06/01/2024 and Schedule B date of visit: 07/01/2024 if we edit the Schedule A visit it should not schedule visit B again)
We need to handle the unplanned visit when editing the unplanned visit. It should not schedule the next visit again.
NOTE: if anyone finds any scenario that needs to be added in the checklist please feel free to add it.
Link for the checklist doc click here
Analysis of high-level checklist (During estimation and when breaking down stories)
Analysis Story Checklist
Specify mandatory check
Approx Number of locations and hierarchy
Types of User roles and permissions
If it is numeric then provide range and whether negative, decimals are allowed
Date fields are future and past dates allowed
If we have a group subject check for add member, exit member
For phone numbers use the phone number data type
Subject Registration Forms
Custom/Offline dashboard reports
Program enrolment/exit forms
Encounter forms
Dev Checklist
All the items in the analysis story checklist are present in the story/doc
If we update the name of the encounter, Subject, or program check the and update the rule according to it.
UAT and Warranty Phase
Testing Checklist
After enrolling into the program if the general encounter is scheduled and we edit the enrollment we should not schedule a visit again.
NOTE: if anyone finds any scenario that needs to be added in the checklist please feel free to add it.