Last updated November 2, 2026 · Published by myLabCompliance, one of the products discussed

QC in a LIMS or LIS vs. a Dedicated QC and Compliance System

What it is: A LIMS- or LIS-integrated QC module is the quality control function built into a laboratory information management system (LIMS) or clinical laboratory information system (LIS). Because the system already receives instrument results, it can store control results next to patient results, chart them and hold or release a run based on rule checks. A dedicated QC and compliance system is separate software that manages QC records together with the other records a CLIA lab must keep, such as corrective action, competency, procedures, equipment and proficiency testing.

Neither option is right for every lab. A LIMS or LIS QC module is close to the data and can stop bad results at the point of release. A dedicated QC and compliance system is built around the evidence trail that surveyors review: who looked at the failure, what was done, which patients were checked, and whether the staff and procedures behind the run were in order. Many CLIA labs end up using both, with a written rule for which system holds which record.

Why this question comes up

Labs usually ask it at one of three moments: when they buy or replace an LIS, when a survey finds that QC corrective action is hard to trace, or when a growing group wants one view of QC across sites. In each case the real question is the same: where should QC data live, and where should the record of what the lab did about it live?

Google's overview of lab QC software lists LIMS-integrated QC modules as one of the core types, next to standalone QC systems and cloud QC platforms. This page compares the integrated option with a dedicated system that combines QC and compliance records. For the broader clinical-versus-manufacturing distinction, see our LIS vs. LIMS quality control guide. For the full map of categories, see our lab quality control software guide.

What a LIMS or LIS QC module usually does well

Automatic capture. Control results arrive from the analyzer or middleware through the same interface as patient results, so there is little manual entry.
Release control. The system can hold patient results on a run until QC passes, which directly supports the CLIA rule that controls must be acceptable before results are reported.
One login for the bench. Technologists see QC and patient work in the same place.
Instrument context. The module knows which instrument, test and run each control belongs to.

Depth varies widely. Some modules offer full Levey-Jennings charting and configurable multirules; others store pass or fail and little more. QC depth also depends on how the system was configured at go-live, which is often a large project with many priorities competing for time.

Where LIMS and LIS QC modules often leave gaps

These are patterns, not defects of any one product. Confirm each with your vendor and your own configuration.

Corrective action as a free-text comment. A rejection may be overridden with a short note, with no structured fields for root cause, patient look-back or reviewer sign-off.
No link to people. The QC record shows a user ID, but the competency file, training and qualifications for that person live in HR folders or binders.
No link to procedures. The QC procedure version in force on the day of the failure is not referenced.
Equipment history kept elsewhere. Maintenance, calibration and service records that explain a shift are often on paper or in a separate system.
Reports built for operations, not surveys. Pulling a single run with its review, corrective action and patient evaluation can take several reports and a binder.
Waived and point-of-care testing outside the LIS. Many POC and waived tests are not interfaced, so their QC lives on paper logs.

What a dedicated QC and compliance system adds

A dedicated system is organized around the evidence a lab must keep under 42 CFR Part 493, not around specimen flow. In myLabCompliance, per its public QC page and CLIA compliance page, that means:

QC scheduling, package insert limits and control lot management for tests whether or not they are interfaced, including waived and point-of-care tests.
Levey-Jennings charts with multiple levels and Westgard rule violation detection.
QC failure records with status, retry sessions, attempt sequence, level-specific corrective action, root cause and resolution notes.
Personnel files and six-element competency assessments in the same platform.
Document control with versions, review cycles and e-signatures.
Equipment maintenance, calibration and service history.
Proficiency testing enrollment, results and corrective action, plus method validation workflows.
Audit trails and dashboards for technical consultants and lab directors.

Its public pages do not describe a built-in interface to any specific LIS or LIMS. QC results are entered in myLabCompliance, or QC reports from the LIS are exported and filed. The Reference / High-Volume plan lists custom workflow automation and API integrations; scope is confirmed in a demo.

Side-by-side comparison

Need	LIMS / LIS QC module	Dedicated QC and compliance system (myLabCompliance)
Automatic QC capture from analyzers	Usually yes, through existing interfaces	Not described; manual entry or file export, API on the Reference / High-Volume plan
Hold patient results until QC passes	Often yes	No; it does not release patient results
Levey-Jennings charts and Westgard rules	Varies by product and setup	Yes
Structured QC failure investigation	Varies; often a comment field	Yes, with root cause and corrective action fields
QC for non-interfaced and waived tests	Often outside the system	Yes, through QC schedules
Competency, documents, equipment, PT, validation	Not the focus	Yes
Implementation effort	Part of a larger LIS or LIMS project	Configuration of QC materials, inserts, schedules, levels, lots and acceptance criteria during onboarding

Rows that say "varies" depend on your vendor and configuration. Test them with your own data before deciding.

Three ways labs combine them

1. LIS for capture and release, compliance system for the record. The LIS holds QC data and blocks release. When a run fails, the technologist opens a QC failure record in the compliance system with the LIS run reference, root cause, patient look-back and reviewer. Monthly LIS QC summaries are exported and filed in document control.

2. Compliance system for non-interfaced testing. Interfaced chemistry and hematology QC stay in the LIS. Waived, point-of-care and manual tests are scheduled and charted in the compliance system, which is often where these tests were weakest.

3. Compliance system as the QC record. Smaller labs, physician office labs and clinic groups without a full LIS QC module chart QC directly in the compliance platform, where schedules, charts, Westgard flags and corrective action sit together.

Whatever the pattern, write it into the QC procedure: which system is the record for QC results, for review, and for corrective action, and from which date.

What CLIA expects regardless of system

42 CFR 493.1256: control procedures for each test system, acceptability criteria for each control lot, acceptable results before reporting, and documentation of all control procedures.
42 CFR 493.1282: documented corrective action when QC fails, including evaluation of patient results back to the last acceptable run.
42 CFR 493.1251: a written procedure manual that covers control procedures and corrective action.
42 CFR 493.1235: competency assessment policies.
42 CFR 493.1105: QC records retained for at least two years.
42 CFR 493.1239: general laboratory systems quality assessment, including monitoring and correcting problems over time.

A system choice satisfies none of these on its own. What matters is whether a surveyor can follow one run from the control result to the review, the corrective action, the patient evaluation and the procedure, without the story changing between systems.

How to decide

List every test system and mark which are interfaced to the LIS and which are not.
Pull three recent QC failures and time how long it takes to assemble the full record for each.
Check whether your LIS QC module can store structured root cause and patient look-back, or only comments.
Ask who maintains LIS QC rules and limits after go-live, and how changes are documented.
Decide whether competency, procedures and equipment records should be linked to QC events.
Confirm record export and retention for at least two years in every system you keep.

If the slow part of each exercise was finding the records around the QC result, a dedicated compliance system is worth a look. If the slow part was entering QC, interface work in the LIS is the priority.

Bring three recent QC failures to a myLabCompliance demo and see how the full record would be organized.

Book a myLabCompliance demo

FAQs

What is the difference between LIMS QC and dedicated QC software?

A LIMS or LIS QC module stores control results inside the system that handles patient results and can hold release until QC passes. Dedicated QC and compliance software manages QC records together with corrective action, competency, procedures, equipment and PT records.

Is a LIMS the same as an LIS?

The terms overlap. In US clinical labs, LIS usually means the clinical laboratory information system that handles orders and results. LIMS is common in research, pharma, public health and industrial labs. Both may include a QC module.

Does myLabCompliance replace my LIS?

No. It does not handle orders or release patient results. It manages QC workflows and compliance records alongside the LIS.

Does myLabCompliance interface with my LIS?

Its public pages do not describe a built-in LIS interface. QC can be entered in myLabCompliance or LIS reports filed as documents. The Reference / High-Volume plan lists custom API integrations; ask in a demo.

Can we keep QC in the LIS and use myLabCompliance for corrective action?

Yes. Write in your QC procedure that the LIS is the record for QC results and that corrective action, root cause and patient look-back are recorded in myLabCompliance with a reference to the LIS run.

What does CLIA require after a QC failure?

42 CFR 493.1282 requires documented corrective action, including evaluating patient results from the failed run back to the last acceptable run.

Where should waived test QC be recorded?

Anywhere the lab can show it was done as required by the manufacturer and the lab's procedure. Many labs schedule waived and point-of-care QC in a compliance platform because those tests are rarely interfaced.

Sources

Related myLabCompliance pages

Unity, Unity Real Time and Unity Next are trademarks of Bio-Rad Laboratories, Inc. LabLink xL is a trademark of Thermo Fisher Scientific. InterQC is a trademark of its owner. ASTM Insight SQC is a product of ASTM International. myLabCompliance is independent software and is not affiliated with, endorsed by or integrated with any of these vendors. Vendor details come from each vendor's public pages, linked in the sources, and may change; confirm them with the vendor. This page is educational and is not legal or regulatory advice.