Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@sormas-api/src/main/java/de/symeda/sormas/api/exposure/ExposureDto.java`:
- Around line 470-472: The sexualContact field in the ExposureDto class is
missing the `@SensitiveData` annotation, which is required for proper
sensitive-data access control. Add the `@SensitiveData` annotation above the
`@Diseases` annotation on the sexualContact field to ensure it is properly
protected as sensitive data.

In `@sormas-api/src/main/java/de/symeda/sormas/api/sample/PathogenSpecie.java`:
- Line 206: The enum constant SHISPP in PathogenSpecie.java was renamed from
SHIGELLA_SPP, but this breaking change requires three synchronization updates to
prevent deserialization failures and UI display issues. Update all 46 language
enum.properties files (enum.properties, enum_en-KE.properties, etc.) to replace
Pathogen.SHIGELLA_SPP with Pathogen.SHISPP. Update sormas_schema.sql to replace
the seed value 'SHIGELLA_SPP' with 'SHISPP' in the customizableenumvalue table
insert statement. Create a database migration script to update any existing
persisted records in the customizableenumvalue table that contain the old value
'SHIGELLA_SPP' to 'SHISPP' to ensure existing data can be properly deserialized
when JPA attempts to map them to the renamed enum constant.

In `@sormas-backend/src/main/resources/sql/sormas_schema.sql`:
- Around line 16305-16312: The migration logic contains an impossible condition
where both the EXISTS and NOT EXISTS checks look for the same column
'undermedication', making the condition always false and preventing the
migration from running. Fix this by changing the NOT EXISTS clause to check for
'onmedication' instead of 'undermedication', so the condition properly verifies
that the old column exists and the new column does not. Additionally, remove the
duplicate IF block that appears immediately after (the second identical IF
statement in each pair), since only one migration check is needed for each
column rename operation. Apply these fixes to both occurrences of this pattern
in the file.

In
`@sormas-ui/src/main/java/de/symeda/sormas/ui/samples/diseasesection/ShigellosisSectionComponent.java`:
- Around line 149-171: The updateFieldVisibility method clears field values in
the setVisibleClear calls before subsequently making those same fields visible
again, causing data loss. The negative condition guards (if (!isSerogrouping),
if (!isSerotype), if (!showDrugSusceptibilityForm)) cause overlapping field
clearances. Restructure the logic so that setVisibleClear only executes when the
field will definitely remain hidden, by either: (1) inverting the guard
conditions to check that the field won't be shown in the subsequent visibility
assignments, or (2) reorganizing to clear fields only when they should remain
invisible across all visibility-setting paths. Ensure specie is only cleared
when both isSerogrouping and isSerotype are false, serotypeTF is only cleared
when isSerotype is false, and serotypingMethodCBF is only cleared when both
isSerotype and showDrugSusceptibilityForm are false.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@sormas-backend/src/main/java/de/symeda/sormas/backend/therapy/DrugSusceptibilityMapper.java`:
- Around line 133-137: The hasData method in DrugSusceptibilityMapper is missing
validation for the five newly introduced *Method fields that were added to the
mapping logic. Update the hasData method to include checks for
AzithromycinMethod, AmpicillinMethod, CeftazidimeMethod, CefotaximeMethod, and
TrimethoprimSulfamethoxazoleMethod so that records containing only these method
values are not incorrectly treated as empty data. Apply the same fix to all
locations where hasData performs similar validation checks for
DrugSusceptibility fields.

In
`@sormas-ui/src/main/java/de/symeda/sormas/ui/therapy/DrugSusceptibilityForm.java`:
- Around line 96-97: Remove the empty string field-location placeholders from
all fluidRowLocsCss method calls in the DrugSusceptibilityForm class. These
empty strings ("") are being passed as arguments for zone-diameter and
surveillance fields, but they generate invalid location='' HTML attributes that
break Vaadin template binding. For each affected fluidRowLocsCss call, identify
the empty strings and either omit those parameters entirely from the argument
list or restructure the call to pass only the fields that have actual location
values, ensuring no empty strings are passed as location placeholders.