2.8 KiB

Why

The CLQMS frontend has several incomplete features marked with TODO comments that block core workflows. Additionally, the sidebar links to Specimens and Users pages that don't exist yet. Completing these TODOs and adding the missing pages will provide a fully functional laboratory management system with complete patient-to-results tracking and user administration capabilities.

What Changes

Backend TODOs (F)

  • Patient Delete: Wire up existing deletePatient() API (currently commented out)
  • Order Detail View: Create modal component to display order details, test list, and status history
  • Barcode Printing: Add print stubs and structure for patient wristbands and specimen labels
  • TestMap Delete: Document API limitation and add error handling for missing TestMapID

New Pages

  • Specimens Page (A): Full CRUD page for specimen tracking with search, list, and detail views
  • Users Page (B): User management interface with CRUD operations

Backend Requirements (Coordinate with clqms01-be)

  • Specimen Delete API: Add DELETE /api/specimen/(:num) endpoint to backend
  • User Management API: Create complete CRUD API for user management:
    • GET /api/users - List users
    • GET /api/users/(:num) - Get user details
    • POST /api/users - Create user
    • PATCH /api/users - Update user
    • DELETE /api/users/(:num) - Delete user

Minor Improvements

  • Update sidebar navigation to point to new pages
  • Add proper error handling for incomplete features

Capabilities

New Capabilities

  • specimen-management: Specimen tracking and management interface
  • user-management: User administration and role management
  • barcode-printing: Barcode generation and printing for patients and specimens
  • order-detail-view: Detailed order inspection with test breakdown

Modified Capabilities

  • patient-management: Add delete functionality to complete CRUD operations

Impact

  • Frontend: 3 new route pages, 2 new modal components, API integrations
  • Backend: New endpoints for specimen delete and user CRUD operations
  • User Experience: Completes core lab workflow from patient registration to results
  • Breaking Changes: None - additive changes only

Dependencies

Backend Changes Required (clqms01-be repo):

Feature Backend Work Status
Patient Delete Already exists Ready
Specimens ⚠️ Add DELETE endpoint BLOCKS specimen delete
Users Create full CRUD API BLOCKS users page
Order Detail Already exists Ready

Coordination Strategy:

  1. Backend team creates specimen delete endpoint
  2. Backend team creates user management API
  3. Frontend implements features as APIs become available
  4. Parallel development possible for non-dependent features