An LIS should protect the chain from request to authorized result
A laboratory information system connects the test request, patient or subject, specimen, method, work status, quality evidence, result, authorization and report. Its first responsibility is traceability: staff should be able to explain which specimen was received, what happened to it, who performed or reviewed the work and which result was released.
Qualified laboratory, clinical, quality, biosafety, legal and management professionals must approve test methods, reference intervals, critical-result rules, acceptance criteria and reporting policy. Software can enforce approved controls; it does not independently determine that a specimen, method or result is clinically valid.
Test catalogue, requests and patient identity
- Approved tests, panels, specimen types, containers, methods and performing sections
- Patient or subject identifiers and controlled duplicate resolution
- Requester, encounter, diagnosis or purpose where authorized
- Priority, collection requirements, expected turnaround and referral rules
- Prices, payer or contract links where billing is in scope
- Privacy classification and role-based visibility
Patient matching and test naming need governed identifiers. Free text should not silently replace controlled values used for clinical work or reporting.
Collection, labelling, transport and accession
The workflow can record collector, collection time, source, container, label, transport condition, receipt time and receiving user. Accession assigns a traceable laboratory identifier and routes work to the correct section. Rejection, recollection and exception reasons should remain linked to the original request.
Barcode support can reduce transcription but does not correct a wrong patient or unsuitable specimen. Collection and acceptance procedures remain professional responsibilities.
Processing, worksheets and analyzer integration
Authorized staff can organize batches, benches, worksheets, aliquots, dilutions, repeats, referrals and instrument work. Analyzer interfaces require verified mappings for test codes, units, flags, identifiers, acknowledgement, duplicates, errors and downtime. Imported output should not become a released result merely because a device transmitted it.
Quality control and nonconforming work
The system may record internal quality-control runs, lot changes, calibration, maintenance, environmental checks, external assessment and corrective actions where included. Failed control, unsuitable samples, instrument faults and other nonconformities need documented review and disposition. Qualified owners define when testing must stop or may resume.
Result review, critical notification and amendment
Results can pass through technical review and clinical or designated authorization according to the laboratory’s policy. Reference intervals, abnormal flags, comments and interpretive text require approved context. Critical-result workflows should record recipient identity, time, communication method, read-back or acknowledgement and escalation.
Corrected or amended reports must preserve the original release, reason, authorizer, date and recipients. A silent overwrite weakens patient safety and auditability.
Reports, portals, privacy and retention
Reports should identify the patient, specimen, request, laboratory, method or limitations where required, result status and authorizer. Portal, email, messaging or API delivery needs verified recipients, access controls and failure handling. Retention, disclosure and deletion rules must be approved for the applicable laboratory and jurisdiction.
Inventory, equipment, billing and finance
Reagents, kits and consumables may use lot, expiry, storage, quarantine and issue controls. Equipment records can connect maintenance, calibration and service history. Billing can connect ordered and completed services to approved prices, invoices, receipts and finance, while preserving a clear boundary between clinical authorization and financial status.
Downtime, continuity and security
A safe operating model defines how requests, labels, results and later reconciliation work when devices, networks or the application are unavailable. Access should separate registration, collection, processing, verification, authorization, billing, configuration and administration. Backups, recovery tests, protected credentials and activity history are part of the operating responsibility.
Implementation, migration and validation
Implementation begins with the laboratory scope, sections, test catalogue, identifiers, workflows, instruments, reports, roles and quality responsibilities. Migration should prioritize active patients or subjects, open requests, approved catalogue data, relevant history and balances. Validation and UAT need representative normal, abnormal, critical, rejected, repeated, amended, interfaced and downtime cases before controlled go-live.
Laboratory quality reference
The operating model was cross-checked against the World Health Organization’s Laboratory Quality Management System handbook, including sample management, process control, information management, equipment and quality responsibilities. This is a planning reference, not WHO endorsement, accreditation or certification.