Closed ageryck closed 2 years ago
NOTES
@ageryck The Remove Member Form (Died)
tab in the data dictionary was locked so I created a duplicate called Copy of Remove Member Form (Died)
tab and suggested edits with red text.
GENERAL FEEDBACK FOR CLEANING UP THE DATA DICTIONARY
Remove Member
and Out of Area Death
forms. I found some inconsistencies. Add Child Under N - Out of Area
tab looks incomplete and does not have the birth certification questions. SPECIFIC FEEDBACK FOR DEATH REPORTING
Preferably, if a family only has one person, the error message would state: "This family only has one member. Please confirm if you would like to remove the entire family." Then a button that takes you to "Remove family" page.
[x] @ageryck mentioned that the Remove family member
and Remove child under 5
forms should assume that the reason for removal is Death. Therefore, the "Reason" field can be removed entirely. If this is the case, please ignore the next comment. : - Client request reason removal however based on his recent sentiments regarding exploring integrating this app with WCARO, there need to retain the base CFC app features with very minimal deviations. I have therefore decided to retain the reason question since it makes sense at family registry
[x] Remove family member
form should not display the question "Was the deceased admitted to a health facility in the past 4 weeks?" and "Do you know the cause of death?" unless the "Reason" for removing the family member is "Died." :- Edits introduced in the DD and task queued for engineering
[ ] The Remove family
form currently only gives 2 options: "Moved away" and "Other." This form should look the same as the Remove family member
form.
[x] Remove child under 5
form should look the same as Remove family member
form EXCEPT: :- Queued for engineering
[ ] Do not display "Marital status" question in 'Remove child under 5' form
[ ] Addition of "Was this a stillborn death?" if the deceased was <27 days old.
[x] Please change phasing of the question "Was MCCD conducted?" to "Was a medical certificate of cause of death (MCCD) issued?":- Changed and queued for engineering
[x] Instead of writing "Death certificate issuance date (if certificate received)" and "Death certificate number (if certificate received)", we should make those two questions relevant only if the answer to "Does the family of the decedent have a death certificate?" "Yes".
[x] The notes in rows 64 and 65 of the Remove Family Member (Died)
tab and rows 77 and 78 of the Record Death Form - Out of Area (New)
tab do not make sense. They say:
[ ] "Ask to see the death notification and instruct the family member to register the death at CRO. (if death notification done)" If death notification was already done, why would they need to register the death at the CRO again?
[ ] "Instruct the family member to have the death registered at CRO. (if birth notification not done)" I think the parentheses should say "If death notification not done."
[ ] The notes are also not displayed in the forms. I don't know if this is intentional or an oversight
[x] The pregnancy questions are not displaying even when removing family members that are women of reproductive age. There are two questions: [ ] "Was the deceased pregnant?" [ ] "Did the pregnancy contribute to her death?"
[x] The relevance for "Do you know the cause of death?" was different in the Remove Member Form
tab and Record Death Form - Out of Area (New)
tab. Based on this workflow diagram, I updated the Remove Member Form
sheet to "{medically_treated} = "Yes". :- _Correctly captured on the DD its application if place of death is not HF ({deathplace != "Health Facility"})
[ ] Change text "Removing entire family" to "Remove entire family." I don't know where in the data dictionary to specify this.
[x] Ager should the Out of area death
page and Death certification
page look the same? :- No, they are not the same, out of area registration includes patient details hence update details. Death certification manages the certification status hence Certified and Not Certified
[ ] Is there any reason it says "update status" on the Death certificate
page vs "update details" on the Out of area death
page? I think consistency helps to avoid confusion for CHWs. :- Not they should not look the same the certification page collates data from different sources and is only focused on updating certification details and not patient details
[x] I don't see "Certificate received" and "Certificate not received" statuses displaying in the Out of area death
page. Steps to replicate: :- This should only be for Death Certification for Out of Area death we register patients hence the status keeps showing update details
SPECIFIC FEEDBACK FOR BIRTH REPORTING
[x] When I update the status of a child in the Birth Certification
page, the data does not appear to save. Steps to replicate:
Birth Certification
pageAll Families
page and when I go back to Birth Certification
page, the information I entered for Angela Cavuto is unsaved and her status is not updated. : - reproduced and queued for engineering[x] The notes (e.g. rows 16 and 17 in the Birth Certificate Form
) are not appearing :- Notes removed as requested by client and cleaned on DD
[x] The out of area birth form should include all questions in the Birth Certificate Form
tab. :- Questions were available and separated on the Birth Certification Form since there's no harm in answering them at the point of registration this request is queued for app engineering
[x] Birth certification does not display "Certificate received" and "Certificate not received" statuses. :- Cannot be reproduced
Please remove the Liberia logo from the CRVS login page.
Please remove the Liberia logo from the CRVS login page.
We will replace this with DRC logo for the current CFC App, client did not share any specific app branding
@ageryck @joyce-x-chen just reviewed the app from https://onaio.slack.com/archives/C01KKF9LUR1/p1643981557660599 and read the thread above (tried not to reproduce the known issues).
The Remove family form currently only gives 2 options: "Moved away" and "Other." This form should look the same as the Remove family member form.
The "Remove family" and "Remove family member" forms cannot be the same since the fields aren't the same and we don't really want the remove family to be like a bulk death reporting form either. The workflow for removing the last remaining person would probably be doing the "remove family member form" with a confirmation in step one that you are removing the last person, which will delete the family/structure as well. If you are trying to remove the entire family and want to say they all died, I feel like you'd have to report each one died first, then remove the family.I don't see "Certificate received" and "Certificate not received" statuses displaying in the Out of area death page.
which I am also seeing.I also noticed some statuses not updating/saving. If we can prioritize those... they are probably the main issue to figure out before UAT. If you are having trouble replicating @ageryck maybe we should have a meeting to identify the broken things vs. stuff we can live with.
@rowo good point about not using remove entire family
to register the death of a person who lives alone. I proposed that as a workaround to the logic that prevents one from using the remove family member
without re-assigning head of household. In this case, we cannot register the death of an individual who lives alone. Is it necessary to keep the logic that prevents the removal of a family member without re-assigning head of household? cc: @ageryck
@ageryck Leigh and I have noticed while testing the CRVS app that we periodically get logged out of the app and receive the following error message: “you have been logged off as your account has been disabled.” In this Slack thread, we received a few suggestions:
This is a nice to have - if there isn't time to squeeze this in, that's ok.
@rowo good point about not using
remove entire family
to register the death of a person who lives alone. I proposed that as a workaround to the logic that prevents one from using theremove family member
without re-assigning head of household. In this case, we cannot register the death of an individual who lives alone. Is it necessary to keep the logic that prevents the removal of a family member without re-assigning head of household? cc: @ageryck
looking into this
@ageryck Leigh and I have noticed while testing the CRVS app that we periodically get logged out of the app and receive the following error message: “you have been logged off as your account has been disabled.” In this Slack thread, we received a few suggestions:
- [ ] Increase the time before a user is automatically logged out, and it should be following a period of inactivity.
- [ ] Display a different error message such as "You have been logged out due to inactivity. Please log in again."
This is a nice to have - if there isn't time to squeeze this in, that's ok.
@allan-on will be looking on this logged under this issue
majority of listed issues have been translated into tshirt size issue and already handled pending QA on the project board, closing this while parking the entire family removal issue for future handling
From @joyce-x-chen here are the bug reports:
1.Relevance and select one options should be specified in the relevant columns in the data dictionary, not written in the label columns and displayed to the CHW. Can we please clean this up? For example [ ] We don't need to display "(Y/N)" to the CHW. "Yes" and "No" will appear in the drop down list
QA Results Actual Results: "(Y/N)" is still displayed see screenshot below
Expected Results: "(Y/N)" should not be displayed
[] We don't need to display "(if death notification done)" to the CHW. We should just note the relevance {death notification}="Yes" for programming the workflow
QA results:
Death notification is displayed see screenshot below
Expected results:
Death notification done should not be displayed only note the relevance {death notification}="Yes" for programming the workflow
From issue "Please remove the Liberia logo from the CRVS login page" Logo has been changed From Liberia to “Justice Paix Travail” See screenshot below !
@ageryck Report on the following : The Relationship descendant drop down Sibling is shown twice see screenshot below Steps to reproduce 1.Login 2.Click menu 3.Click Death Certificate 4.Click on update status 5.Select Relationship to decedent
This will be a holder issue for bug reproduced and suggested changes, each task resolved or assigned to an engineer will be marked as done;
[x] Change nationality spinner to a text box in Family member registration, out_of_area_death_form, family_details_remove_member and family_register
[x] update status in death summary; form to ask all questions asked in remove family member form. Currently ask partial question but only if death certificate is YES. Manner of death is asked as an open text rather than drop down spinner options.
[x] Remove family member for under 5 should ask all question in remove family member form
[x] Edit/Update Death certification; form not loading back saved records
[x] Out of Area Death; MCCD follow on questions relevance not implemented
[ ]