1. Ticket Details

FieldDescription
Ticket IDAMM-1394
SeverityHigh
CategoryBug
Affected Module / FeatureMMU

2. Issue Description

When the doctor captures the Chief Complaint as “Fever,” they are unable to update the temperature in the Vitals section because the system prompts for a “Lung Assessment”—but this option is not visible, as it has been disabled in the mmu-ui properties.

3. Root Cause Analysis (RCA)

Technique Used: 5 Whys & Log/Trace Review

  • Primary Root Cause Identified: Validation logic did not account for the conditional disabling of the Lung Assessment field when isMMUOfflineSync is true.

  • Why it happened: The vitals section validation was dependent on the “Lung Assessment” being filled when “Fever” was selected. However, in MMU mode (where isMMUOfflineSync is true), the Lung Assessment field was disabled via the mmu-ui properties. Despite being disabled on the UI, the backend validation still required it, causing the temperature data not to save.

  • Why wasn't it caught earlier? This specific scenario with the combination of “Fever” and MMU offline sync condition was not part of test cases, and Lung Assessment dependency wasn’t revalidated after disabling the feature from UI.

4. Corrective Actions (Fixes for this instance)

ActionOwnerTarget DateStatus
Remove the required condition for lung assessment when isMMUOfflineSync is trueDevika25-04-2025Completed


5. Preventive Actions (To prevent recurrence)

ActionOwnerTarget DateStatus
Include MMU specific flows in QA regression checklistQA


6. Verification of Effectiveness

• Verified by testing the scenario with isMMUOfflineSync true in Wiprodev environment.
• Vitals (temperature) were saved successfully after applying the fix.

7. Lessons Learned

• Need to align UI configurations and backend validations.
• Critical to test MMU-specific flows during QA.
• All conditional validations must be reviewed post-feature flag changes.

8. CAPA Review & Closure

Reviewed ByDateRemarks




  • No labels