QC records need more than a result field
Quality control is one of the clearest examples of why laboratory compliance software needs laboratory-specific structure. A QC record is not only a number. It may depend on the instrument, assay, control material, lot number, package insert, expected mean, high and low limits, level, run time, operator, status, review comments, investigation notes, root cause, corrective action, and whether the result should appear on a Levey-Jennings report. myLabCompliance.io contains QC components and services that reflect that complexity, including QC package inserts, QC scheduling, instrument QC profiles, group QC profiles, Levey-Jennings reporting, corrective action, and IQCP workflows.
The public feature page describes quality control with Levey-Jennings charts and statistical analysis, QC failure investigation tracking, automated QC scheduling, control lot management, and Westgard rule violation detection. The home page also describes comprehensive QC management with automated testing schedules, result tracking, and compliance reporting. Those are product facts that matter for labs trying to replace manual logs and spreadsheet charts.
Levey-Jennings charts in context
A Levey-Jennings chart becomes more useful when it is tied to the underlying control setup. The software needs to know the control material, lot, target, upper limit, lower limit, units, level, and test result history. The QC components include support for multiple QC levels, package insert limits, target and control limit display, level selection, date range selection, CSV export, PDF-oriented report generation, and chart legends. The application also supports excluding a QC run from LJ reports while preserving the QC log row, which is important when a lab needs both transparency and accurate trend review.
For day-to-day users, the practical question is simple: can the lab see whether the control process is in control, and can reviewers document what happened when it is not? A platform that connects results, charts, investigations, and reports makes that review easier than rebuilding each chart separately.
Westgard review and investigations
Westgard rule review helps laboratories identify control results that require attention. The product materials list Westgard rule violation detection as a quality control feature. QC components also include fields and workflows for failure status, retry sessions, attempt sequence, level-specific corrective actions, root cause of QC failure, and escalation or resolution notes. Those details are important because a QC exception should not end with a red flag; the laboratory needs a record of follow-up.
myLabCompliance.io gives QA teams, technical consultants, and lab directors a place to connect the result, chart, investigation, corrective action, and review comments. The software does not remove the need for laboratory policy or professional review. It creates a consistent evidence path so the lab can show how it monitored QC and what it did when QC did not meet acceptance criteria.
Scheduling, package inserts, and control lots
QC scheduling is where many manual systems start to break down. The platform includes automated QC scheduling and control lot management, and myLabCompliance.io onboarding materials describe configuring QC materials, package inserts, schedules, frequencies, levels, lots, and acceptance criteria to match how the lab already runs QC. Inventory features also track reagents, controls, lot numbers, expiration dates, reorder alerts, and usage. These records support QC because expired or poorly documented control material can affect the credibility of the entire control program.
A good software workflow lets the laboratory attach or link package inserts, define QC levels and limits, schedule recurring QC, document results, and review trends. It also keeps related instrument and calibration information available because QC, maintenance, calibration, and service history are often reviewed together during inspections.
How QC software supports survey readiness
Inspection readiness for QC is about retrieval and clarity. A lab should be able to show what QC was required, what was run, which controls and lots were used, whether the results were acceptable, what chart or rule review showed, who reviewed the record, and what corrective action occurred when needed. myLabCompliance.io supports that story through QC scheduling, LJ charts, Westgard detection, reports, investigation tracking, document management, audit trails, Technical Consultant and Lab Director dashboards, and QA workflows.
For broader planning, pair this QC page with the CLIA compliance software page, competency assessment page, CAP inspection readiness page, COLA accreditation software page, and pricing page. QC is not isolated; it is part of the same quality system that includes personnel, documents, instruments, PT, and corrective action.
Frequently asked questions
Does myLabCompliance.io include Levey-Jennings charts?
Yes. The feature page lists Levey-Jennings charts and statistical analysis, and the codebase includes multiple Levey-Jennings chart and report components.
Does the software detect Westgard violations?
Yes. The public feature list includes Westgard rule violation detection as part of the quality control module.
Can QC failures be investigated in the software?
Yes. The feature list includes QC failure investigation tracking, and QC components include corrective action, root cause, and resolution note fields.
Can the software manage QC package insert limits?
Yes. The QC code includes package insert records, QC levels, target means, high and low limits, units, lot numbers, and expiration details.
See how myLabCompliance.io fits your lab
Use the form on this page to request a walkthrough focused on your personnel, QC, document, equipment, validation, and survey readiness workflows.
Request a walkthrough