@blackcode_sa/metaestetics-api 1.12.61 → 1.12.62

package/src/services/notifications/notification.service.ts

@@ -1,215 +1,215 @@
-import {
-  collection,
-  doc,
-  getDoc,
-  getDocs,
-  query,
-  where,
-  updateDoc,
-  deleteDoc,
-  orderBy,
-  Timestamp,
-  addDoc,
-  writeBatch,
-} from "firebase/firestore";
-import { BaseService } from "../base.service";
-import {
-  Notification,
-  NotificationStatus,
-  NotificationType,
-  BaseNotification,
-  NOTIFICATIONS_COLLECTION,
-} from "../../types/notifications";
-import { UserRole } from "../../types";
-
-export class NotificationService extends BaseService {
-  /**
-   * Kreira novu notifikaciju
-   */
-  async createNotification(
-    notification: Omit<Notification, "id" | "createdAt" | "updatedAt">
-  ): Promise<Notification> {
-    const notificationsRef = collection(this.db, NOTIFICATIONS_COLLECTION);
-
-    const now = Timestamp.now();
-    const notificationData = {
-      ...notification,
-      createdAt: now,
-      updatedAt: now,
-      status: NotificationStatus.PENDING,
-      isRead: false,
-      userRole: notification.userRole || UserRole.PATIENT,
-    };
-
-    const docRef = await addDoc(notificationsRef, notificationData);
-    return {
-      ...notificationData,
-      id: docRef.id,
-    } as Notification;
-  }
-
-  /**
-   * Dohvata notifikaciju po ID-u
-   */
-  async getNotification(notificationId: string): Promise<Notification | null> {
-    const notificationRef = doc(
-      this.db,
-      NOTIFICATIONS_COLLECTION,
-      notificationId
-    );
-    const notificationDoc = await getDoc(notificationRef);
-
-    if (!notificationDoc.exists()) {
-      return null;
-    }
-
-    return {
-      id: notificationDoc.id,
-      ...notificationDoc.data(),
-    } as Notification;
-  }
-
-  /**
-   * Dohvata sve notifikacije za korisnika
-   */
-  async getUserNotifications(userId: string): Promise<Notification[]> {
-    const q = query(
-      collection(this.db, NOTIFICATIONS_COLLECTION),
-      where("userId", "==", userId),
-      orderBy("notificationTime", "desc")
-    );
-
-    const querySnapshot = await getDocs(q);
-    return querySnapshot.docs.map((doc) => ({
-      id: doc.id,
-      ...doc.data(),
-    })) as Notification[];
-  }
-
-  /**
-   * Dohvata nepročitane notifikacije za korisnika
-   */
-  async getUnreadNotifications(userId: string): Promise<Notification[]> {
-    const q = query(
-      collection(this.db, NOTIFICATIONS_COLLECTION),
-      where("userId", "==", userId),
-      where("isRead", "==", false),
-      orderBy("notificationTime", "desc")
-    );
-
-    const querySnapshot = await getDocs(q);
-    return querySnapshot.docs.map((doc) => ({
-      id: doc.id,
-      ...doc.data(),
-    })) as Notification[];
-  }
-
-  /**
-   * Označava notifikaciju kao pročitanu
-   */
-  async markAsRead(notificationId: string): Promise<void> {
-    const notificationRef = doc(
-      this.db,
-      NOTIFICATIONS_COLLECTION,
-      notificationId
-    );
-
-    await updateDoc(notificationRef, {
-      isRead: true,
-      updatedAt: Timestamp.now(),
-    });
-  }
-
-  /**
-   * Označava sve notifikacije korisnika kao pročitane
-   */
-  async markAllAsRead(userId: string): Promise<void> {
-    const notifications = await this.getUnreadNotifications(userId);
-
-    const batch = writeBatch(this.db);
-    notifications.forEach((notification) => {
-      const notificationRef = doc(
-        this.db,
-        NOTIFICATIONS_COLLECTION,
-        notification.id
-      );
-      batch.update(notificationRef, {
-        isRead: true,
-        updatedAt: Timestamp.now(),
-      });
-    });
-
-    await batch.commit();
-  }
-
-  /**
-   * Ažurira status notifikacije
-   */
-  async updateNotificationStatus(
-    notificationId: string,
-    status: NotificationStatus
-  ): Promise<void> {
-    const notificationRef = doc(
-      this.db,
-      NOTIFICATIONS_COLLECTION,
-      notificationId
-    );
-
-    await updateDoc(notificationRef, {
-      status,
-      updatedAt: Timestamp.now(),
-    });
-  }
-
-  /**
-   * Briše notifikaciju
-   */
-  async deleteNotification(notificationId: string): Promise<void> {
-    const notificationRef = doc(
-      this.db,
-      NOTIFICATIONS_COLLECTION,
-      notificationId
-    );
-    await deleteDoc(notificationRef);
-  }
-
-  /**
-   * Dohvata notifikacije po tipu
-   */
-  async getNotificationsByType(
-    userId: string,
-    type: NotificationType
-  ): Promise<Notification[]> {
-    const q = query(
-      collection(this.db, NOTIFICATIONS_COLLECTION),
-      where("userId", "==", userId),
-      where("notificationType", "==", type),
-      orderBy("notificationTime", "desc")
-    );
-
-    const querySnapshot = await getDocs(q);
-    return querySnapshot.docs.map((doc) => ({
-      id: doc.id,
-      ...doc.data(),
-    })) as Notification[];
-  }
-
-  /**
-   * Dohvata notifikacije za određeni termin
-   */
-  async getAppointmentNotifications(
-    appointmentId: string
-  ): Promise<Notification[]> {
-    const q = query(
-      collection(this.db, NOTIFICATIONS_COLLECTION),
-      where("appointmentId", "==", appointmentId),
-      orderBy("notificationTime", "desc")
-    );
-
-    const querySnapshot = await getDocs(q);
-    return querySnapshot.docs.map((doc) => ({
-      id: doc.id,
-      ...doc.data(),
-    })) as Notification[];
-  }
-}
+import {
+  collection,
+  doc,
+  getDoc,
+  getDocs,
+  query,
+  where,
+  updateDoc,
+  deleteDoc,
+  orderBy,
+  Timestamp,
+  addDoc,
+  writeBatch,
+} from "firebase/firestore";
+import { BaseService } from "../base.service";
+import {
+  Notification,
+  NotificationStatus,
+  NotificationType,
+  BaseNotification,
+  NOTIFICATIONS_COLLECTION,
+} from "../../types/notifications";
+import { UserRole } from "../../types";
+
+export class NotificationService extends BaseService {
+  /**
+   * Kreira novu notifikaciju
+   */
+  async createNotification(
+    notification: Omit<Notification, "id" | "createdAt" | "updatedAt">
+  ): Promise<Notification> {
+    const notificationsRef = collection(this.db, NOTIFICATIONS_COLLECTION);
+
+    const now = Timestamp.now();
+    const notificationData = {
+      ...notification,
+      createdAt: now,
+      updatedAt: now,
+      status: NotificationStatus.PENDING,
+      isRead: false,
+      userRole: notification.userRole || UserRole.PATIENT,
+    };
+
+    const docRef = await addDoc(notificationsRef, notificationData);
+    return {
+      ...notificationData,
+      id: docRef.id,
+    } as Notification;
+  }
+
+  /**
+   * Dohvata notifikaciju po ID-u
+   */
+  async getNotification(notificationId: string): Promise<Notification | null> {
+    const notificationRef = doc(
+      this.db,
+      NOTIFICATIONS_COLLECTION,
+      notificationId
+    );
+    const notificationDoc = await getDoc(notificationRef);
+
+    if (!notificationDoc.exists()) {
+      return null;
+    }
+
+    return {
+      id: notificationDoc.id,
+      ...notificationDoc.data(),
+    } as Notification;
+  }
+
+  /**
+   * Dohvata sve notifikacije za korisnika
+   */
+  async getUserNotifications(userId: string): Promise<Notification[]> {
+    const q = query(
+      collection(this.db, NOTIFICATIONS_COLLECTION),
+      where("userId", "==", userId),
+      orderBy("notificationTime", "desc")
+    );
+
+    const querySnapshot = await getDocs(q);
+    return querySnapshot.docs.map((doc) => ({
+      id: doc.id,
+      ...doc.data(),
+    })) as Notification[];
+  }
+
+  /**
+   * Dohvata nepročitane notifikacije za korisnika
+   */
+  async getUnreadNotifications(userId: string): Promise<Notification[]> {
+    const q = query(
+      collection(this.db, NOTIFICATIONS_COLLECTION),
+      where("userId", "==", userId),
+      where("isRead", "==", false),
+      orderBy("notificationTime", "desc")
+    );
+
+    const querySnapshot = await getDocs(q);
+    return querySnapshot.docs.map((doc) => ({
+      id: doc.id,
+      ...doc.data(),
+    })) as Notification[];
+  }
+
+  /**
+   * Označava notifikaciju kao pročitanu
+   */
+  async markAsRead(notificationId: string): Promise<void> {
+    const notificationRef = doc(
+      this.db,
+      NOTIFICATIONS_COLLECTION,
+      notificationId
+    );
+
+    await updateDoc(notificationRef, {
+      isRead: true,
+      updatedAt: Timestamp.now(),
+    });
+  }
+
+  /**
+   * Označava sve notifikacije korisnika kao pročitane
+   */
+  async markAllAsRead(userId: string): Promise<void> {
+    const notifications = await this.getUnreadNotifications(userId);
+
+    const batch = writeBatch(this.db);
+    notifications.forEach((notification) => {
+      const notificationRef = doc(
+        this.db,
+        NOTIFICATIONS_COLLECTION,
+        notification.id
+      );
+      batch.update(notificationRef, {
+        isRead: true,
+        updatedAt: Timestamp.now(),
+      });
+    });
+
+    await batch.commit();
+  }
+
+  /**
+   * Ažurira status notifikacije
+   */
+  async updateNotificationStatus(
+    notificationId: string,
+    status: NotificationStatus
+  ): Promise<void> {
+    const notificationRef = doc(
+      this.db,
+      NOTIFICATIONS_COLLECTION,
+      notificationId
+    );
+
+    await updateDoc(notificationRef, {
+      status,
+      updatedAt: Timestamp.now(),
+    });
+  }
+
+  /**
+   * Briše notifikaciju
+   */
+  async deleteNotification(notificationId: string): Promise<void> {
+    const notificationRef = doc(
+      this.db,
+      NOTIFICATIONS_COLLECTION,
+      notificationId
+    );
+    await deleteDoc(notificationRef);
+  }
+
+  /**
+   * Dohvata notifikacije po tipu
+   */
+  async getNotificationsByType(
+    userId: string,
+    type: NotificationType
+  ): Promise<Notification[]> {
+    const q = query(
+      collection(this.db, NOTIFICATIONS_COLLECTION),
+      where("userId", "==", userId),
+      where("notificationType", "==", type),
+      orderBy("notificationTime", "desc")
+    );
+
+    const querySnapshot = await getDocs(q);
+    return querySnapshot.docs.map((doc) => ({
+      id: doc.id,
+      ...doc.data(),
+    })) as Notification[];
+  }
+
+  /**
+   * Dohvata notifikacije za određeni termin
+   */
+  async getAppointmentNotifications(
+    appointmentId: string
+  ): Promise<Notification[]> {
+    const q = query(
+      collection(this.db, NOTIFICATIONS_COLLECTION),
+      where("appointmentId", "==", appointmentId),
+      orderBy("notificationTime", "desc")
+    );
+
+    const querySnapshot = await getDocs(q);
+    return querySnapshot.docs.map((doc) => ({
+      id: doc.id,
+      ...doc.data(),
+    })) as Notification[];
+  }
+}

package/src/services/patient/README.md

@@ -1,48 +1,48 @@
-# Patient Service
-
-This service provides a comprehensive API for managing patient-related data within the application. It handles the creation, retrieval, and updating of patient profiles, as well as their sensitive, medical, and location-based information.
-
-## Core Responsibilities
-
-- **Patient Profile Management**: Creating standard (user-linked) and manual (offline) patient profiles.
-- **Data Segregation**: Manages different aspects of patient data in separate sub-collections for enhanced security and privacy:
-  - `sensitive-info`: Personal Identifiable Information (PII) like name, DOB, and contact details.
-  - `medical-info`: Health-related data including allergies, conditions, and medications.
-  - `location-info`: Geolocation data for search and mapping features.
-- **Security**: Enforces role-based access control, ensuring that only authorized users (patients, practitioners, clinic admins) can access or modify patient data.
-
-## Key Methods
-
-### `createPatientProfile(data: CreatePatientProfileData)`
-
-- Creates a standard patient profile linked to an existing, authenticated user account via `userRef`.
-- This is the standard flow for patients registering through the application.
-
-### `createManualPatient(data: CreateManualPatientData, requester: RequesterInfo)`
-
-- Allows a `clinic_admin` to create a patient profile that is **not** linked to a user account.
-- This is designed for managing "offline" patients within the clinic's ecosystem.
-- The `isManual` flag is set to `true` on the profile.
-- The patient is automatically associated with the admin's clinic.
-
-### `getPatientProfile(patientId: string)`
-
-- Retrieves the public-facing profile of a patient.
-
-### `getSensitiveInfo(patientId: string, requesterUserId: string)`
-
-- Retrieves the sensitive PII of a patient. Access is restricted and requires proper authorization.
-
-### `getMedicalInfo(patientId:string)`
-
-- Retrieves the medical information for a patient. Access is strictly controlled based on the requester's permissions.
-
-## Data Models
-
-The main data models used by this service are:
-
-- `PatientProfile`: The core, top-level patient document.
-- `PatientSensitiveInfo`: Sub-collection for private, personal data.
-- `PatientMedicalInfo`: Sub-collection for health records.
-
-For detailed information on the data structures, see `Api/src/types/patient/index.ts`.
+# Patient Service
+
+This service provides a comprehensive API for managing patient-related data within the application. It handles the creation, retrieval, and updating of patient profiles, as well as their sensitive, medical, and location-based information.
+
+## Core Responsibilities
+
+- **Patient Profile Management**: Creating standard (user-linked) and manual (offline) patient profiles.
+- **Data Segregation**: Manages different aspects of patient data in separate sub-collections for enhanced security and privacy:
+  - `sensitive-info`: Personal Identifiable Information (PII) like name, DOB, and contact details.
+  - `medical-info`: Health-related data including allergies, conditions, and medications.
+  - `location-info`: Geolocation data for search and mapping features.
+- **Security**: Enforces role-based access control, ensuring that only authorized users (patients, practitioners, clinic admins) can access or modify patient data.
+
+## Key Methods
+
+### `createPatientProfile(data: CreatePatientProfileData)`
+
+- Creates a standard patient profile linked to an existing, authenticated user account via `userRef`.
+- This is the standard flow for patients registering through the application.
+
+### `createManualPatient(data: CreateManualPatientData, requester: RequesterInfo)`
+
+- Allows a `clinic_admin` to create a patient profile that is **not** linked to a user account.
+- This is designed for managing "offline" patients within the clinic's ecosystem.
+- The `isManual` flag is set to `true` on the profile.
+- The patient is automatically associated with the admin's clinic.
+
+### `getPatientProfile(patientId: string)`
+
+- Retrieves the public-facing profile of a patient.
+
+### `getSensitiveInfo(patientId: string, requesterUserId: string)`
+
+- Retrieves the sensitive PII of a patient. Access is restricted and requires proper authorization.
+
+### `getMedicalInfo(patientId:string)`
+
+- Retrieves the medical information for a patient. Access is strictly controlled based on the requester's permissions.
+
+## Data Models
+
+The main data models used by this service are:
+
+- `PatientProfile`: The core, top-level patient document.
+- `PatientSensitiveInfo`: Sub-collection for private, personal data.
+- `PatientMedicalInfo`: Sub-collection for health records.
+
+For detailed information on the data structures, see `Api/src/types/patient/index.ts`.

package/src/services/patient/To-Do.md

@@ -1,43 +1,43 @@
-# To-Do: Manual Patient Creation
-
-This document outlines the steps required to implement the manual creation of patient profiles by clinic admins. This allows clinics to manage patients who do not yet have an account in the patient application.
-
-## Phase 1: Core Implementation (No User Link)
-
-### 1. Update Data Models and Types (`types/patient/index.ts`)
-
-- [ ] Modify `PatientProfile` to make `userRef` optional.
-- [ ] Modify `CreatePatientProfileData` to make `userRef` optional.
-- [ ] Add a new field `isManual: boolean` to `PatientProfile` and `CreatePatientProfileData` to flag patients created without a user account.
-- [ ] Modify `PatientSensitiveInfo` to make `userRef` optional.
-- [ ] Modify `CreatePatientSensitiveInfoData` to make `userRef` optional.
-- [ ] Create a new type `CreateManualPatientData` that combines necessary fields from `CreatePatientProfileData` and `CreatePatientSensitiveInfoData`, but tailored for manual creation (e.g., requires `firstName`, `lastName`, `clinicId`).
-
-### 2. Update Validation Schemas (`validations/patient.schema.ts`)
-
-- [ ] Update `patientProfileSchema` to reflect that `userRef` is optional.
-- [ ] Update `createPatientProfileSchema` to make `userRef` optional and include `isManual`.
-- [ ] Update `patientSensitiveInfoSchema` to reflect that `userRef` is optional.
-- [ ] Update `createPatientSensitiveInfoSchema` to make `userRef` optional.
-- [ ] Create a new schema `createManualPatientSchema` to validate the input for the new service method.
-
-### 3. Implement New Service Method (`services/patient/patient.service.ts`)
-
-- [ ] Create a new public method: `createManualPatient(data: CreateManualPatientData, requester: RequesterInfo): Promise<PatientProfile>`.
-- [ ] The method should perform security checks to ensure the requester is a `clinic_admin`.
-- [ ] Inside the method:
-  - Generate a new `patientId`.
-  - Create a `PatientProfile` object with `isManual: true`, no `userRef`, and link it to the admin's clinic (`requester.associatedClinicId`).
-  - Create a `PatientSensitiveInfo` object with the provided patient details.
-  - Use a Firestore batch write to create both documents atomically.
-  - Return the newly created `PatientProfile`.
-
-### 4. Documentation & README
-
-- [ ] Update the `Api/docs/guides/patient-management.md` to document the new manual creation flow.
-- [ ] Create a `README.md` file in `Api/src/services/patient/` explaining the purpose of the service and its key methods, including `createManualPatient`.
-
-## Phase 2: Future Enhancements (Post-MVP)
-
-- [ ] **Claim/Merge Profile:** Implement logic for a patient to claim a manually created profile when they register for the app. This could involve an invitation flow or matching based on personal details.
-- [ ] **UI Implementation:** Develop the UI components in the Backoffice/Clinic app for clinic admins to use this new functionality.
+# To-Do: Manual Patient Creation
+
+This document outlines the steps required to implement the manual creation of patient profiles by clinic admins. This allows clinics to manage patients who do not yet have an account in the patient application.
+
+## Phase 1: Core Implementation (No User Link)
+
+### 1. Update Data Models and Types (`types/patient/index.ts`)
+
+- [ ] Modify `PatientProfile` to make `userRef` optional.
+- [ ] Modify `CreatePatientProfileData` to make `userRef` optional.
+- [ ] Add a new field `isManual: boolean` to `PatientProfile` and `CreatePatientProfileData` to flag patients created without a user account.
+- [ ] Modify `PatientSensitiveInfo` to make `userRef` optional.
+- [ ] Modify `CreatePatientSensitiveInfoData` to make `userRef` optional.
+- [ ] Create a new type `CreateManualPatientData` that combines necessary fields from `CreatePatientProfileData` and `CreatePatientSensitiveInfoData`, but tailored for manual creation (e.g., requires `firstName`, `lastName`, `clinicId`).
+
+### 2. Update Validation Schemas (`validations/patient.schema.ts`)
+
+- [ ] Update `patientProfileSchema` to reflect that `userRef` is optional.
+- [ ] Update `createPatientProfileSchema` to make `userRef` optional and include `isManual`.
+- [ ] Update `patientSensitiveInfoSchema` to reflect that `userRef` is optional.
+- [ ] Update `createPatientSensitiveInfoSchema` to make `userRef` optional.
+- [ ] Create a new schema `createManualPatientSchema` to validate the input for the new service method.
+
+### 3. Implement New Service Method (`services/patient/patient.service.ts`)
+
+- [ ] Create a new public method: `createManualPatient(data: CreateManualPatientData, requester: RequesterInfo): Promise<PatientProfile>`.
+- [ ] The method should perform security checks to ensure the requester is a `clinic_admin`.
+- [ ] Inside the method:
+  - Generate a new `patientId`.
+  - Create a `PatientProfile` object with `isManual: true`, no `userRef`, and link it to the admin's clinic (`requester.associatedClinicId`).
+  - Create a `PatientSensitiveInfo` object with the provided patient details.
+  - Use a Firestore batch write to create both documents atomically.
+  - Return the newly created `PatientProfile`.
+
+### 4. Documentation & README
+
+- [ ] Update the `Api/docs/guides/patient-management.md` to document the new manual creation flow.
+- [ ] Create a `README.md` file in `Api/src/services/patient/` explaining the purpose of the service and its key methods, including `createManualPatient`.
+
+## Phase 2: Future Enhancements (Post-MVP)
+
+- [ ] **Claim/Merge Profile:** Implement logic for a patient to claim a manually created profile when they register for the app. This could involve an invitation flow or matching based on personal details.
+- [ ] **UI Implementation:** Develop the UI components in the Backoffice/Clinic app for clinic admins to use this new functionality.