📋 Project Backlog: Lab & Clinic Management System
Priority 0: Critical (Workflow Blockers)

Must be completed first to ensure the basic process flow is correct.
1. Role-Based Dashboard Filtering

    User Story: As a Lab Staff, I want the dashboard to only show "Klinik+Lab" or "Lab Only" patients so that I can focus only on relevant tasks.

    User Story: As a CS Staff, I want to see all patients to monitor the entire facility flow.

    Technical Note: Implement a filter logic based on the patient_status or service_type field.

2. Validation State Management

    User Story: As a Lab Validator, I want the "Validate" button to disappear or disable once 2-level validation is complete to prevent redundant actions.

    User Story: As an Admin, I want an "Unvalidate" menu to revert finalized records in case of data entry errors.

3. Role-Based Print Permissions

    User Story: As a Manager, I want to restrict the "Print Result" permission to the CS Role only, so that the Lab team cannot bypass the official release process.

Priority 1: High (Efficiency & Accuracy)

Features that improve the speed and correctness of the lab operations.

4. Multilingual Result Preview

    User Story: As a Lab Staff, I want to toggle the lab result preview between Indonesian and English so that I can provide reports for international requirements.

5. Table Sorting & Search

    User Story: As a User, I want to sort the dashboard tables by "No Register" and "Patient Name" to find specific records quickly.

6. Enhanced Patient Detail Logging

    User Story: As a Staff member, I want to see a detailed history in the patient profile, including:

        Sample Collection Time (categorized by type: EDTA, Serum, etc.).

        Sample Received Time.

        Print History (Who printed the result and at what time).

7. Unvalidation Transparency

    User Story: As a User, I want the "Reason for Unvalidation" to be visible in the Patient Detail view so I know why a record was reopened.

Priority 2: Medium (UX & Technical Debt)

UI improvements and backend optimizations.
8. Visual Status Indicators (Color Coding)

    User Story: As a User, I want the "No Register" column to be color-coded (Yellow/Blue/Green) based on the legacy system logic for quick status recognition.

9. Print UI Standardization

    User Story: As a User, I want a clear "Print" button that triggers the browser/system print dialog, as standard shortcuts (Ctrl+P) are currently unreliable in the app.

10. Backend: Performance & Connectivity

    Task: Investigate the intermittent connection issues with Server 253.

    Task: Plan and execute an SSD Upgrade for the database server to resolve reported system slowness.

    Task: Verify API integration between GDC_cmod, GDC_CS2, and Report2 for the sample reception module.

Summary of Acceptance Criteria for the Junior:

    Code Consistency: All new UI elements (buttons/toggles) must match the existing design system.

    Audit Trail: Every status change (Validate/Unvalidate) must be logged with a timestamp and user ID.

    Cross-Browser: The "Print" functionality must work across Chrome and Edge browsers.