📋 UC06: Nurse Care Request

Use Case Uc06 Care Request Submitted By A Nurse

USE CASE NAME: Care Request Creation by a Nurse

PRIMARY ACTOR: Nurse registered on CareDeal

Business Objective

Allow a registered nurse to create a care request for a

patient they cannot take care of themselves (overload, different

geographic area, specific care type, etc.).

Preconditions

• The nurse has a CareDeal account of type "caregiver"
• The nurse is logged into the application
• The nurse's account is validated (status = active)
• The nurse knows the patient's information

Nurses CAN create care requests for patients.

Important Limitation

A nurse who creates a request CANNOT:

• See this request in their "available requests" interface
• Mark this request as "arranged" from their caregiver interface

The request they create is visible to OTHER nurses in the area.

Typical Use Cases

• Refer a patient to other colleagues
• Create a request for a patient they cannot take care of
• Help a patient find another caregiver

• The nurse accesses the care request creation form
• (Same form as for patients)

• They select the necessary care types:
• Bathing assistance, Wound care, Injections, etc.
• They press "Next"

• They indicate the daily frequency of care
• They press "Next"

• They enter the patient's home address
• They verify the location on the map
• They press "Next"

• They enter:
• Patient's first name and last name
• Date of birth
• Email (optional)
• Languages spoken
• They press "Next"

• They select "Professional" as contact type

(This indicates that a nurse is making the request)

• They press "Next"

• Their number (from caregiver account) is automatically used
• They can add the patient's number as a complement
• Note: Other nurses will call THEM first

• They verify all information
• They submit the request

• The request is created with them as creator
• The request is visible to other nurses in the area
• THEY do NOT see this request in their "available requests" interface

For The Creating Nurse

• The request appears in their "created" requests (if interface available)
• They can see the request status
• They can potentially cancel the request
• They CANNOT mark it as "arranged" from the caregiver interface

For Other Nurses

• The request appears in their "available requests"
• They can contact the contact person (the creating nurse)
• They can mark the request as "arranged"

Communication

• Other nurses will call the creating nurse
• The creating nurse will then coordinate with the patient
• Or they will give the patient's number directly

The CareRequestEntity entity contains:

• userUuid: NURSE's UUID (creator)
• phoneNumber: nurse's number (primary contact)
• patientPhoneNumber: patient's number (optional)
• contactPersonType: "professional"
• firstNamePatient/lastNamePatient: patient's info
• address: patient's home
• careServiceTypes: required care types
• active: true
• arrangedForPatient: null (not yet arranged)
• arrangedForCareGiver: {} (no caregiver has arranged)

1. Invisibility In Caregiver Interface

The nurse does not see their own request in "available requests".

This is expected behavior to prevent them from responding to their own request.

2. Marking As "Arranged"

The creating nurse cannot mark the request as arranged

from their caregiver interface. They can possibly do so

from another interface (to be verified).

3. Coordination

The creating nurse must coordinate with:

• The patient (to confirm the care)
• The nurse taking over (to validate the arrangement)

4. Credits/Plan

Creating a request does not consume credits.

Credits are used to CONTACT patients on existing requests.

Request creation:

• lib/modules/carerequest/presentation/controllers/care_request_submission_controller.dart
• lib/modules/carerequest/presentation/controllers/carerequest_form_controller.dart

Request entity:

• lib/modules/carerequest/domain/entities/carerequest_entity.dart

Any logged-in user can create a care request.