Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update case when person's condition is set to "Dead" or "Buried" [3] #13211

Open
1 task
SORMAS-JanBoehme opened this issue Dec 11, 2024 · 3 comments
Open
1 task
Assignees
Labels
change A change of an existing feature (ticket type) lu Adaptations requested by or implemented for Luxembourg pertussis

Comments

@SORMAS-JanBoehme
Copy link

SORMAS-JanBoehme commented Dec 11, 2024

Problem Description

See Epic #13208

Proposed Change

See Epic #13208

Added Value/Benefit

See epic #13208

Acceptance Criteria

  • Popup behaves as described in "implementation details"

Implementation Details

When a user tries to save the person form while the field "Present condition of person" is either "Dead" or "Buried" AND "Cause of Death" is "Epidemic Disease", the following check has to be performed on all associated cases:

Does the person have one or more associated cases where:
Is Person.responsibleDisease equal to CaseData.Disease

If No, no action required, save form as normal

If Yes:
Are there more than one associated cases?

If No:
Continue with next check with the one case found

If Yes:
Use the newest case (Report Date) for the next checks.

Does the selected case fulfill the following conditions:
Is Case.outcome equal to DECEASED?
AND
Is Person.DateOfDeath equal to CaseData.outcomeDate?

If Yes:
no action required, save form as normal

If No:
A popup appears that shows the consequences of their actions. See Mockup for information about how the popup looks and the shown text (new localization IDs need to be added if required, otherwise reuse the current localization IDs where possible)

Variables are marked with Curly Brackets:
{CaseData.Disease} = Current value of the field "Disease" of the case
{CaseData.UUID} = The UUID of the case
{Person.deathDate} = Current value of the field "Death Date" of the person

Click on "Discard":

  • The pop up closes
  • The form is not saved

Click on "Save":

  • Values of case are updated in the database according to the shown data
  • the pop up closes
  • The form is saved

Mockups

image

Additional Information

No response

@SORMAS-JanBoehme SORMAS-JanBoehme added the change A change of an existing feature (ticket type) label Dec 11, 2024
@SORMAS-JanBoehme SORMAS-JanBoehme changed the title abc Update case when person's status is set to "Dead" or "Buried" Dec 11, 2024
@SORMAS-JanBoehme SORMAS-JanBoehme changed the title Update case when person's status is set to "Dead" or "Buried" Update case when person's condition is set to "Dead" or "Buried" Dec 11, 2024
@SORMAS-JanBoehme SORMAS-JanBoehme added lu Adaptations requested by or implemented for Luxembourg pertussis labels Dec 11, 2024
@SORMAS-JanBoehme
Copy link
Author

@markusmann-vg not directly related to pertussis, but came up when discussing the requirements

@markusmann-vg
Copy link

@SORMAS-JanBoehme Is this for Lux only or should it apply in general?

@SORMAS-JanBoehme
Copy link
Author

@markusmann-vg this is a general change

@markusmann-vg markusmann-vg added this to the Sprint 4 - SORMAS 1.101 milestone Dec 19, 2024
@markusmann-vg markusmann-vg changed the title Update case when person's condition is set to "Dead" or "Buried" Update case when person's condition is set to "Dead" or "Buried" [3] Jan 13, 2025
@sergiupacurariu sergiupacurariu self-assigned this Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change A change of an existing feature (ticket type) lu Adaptations requested by or implemented for Luxembourg pertussis
Projects
None yet
Development

No branches or pull requests

3 participants