222
edits
Mikrosha2000 (talk | contribs) (→QC Specifications: Added LabQC Pro documentation images and completed module documentation.) |
Mikrosha2000 (talk | contribs) (Updated LabQC Pro documentation to version 1.0.43, including CAPA & Deviation Manager integration, BatchSafe workflow, audit trail, reports and current requirements.) |
||
| Line 3: | Line 3: | ||
=LabQC Pro= | =LabQC Pro= | ||
'''LabQC Pro''' is a laboratory quality control module for Dolibarr | '''LabQC Pro''' is a laboratory quality control module for Dolibarr. | ||
It provides a structured workflow from product-specific QC specifications and analytical testing to automatic PASS / FAIL evaluation, final approval, result locking, audit trail, Certificate of Analysis generation and OOS / deviation follow-up. | |||
LabQC Pro is designed for organizations that manage products by batch or lot and require documented quality-control decisions inside Dolibarr. | |||
The module can operate independently or integrate with '''BatchSafe Pro''' and '''CAPA & Deviation Manager'''. | |||
== | ==Overview== | ||
LabQC Pro | LabQC Pro adds a complete laboratory quality-control workflow to Dolibarr. | ||
Typical workflow: | |||
'''QC Specification → QC Test → Analytical Results → Automatic PASS / FAIL → Finalization & Locking → CoA | '''QC Specification → QC Test → Analytical Results → Automatic PASS / FAIL → Finalization & Locking → CoA / OOS Report → Optional CAPA / Deviation''' | ||
Main capabilities include: | |||
*Product-specific QC specifications | *Product-specific QC specifications | ||
*Specification version management | *Specification version management | ||
*Analytical parameters and acceptance criteria | *Analytical parameters and acceptance criteria | ||
*Numeric and text-based | *Numeric and text-based analytical results | ||
*Mandatory | *Mandatory QC parameters | ||
*QC tests linked to | *QC tests linked to real Dolibarr batches / lots | ||
*Automatic PASS / FAIL evaluation | *Automatic PASS / FAIL evaluation | ||
*Finalization and permanent result locking | *Finalization and permanent result locking | ||
* | *Role-based laboratory workflow | ||
*Immutable Audit Trail | *Immutable Audit Trail | ||
*Previous and new value tracking | *Previous and new value tracking | ||
*Certificate of Analysis generation | |||
*Certificate of Analysis generation | *OOS / QC Test Report generation | ||
*OOS / QC Test Report generation | *BatchSafe Pro synchronization | ||
* | *CAPA & Deviation Manager integration | ||
* | |||
*Responsive desktop and mobile interface | *Responsive desktop and mobile interface | ||
*English and Romanian interface | *English and Romanian interface | ||
==QC Specifications== | ==QC Specifications== | ||
QC Specifications define the quality requirements that a product must meet. | |||
A specification can contain: | |||
*Product | *Product | ||
* | *Specification reference | ||
* | *Specification version | ||
*Analytical parameters | *Analytical parameters | ||
*Test method | |||
*Acceptance criteria | |||
*Units | |||
* | *Mandatory / optional parameter status | ||
* | |||
* | |||
*Mandatory status | |||
Example: | Example: | ||
| Line 106: | Line 59: | ||
!Parameter | !Parameter | ||
!Method | !Method | ||
!Acceptance | !Acceptance criteria | ||
!Mandatory | !Mandatory | ||
|- | |- | ||
|Assay | |Assay | ||
|HPLC | |HPLC | ||
| | |98–102 % | ||
|Yes | |Yes | ||
|- | |- | ||
| Line 120: | Line 73: | ||
|} | |} | ||
Specifications can be versioned so that the quality requirements used for a QC test remain identifiable and traceable. | |||
==QC Tests== | |||
A QC Test links laboratory analysis to a specific product and batch / lot. | |||
Typical QC Test information includes: | |||
* | *QC test reference | ||
* | *Product | ||
* | *Batch / lot | ||
* | *QC specification | ||
*Specification version | |||
*Test status | |||
*Analytical results | *Analytical results | ||
*Analyst | |||
*Approval / finalization information | |||
A QC test can contain multiple analytical parameters taken from the selected QC specification. | |||
==Analytical results== | |||
Analytical results can be entered for each QC parameter. | |||
Depending on the parameter configuration, LabQC Pro can support: | |||
The | *Numeric results | ||
*Text-based results | |||
*Acceptance limits | |||
*Required parameters | |||
*Individual PASS / FAIL evaluation | |||
The result screen clearly displays the measured value, acceptance criteria and parameter verdict. | |||
==Automatic PASS / FAIL evaluation== | ==Automatic PASS / FAIL evaluation== | ||
LabQC Pro evaluates | LabQC Pro automatically evaluates QC results against the configured specification. | ||
Typical behavior: | |||
*All mandatory parameters within specification → '''PASS''' | |||
*One or more mandatory parameters outside specification → '''FAIL / OOS''' | |||
*Missing mandatory results → test cannot be considered complete | |||
Automatic evaluation reduces manual verdict entry and helps keep laboratory decisions consistent with the active specification. | |||
==Finalization and locking== | |||
QC results remain editable while the test is open. | |||
After | After review, an authorized QC Manager can finalize the test. | ||
Finalization: | Finalization: | ||
*Records the final QC verdict | |||
*Records the approving user | *Records the approving user | ||
*Records the | *Records the finalization date and time | ||
* | *Locks the analytical results | ||
* | *Prevents silent modification of finalized data | ||
* | *Enables final quality reporting | ||
A finalized QC test becomes a permanent quality-control record. | |||
==Suggested user roles== | |||
===Laboratory Analyst=== | |||
Typical permissions and responsibilities: | |||
*Create QC tests | |||
*Select product and batch / lot | |||
*Enter analytical results | |||
*Review parameter evaluation | |||
*Trigger automatic PASS / FAIL evaluation | |||
===QC Manager=== | |||
Typical permissions and responsibilities: | |||
*Review completed analytical results | |||
*Review PASS / FAIL evaluation | |||
*Finalize and lock QC tests | |||
*Approve final quality decisions | |||
*Review Audit Trail | |||
*Generate CoA and OOS reports | |||
*Initiate CAPA / deviation follow-up when required | |||
The exact Dolibarr permissions can be configured according to the organization's internal procedures. | |||
==Certificate of Analysis== | ==Certificate of Analysis== | ||
Finalized PASS tests can generate a '''Certificate of Analysis (CoA)'''. | |||
The | The report can include: | ||
*Product | *Product | ||
*Batch / | *Batch / lot | ||
*QC specification | *QC specification | ||
* | *Specification version | ||
*Analytical parameters | *Analytical parameters | ||
*Results | *Results | ||
* | *Acceptance criteria | ||
*Individual verdicts | |||
*Overall PASS verdict | |||
*Tested by | *Tested by | ||
*Approved by | *Approved by | ||
*Approval date | *Approval date | ||
The CoA provides a structured summary of the finalized laboratory decision. | |||
==OOS / QC Test Report== | ==OOS / QC Test Report== | ||
Finalized FAIL tests can generate an '''OOS / QC Test Report'''. | |||
The report | The report can include: | ||
* | *Product | ||
* | *Batch / lot | ||
* | *QC specification | ||
* | *Analytical results | ||
* | *Failed parameters | ||
* | *Acceptance criteria | ||
* | *Final FAIL / OOS verdict | ||
* | *Analyst and approval information | ||
The report can be used as the starting point for further investigation or deviation management. | |||
==Audit Trail== | ==Audit Trail== | ||
LabQC Pro | LabQC Pro records important quality-control events. | ||
Audit Trail entries can include: | |||
*User | |||
*Date and time | *Date and time | ||
*Object | *Object | ||
* | *Event / action | ||
*Previous value | *Previous value | ||
*New value | *New value | ||
*Note | *Note | ||
Typical recorded events include: | |||
*QC test creation | |||
*Result entry or modification | |||
*Status changes | |||
*PASS / FAIL evaluation | |||
*Finalization | |||
This provides traceability of important laboratory actions and supports internal review and audit activities. | |||
==BatchSafe Pro integration== | ==BatchSafe Pro integration== | ||
When '''BatchSafe Pro''' is installed and enabled, LabQC Pro can synchronize QC decisions with lot operational status. | |||
When BatchSafe Pro is installed and enabled, LabQC Pro can | |||
Typical workflow: | Typical workflow: | ||
| Line 252: | Line 232: | ||
{| class="wikitable" | {| class="wikitable" | ||
!LabQC event | !LabQC event | ||
!BatchSafe | !BatchSafe status | ||
|- | |- | ||
|QC test opened | |New QC test opened | ||
|Under inspection | |Under inspection | ||
|- | |- | ||
| Line 267: | Line 244: | ||
|} | |} | ||
LabQC Pro | This allows laboratory quality decisions to influence warehouse lot availability automatically. | ||
Existing manual critical holds can be preserved instead of being silently overwritten by automatic synchronization. | |||
For example, if a lot is already manually Rejected or Recalled for another critical reason, LabQC Pro can preserve that status and display an informational message rather than replacing it. | |||
BatchSafe Pro integration is optional. | |||
LabQC Pro continues to work independently when BatchSafe Pro is not installed or disabled. | |||
==CAPA & Deviation Manager integration== | |||
Starting with LabQC Pro 1.0.43, finalized FAIL / OOS tests can be integrated with '''CAPA & Deviation Manager'''. | |||
A linked deviation can be created directly from the QC test. | |||
Typical workflow: | |||
'''QC Test → FAIL / OOS → Finalization → Create CAPA / Deviation → Investigation → Corrective / Preventive Action''' | |||
The deviation form can be prefilled with information from the originating laboratory test, including: | |||
*Source module | |||
*QC test reference | |||
*Product | |||
*Batch / lot | |||
*QC specification | |||
*Severity | |||
*Department | |||
*Relevant QC context | |||
Example source reference: | |||
'''LabQC Pro · QCT-YYYYMMDD-HHMMSS''' | |||
This reduces duplicate data entry and keeps the deviation linked to the original laboratory result. | |||
After a deviation has been created, LabQC Pro can recognize the existing linked record and provide an '''Open CAPA Deviation''' action instead of creating unnecessary duplicates. | |||
The deviation description remains readable and editable when opened or modified. | |||
CAPA & Deviation Manager integration is optional. | |||
LabQC Pro continues to work independently when CAPA & Deviation Manager is not installed. | |||
==Product and lot traceability== | |||
QC tests can be linked to real Dolibarr products and lot / serial records. | |||
This helps maintain traceability between: | |||
*Product | |||
*Batch / lot | |||
*QC specification | |||
*Analytical results | |||
*Final QC verdict | |||
*BatchSafe status | |||
*CAPA / deviation record when applicable | |||
==Mobile support== | |||
LabQC Pro includes a responsive interface suitable for desktop, tablet and smartphone use. | |||
The mobile interface supports: | |||
*QC test review | |||
*Analytical result entry | |||
*PASS / FAIL visibility | |||
*Finalization information | |||
*Audit Trail access | |||
*BatchSafe status display | |||
*CAPA / deviation actions | |||
*Responsive tables and result cards | |||
==Installation== | ==Installation== | ||
#Download the LabQC Pro | #Download the LabQC Pro module package. | ||
# | #Go to '''Home → Setup → Modules/Applications''' in Dolibarr. | ||
#Use the external module deployment function. | #Use the external module deployment / installation function. | ||
#Upload the LabQC Pro ZIP package. | #Upload the LabQC Pro ZIP package. | ||
# | #Enable '''LabQC Pro'''. | ||
#Configure user permissions. | #Configure user permissions. | ||
# | #Make sure Products, Stock and Lot / Serial management are enabled when batch-based QC is required. | ||
==Basic configuration== | ==Basic configuration== | ||
After activation: | |||
#Create or select a | #Create or select a product. | ||
# | #Make sure the product uses lot / serial management when required. | ||
#Create a QC Specification for the product. | #Create a QC Specification for the product. | ||
#Add analytical parameters. | #Add analytical parameters and acceptance criteria. | ||
#Create a QC Test and | #Create a QC Test linked to a product and batch / lot. | ||
#Enter analytical results. | |||
#Review automatic PASS / FAIL evaluation. | |||
#Finalize the QC Test using an authorized QC Manager account. | |||
#Generate the appropriate CoA or OOS report. | |||
Optional integrations can then be enabled by installing BatchSafe Pro and / or CAPA & Deviation Manager. | |||
==Requirements== | |||
*Dolibarr V18 to V23 | |||
*PHP 7.4 or later | |||
*Products module | |||
*Stock / warehouse management | |||
*Lot / Serial management for batch-based QC workflows | |||
Optional: | |||
*'''BatchSafe Pro''' for lot-status synchronization | |||
*'''CAPA & Deviation Manager''' for deviation and CAPA follow-up | |||
==Version== | |||
== | Current documented version: | ||
'''LabQC Pro 1.0.43''' | |||
==Languages== | |||
LabQC Pro includes: | |||
*English | |||
*Romanian | |||
Additional translations can be added using the standard Dolibarr translation mechanism. | |||
==Typical use cases== | |||
LabQC Pro can be used in organizations such as: | |||
*Laboratories | |||
*Pharmaceutical companies | |||
*Food and supplement manufacturers | |||
*Chemical manufacturers | |||
*Manufacturing companies | |||
*Quality-controlled warehouses | |||
*Organizations using batch / lot-based product quality control | |||
==Documentation workflow example== | |||
A typical integrated workflow may look like: | |||
'''Product / Lot''' | |||
↓ | |||
'''QC Specification''' | |||
↓ | |||
'''QC Test''' | |||
↓ | |||
'''Analytical Results''' | |||
↓ | |||
'''Automatic PASS / FAIL''' | |||
↓ | |||
'''QC Manager Finalization''' | |||
↓ | |||
'''PASS → CoA → BatchSafe Released''' | |||
or | |||
'''FAIL / OOS → OOS Report → BatchSafe Rejected → CAPA / Deviation''' | |||
==Support== | ==Support== | ||
Support and product information: | |||
'''support@panciucsoft.com''' | |||
''' | LabQC Pro is developed by '''PanciucSoft'''. | ||
==License== | ==License== | ||
LabQC Pro is distributed under the '''GNU | LabQC Pro is distributed under the '''GNU GPL v3 or later''' license. | ||
==Regulatory notice== | ==Regulatory notice== | ||
LabQC Pro provides software | LabQC Pro provides software tools for laboratory quality-control workflows. | ||
The module does not replace an organization's quality management system, standard operating procedures, validation activities, qualification activities or legally required controls. | |||
Validation, qualification and compliance with GMP, GLP, GxP, ISO or other regulatory requirements remain the responsibility of the organization using the module. | |||
edits