mahdahar a94df3b5f7 **feat: migrate to v2 frontend with Alpine.js pattern**
- Introduce v2 views directory with Alpine.js-based UI components
- Add AuthV2 controller for v2 authentication flow
- Update PagesController for v2 routing
- Refactor ValueSet module with v2 dialogs and nested CRUD views
- Add organization management views (accounts, departments, disciplines, sites, workstations)
- Add specimen management views (containers, preparations)
- Add master views for tests and valuesets
- Migrate patient views to v2 pattern
- Update Routes and Exceptions config for v2 support
- Enhance CORS configuration
- Clean up legacy files (check_db.php, llms.txt, sanity.php, old views)
- Update agent workflow patterns for PHP Alpine.js
2025-12-30 14:30:35 +07:00
2025-06-26 14:09:25 +07:00
2025-06-26 15:23:16 +07:00
2025-06-26 15:23:16 +07:00
2025-09-19 16:42:27 +07:00
2025-09-19 16:42:27 +07:00
env
2025-06-26 15:23:16 +07:00
2025-06-26 15:23:16 +07:00
2025-06-26 15:23:16 +07:00
2025-06-26 15:23:16 +07:00

CLQMS (Clinical Laboratory Quality Management System)

The core backend engine for modern clinical laboratory workflows.

CLQMS is a robust, mission-critical API suite designed to streamline laboratory operations, ensure data integrity, and manage complex diagnostic workflows. Built on a foundation of precision and regulatory compliance, this system handles everything from patient registration to high-throughput test resulting.


🏛️ Core Architecture & Design

The system is currently undergoing a strategic Architectural Redesign to consolidate legacy structures into a high-performance, maintainable schema. This design, spearheaded by leadership, focuses on reducing technical debt and improving data consistency across:

  • Unified Test Definitions: Consolidating technical, calculated, and site-specific test data.
  • Reference Range Centralization: A unified engine for numeric, threshold, text, and coded results.
  • Ordered Workflow Management: Precise tracking of orders from collection to verification.

🛡️ Strategic Pillars

  • Precision & Accuracy: Strict validation for all laboratory parameters and reference ranges.
  • Scalability: Optimized for high-volume diagnostic environments.
  • Compliance: Built-in audit trails and status history for full traceability.
  • Interoperability: Modular architecture designed for LIS, HIS, and analyzer integrations.

🛠️ Technical Stack

Component Specification
Language PHP 8.1+ (PSR-compliant)
Framework CodeIgniter 4
Security JWT (JSON Web Tokens) Authorization
Database MySQL (Optimized Schema Migration in progress)

📂 Documentation & Specifications

For detailed architectural blueprints and API specifications, please refer to the internal documentation:

👉 Internal Documentation Index

Key documents:


🔌 Edge API - Instrument Integration

The Edge API provides endpoints for integrating laboratory instruments via the tiny-edge middleware. Results from instruments are staged in the edgeres table before processing into the main patient results (patres).

Endpoints

Method Endpoint Description
POST /api/edge/results Receive instrument results (stored in edgeres)
GET /api/edge/orders Fetch pending orders for an instrument
POST /api/edge/orders/:id/ack Acknowledge order delivery to instrument
POST /api/edge/status Log instrument status updates

Workflow

Instrument → tiny-edge → POST /api/edge/results → edgeres table → [Manual/Auto Processing] → patres table

Key Features:

  • Staging Table: All results land in edgeres first for validation
  • Rerun Handling: Duplicate SampleID + TestSiteCode increments AspCnt in patres
  • Configurable Processing: Auto or manual processing based on settings
  • Status Tracking: Full audit trail via edgestatus and edgeack tables

📜 Usage Notice

This repository contains proprietary information intended for the 5Panda Team and authorized collaborators.


© 2025 5Panda Team. Engineering Precision in Clinical Diagnostics.

Description
No description provided
Readme MIT 16 MiB
Languages
PHP 98.4%
HTML 0.7%
JavaScript 0.6%
CSS 0.3%