Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Description
Yes, the bug is related to the problem: the lack of notifications when a new prescription is described. See the detailed issue below:

Proposed Solution
To address this issue, we propose using Server-Side Events (SSE) to create an endpoint in the server that allows the client UI to subscribe and listen for notifications. This is demonstrated in the following steps, as shown in the referenced pull request:
Step 1: Create a Prescription Notification Module
The solution begins with the creation of the Prescription Notification Module, including the following key components:
See the implementation snapshots below:

Controller:
Message Constructor:

Prescription Service:

Step 2: Dispatch Notifications
Notifications are dispatched each time a prescription is triggered by modifying the iCare service implementation:

Step 3: Client-Side Notification Handling
On the UI side, we added:
notification.service.ts
): Listens for events from the server.Implementation preview:

Final Results
With mock data, the notification system functions as expected, displaying notifications in the UI:

Alternatives Considered
Backend Alternatives:
UI Alternatives:
Contributors
The following team members contributed to the solution: