[Backend] Implement Critical Condition Severity Alerts in Conditions Module

[llinsss]

⚠️ This is a backend issue — work is done inside the backend/ folder

Description

backend/src/modules/conditions/conditions.service.ts has full CRUD for pet health conditions and sorts by severity DESC, but there is no alerting when a critical condition is created or when a condition's severity is escalated. Vets and owners are not notified when a pet is diagnosed with a critical condition.

Current State

• ConditionsService — CRUD only, no notification logic
• Condition entity has a severity field (assumed enum: LOW, MEDIUM, HIGH, CRITICAL)
• NotificationsService is not injected into ConditionsModule
• No severity escalation detection on update()

What Needs to Be Built

1. Inject NotificationsService

• Add NotificationsModule to ConditionsModule imports
• Inject NotificationsService into ConditionsService

2. Alert on Critical Condition Creation

In ConditionsService.create():

if (dto.severity === ConditionSeverity.CRITICAL) {
  await this.notificationsService.create({
    userId: pet.ownerId,
    title: 'Critical Condition Diagnosed',
    body: `${pet.name} has been diagnosed with a critical condition: ${dto.name}`,
    category: NotificationCategory.ALERT,
  });
}

3. Alert on Severity Escalation

In ConditionsService.update():

• Load the existing condition before updating
• If severity changes from non-critical to CRITICAL: send alert
• If severity changes from CRITICAL to lower: send a resolution notification

4. Vet Notification

• Also notify the assigned vet (if vetId is present on the condition) for CRITICAL and HIGH severity

5. Audit Logging

• Log severity changes via AuditService with action: UPDATE and metadata containing old/new severity

Acceptance Criteria

• Creating a CRITICAL condition sends an immediate alert to the pet owner
• Escalating severity to CRITICAL sends an alert
• Resolving a CRITICAL condition sends a resolution notification
• Assigned vet is notified for CRITICAL and HIGH severity conditions
• Severity changes are recorded in the audit log
• Unit tests cover creation alert, escalation, and resolution scenarios

Files to Modify

• backend/src/modules/conditions/conditions.service.ts
• backend/src/modules/conditions/conditions.module.ts
• backend/src/modules/conditions/conditions.service.spec.ts (new)

Priority

High — critical diagnoses must trigger immediate owner notification

Estimated Effort

1–2 days

[sevencat2004]

@sevencat2004 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainer, I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sevencat2004 to this issue.

[ndii-dev]

@ndii-dev has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ndii-dev to this issue.

[drips-wave]

Congratulations, @ndii-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @ndii-dev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊