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

Disable Contact Management for RSV Cases [0.5] #13157

Closed
10 tasks
markusmann-vg opened this issue Oct 8, 2024 · 2 comments · Fixed by #13178
Closed
10 tasks

Disable Contact Management for RSV Cases [0.5] #13157

markusmann-vg opened this issue Oct 8, 2024 · 2 comments · Fixed by #13178
Assignees
Labels
change A change of an existing feature (ticket type) qa-verified Issue has been tested and verified by QA RSV

Comments

@markusmann-vg
Copy link

Problem Description

For RSV, contact tracing is not required, and therefore, the contact management functionality should be disabled. The system should ensure that no contacts can be linked, displayed, or added for RSV cases in any part of the system. This behavior should be governed by the "follow up enabled" parameter, which should be set to false for RSV in the disease configuration.

Proposed Change

Disable Contact Linking for RSV:

  • It should not be possible to link a case managed as RSV via the "Contacts" section.
    Remove Contact Management in Case Person View:
  • In the "Case Person" tab, users should not be able to add contacts when viewing an RSV case.
  • The right-side navigation should not display any contact-related information for RSV cases.
    System-wide Check:
  • Review and ensure that in every part of the system where a contact can be added or linked, the option is disabled or hidden for RSV cases.
    "Follow Up Enabled" Parameter:
  • The "follow up enabled" parameter should be set to false for RSV in the disease configuration, which controls the contact management functionality.

Added Value/Benefit

Increased Workflow Efficiency:
By removing unnecessary contact management options for RSV, users can focus solely on the relevant aspects of case management. This streamlines the workflow, eliminating the distraction of unrelated tasks.

Reduced User Confusion:
Since contact tracing is not required for RSV, disabling this feature simplifies the user interface. Users won’t need to navigate or worry about contact tracing elements, making the system easier to use and reducing potential errors or misinterpretations.

Acceptance Criteria

  • The "Contacts" section should not allow linking to RSV cases.
  • In the "Case Person" view, contacts should not be able to be added or displayed when the case is RSV.
  • The right-side navigation in the "Case Person" view should not display contacts for RSV cases.
  • Ensure that across the system, no contact can be created, linked, or displayed for RSV cases.
  • The "follow up enabled" parameter should be set to false for RSV, ensuring that contact management is disabled for RSV cases.

Implementation Details

No response

Mockups

No response

Additional Information

No response

@markusmann-vg markusmann-vg added the change A change of an existing feature (ticket type) label Oct 8, 2024
@markusmann-vg markusmann-vg changed the title Disable Contact Management for RSV Cases Disable Contact Management for RSV Cases [0.5] Oct 16, 2024
@sergiupacurariu sergiupacurariu self-assigned this Oct 24, 2024
@markusmann-vg markusmann-vg added this to the Sprint 2 - 1.99.0 milestone Oct 29, 2024
@leventegal-she
Copy link
Contributor

Case person view must have the contact section because a person that is a covid contact can have also RSV case without duplicating the person.
Person view is not hard linked to case, the same person can have any number of cases and contacts with any disease.

@markusmann-vg Wouldn't be better to just don't allow creating contacts with a disease that doesn't have followup enabled?

leventegal-she added a commit that referenced this issue Nov 11, 2024
…e_contact_management_for_RSV_cases

#13157 - Disable Contact Management for RSV Cases
@richardbartha richardbartha added the qa-verified Issue has been tested and verified by QA label Nov 13, 2024
@richardbartha
Copy link
Contributor

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) qa-verified Issue has been tested and verified by QA RSV
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants