Custom Software for Diagnostic Labs: Connecting Competency, QC, Maintenance, and Reagent Records

CMS's latest list of the deficiencies it cites most often in clinical labs reads a lot like an inventory of lab spreadsheets.

CMS publishes a list of the deficiencies its surveyors cite most often in clinical labs. Read the latest list, which covers 2024, and storage and testing conditions, staff competency, expired supplies, and instrument maintenance all make the top ten (CMS). For anyone weighing custom software for diagnostic labs, that list is the right place to start.

None of those findings are about bad science. They are about records that live in separate files, owned by different people, with nothing connecting them. A competency review needs QC and maintenance evidence. A reagent change can trigger calibration verification. A freezer excursion calls into question every reagent inside it. When each record sits in its own workbook, those links depend on someone remembering them.

Custom software for diagnostic labs is one way to fix that, but it is not always the right one. Some records are fine in a spreadsheet, and some are better served by a ready-made tool. This guide helps you sort out which is which.

In this article, we will explore:

  • Which compliance records CMS and CAP inspectors cite most often, and why they cluster together.
  • How competency, QC, maintenance, reagent, and storage records depend on each other under CLIA and ISO 15189:2022.
  • What each record needs from software, and where spreadsheets tend to break.
  • When to keep a record in a spreadsheet, buy a ready-made tool, or build custom software.
  • What custom lab compliance software should connect to, and how NonStop approaches the build.

The CLIA Deficiencies That Point Straight at Lab Compliance Records

Here are four entries from the CMS top ten standard-level deficiencies for 2024, the most recent list CMS has published, with the share of labs cited for each:

  • 5.0%Defining and monitoring storage and test operating conditions (D5413), ranked first
  • 4.8%Assessing employee and consultant competency (D5209), ranked second
  • 3.7%Using expired or deteriorated reagents and supplies (D5417)
  • 2.8%Performing maintenance at the manufacturer's frequency (D5429)

CAP's summary of its 2025 top ten deficiencies, revised in March 2026, tells a similar story from the accreditation side. It includes:

  • Maintenance and function checks (COM.30600)
  • Competency assessment elements for nonwaived testing (GEN.55500)
  • Instrument and equipment record review (COM.04200)
  • Correction of laboratory records (GEN.20450)
  • Reagent labeling (COM.30300)
  • Temperature checks (COM.30750)

Look closely and a pattern shows up. Many of these items concern documentation and review as much as the work itself.

A task done but not recorded, recorded in the wrong place, or recorded without the review that should follow.

How Lab Compliance Records Feed Each Other Under CLIA

Most labs treat these records as separate chores. The regulations treat them as a chain. A change in one record often creates an obligation in another:

Complete reagent change
  • Reagent lot change
  • Calibration verification
Major maintenance
  • Critical part replaced
  • Calibration verification
QC trend or shift
  • Corrective action fails
  • Calibration verification
Competency review
  • QC records
  • PT results
  • Maintenance records
Storage excursion
  • Temperature out of range
  • Every reagent and specimen in that unit
  • A complete reagent change triggers calibration verification, unless the lab can show that lot changes do not affect the reportable range or control values (42 CFR 493.1255(b)(3)).
  • Major preventive maintenance or a critical part replacement also triggers calibration verification.
  • Control results that trend or shift trigger calibration verification when other corrective action does not resolve them.
  • Competency assessment has to review QC records, proficiency testing results, and preventive maintenance records, and observe instrument maintenance and function checks (42 CFR 493.1451(b)(8)).
  • A new test method or instrument means staff must be reassessed before they report patient results on it (42 CFR 493.1451(b)(9)).
  • A storage temperature excursion raises questions about every reagent and specimen stored in that unit (42 CFR 493.1252(b)).

Each link is easy to follow when one person holds all the records in their head. It becomes fragile once a lab has several benches, shifts or sites.

Lab Compliance Records, File by File

Here is what each record needs, where it usually lives today, and what software should do with it. Use each file to judge whether the record is a candidate for custom software for your diagnostic lab.

Competency Assessment Records for Clinical Lab Staff

Record fileCompetency
What CLIA asks
Written policies to assess staff competency (42 CFR 493.1235). Six procedures for testing personnel, including direct observation, monitoring of result recording, review of QC, PT, and maintenance records, observation of maintenance, assessment of test performance, and problem solving. Twice in the first year of patient testing, then at least annually, per the CMS competency brochure revised in May 2025 (CMS).
What it covers
Each test the person performs. CMS says all six procedures apply to every test, even when several tests share one platform.
Who signs
The technical consultant for moderate complexity testing, or the technical supervisor for high complexity testing, who may delegate in writing to a qualified general supervisor. CLIA personnel qualifications changed in a CMS rule that took full effect on December 28, 2024, so confirm who on your team qualifies today (ASCP).
ISO 15189:2022
Clause 6.2.2 on personnel competence and clause 6.2.5 on personnel records (ISO).
Where it breaks
Due dates tracked per person, not per person and test system. Element three evidence sits in QC and maintenance files someone has to dig out. Reassessment after a method change gets missed.
What software should do
Schedule assessments by person and test system, pull QC, PT, and maintenance evidence into the review, record the assessor and their qualification, and flag anyone due for reassessment after a method or instrument change.

Competency files are also personal data about your staff. For UK and EU labs, that means GDPR security duties apply, including confidentiality, integrity, and regular testing of security measures (GDPR Article 32).

Electronic QC Records for Clinical Labs

Record fileQuality control
What CLIA asks
At least two control levels each day of testing for quantitative procedures, and a positive and negative control for qualitative ones. Control results must meet criteria before patient results go out, and all control procedures must be documented (42 CFR 493.1256).
ISO 15189:2022
Clause 7.3.7.2 on internal quality control.
Where it breaks
Values copied by hand from instruments. Review and corrective action recorded somewhere other than the result itself. No easy way to show an assessor which QC a person reviewed.
What software should do
Capture results from instruments or middleware, hold review and corrective action against the run, and make that history available to competency reviews and calibration decisions.

Instrument Maintenance Log and Function Check Records

Record fileMaintenance
What CLIA asks
Maintenance and function checks as defined by the manufacturer, at least as often as the manufacturer specifies, with function checks inside limits before patient testing. For modified or in-house equipment, the lab writes and follows its own protocol (42 CFR 493.1254).
ISO 15189:2022
Clause 6.4 on equipment, and the equipment calibration and metrological traceability requirements that follow it.
Where it breaks
Paper logs on the instrument, scanned later. Monthly record review signed without anyone checking gaps. No link between a major repair and the calibration verification it should trigger.
What software should do
Schedule tasks based on the manufacturer's frequency, record who did them and the results, flag an instrument whose function checks failed, and open a calibration verification task after major maintenance.

Reagent Lot Tracking and Calibration Verification Records

Record fileReagents
What CLIA asks
Reagents labeled with identity, storage needs, and preparation and expiration dates. Nothing used past expiration. Kit components from different lots not interchanged unless the manufacturer allows it (42 CFR 493.1252).
ISO 15189:2022
Clause 6.6 on reagents and consumables, including acceptance testing, inventory management, and records.
Where it breaks
Expiry tracked on a shared sheet that nobody checks at the bench. Lot acceptance results kept apart from the runs that used the lot. Finding every result run on a bad lot takes days.
What software should do
Record lots at receipt, hold them until acceptance testing passes, warn at the point of use when a lot is expired, link each lot to the runs and results that used it, and open calibration verification when a complete reagent change requires it.

Lab Temperature Monitoring Records for Storage and Testing Conditions

Record fileStorage and environment
What CLIA asks
Defined criteria for storing reagents and specimens and for running test systems, monitored and documented where applicable, including temperature, humidity, water quality, and protection from power fluctuations (42 CFR 493.1252(b)).
ISO 15189:2022
Clause 6.3 on facilities and environmental conditions, including storage facilities.
Where it breaks
Readings logged once a day by hand, so an overnight excursion goes unseen. Corrective action written on the log sheet, not linked to the reagents and specimens affected.
What software should do
Take readings from sensors or structured manual entry, alert on excursions, require a corrective action entry, and list the lots and specimens stored in the affected unit.
Retention

Under CLIA, records of these analytic systems activities, including QC, maintenance, calibration, and reagent records, must be kept for at least two years (42 CFR 493.1105). Whatever replaces the spreadsheet has to keep that history retrievable.

Keep It in Excel, Buy a Tool, or Build Custom Software for Your Diagnostic Lab?

There is no single right answer for every record. Here is a simple way to decide, one record at a time.

Option 1

Keep it in a spreadsheet

  • One site and a small test menu
  • One clear owner, with a second person reviewing on a schedule
  • No need to link the record to other systems
  • Locked templates, version history, and controlled access already in place
Option 2

Buy a ready-made tool

  • The record works on its own, such as staff competency
  • Your process matches what the tool expects
  • The tool supports your accreditation body's terms
  • Your data can be exported in full if you leave
Option 3

Build custom software

  • Records must connect to your LIMS, middleware, or instruments
  • Several sites or benches need one shared view
  • Your test menu or workflow is unusual, as in many genomics labs
  • You want to own the code, data, and roadmap

Many labs end up with a mix. A purchased competency tool might handle the assessment workflow, while a small piece of custom software feeds it QC and maintenance evidence from the LIMS and middleware.

That hybrid can be the most economical way to close the gaps inspectors actually cite.

What Custom Lab Compliance Software Should Connect To

Most of the value of custom software for diagnostic labs comes from what it connects to. Before any build starts, list the systems the records need to talk to.

  • The LIMS or LIS, for test systems, runs, results, and which staff performed which tests.
  • Instrument middleware or instruments, for QC results, function checks, and run metadata.
  • Inventory or purchasing, for reagent lots, receipt dates, and expiry.
  • Environmental sensors, for storage and room readings.
  • HR or identity systems, for staff roles, start dates, and qualifications, so competency schedules stay current.

Decide which system owns each record before connecting anything. The custom LIMS requirements guide covers how to write those ownership rules, and NonStop's LIS and LIMS integration services cover the interfaces themselves.

How NonStop Builds Custom Software for Diagnostic Labs

NonStop builds software for lab needs that don't fit a LIMS, a reporting platform or a portal. Published examples include:

  • QC dashboard built around a lab's own control charts
  • Scheduling system for a specific instrument rotation
  • Internal tools shaped around one team's exact process
  • Instrument-control software

Projects start from how your team works today rather than a generic template, and scope stays tied to the problem you named. Systems that touch lab data get role-based access, audit logging, and data classification from the start. Integration with your LIMS, EHR, and instruments uses HL7 v2 and FHIR R4 where relevant.

NonStop's forward-deployed engineers work directly with your team and deliver in stages, so the lab can change direction before the build is finished. When it ships, your lab owns the code, the data, and the roadmap outright. The work is engineered for the CLIA and CAP environment, and certification and accreditation stay with your lab. NonStop builds for clinical chemistry, toxicology, pathology, and reference labs and multi-site networks, as well as genomics and molecular labs.

If the records you are trying to connect really belong inside a LIMS, custom LIMS development may be the better fit than a separate tool.

Custom Software for Diagnostic Labs: FAQs

What records does CLIA require diagnostic labs to keep for QC and maintenance?

Labs must document all control procedures, perform and document maintenance and function checks at least as often as the manufacturer specifies, and keep records of these analytic systems activities for at least two years under 42 CFR 493.1105.

How often does CLIA require competency assessment?

Twice during the first year a person tests patient specimens, then at least once a year. Staff must also be reassessed before reporting results on a new method or instrument.

Who can perform CLIA competency assessments?

The technical consultant for moderate complexity testing, or the technical supervisor for high complexity testing, who may delegate in writing to a qualified general supervisor. The laboratory director remains ultimately responsible.

What are the most common CLIA deficiencies?

In the most recent list CMS has published, covering 2024, CMS ranked defining and monitoring storage and test operating conditions first and assessing employee and consultant competency second. Expired or deteriorated supplies and manufacturer-specified maintenance were also in the top ten.

Does a reagent lot change require calibration verification?

A complete change of reagents for a procedure triggers calibration verification under 42 CFR 493.1255, unless the lab can show that changing lot numbers does not affect the reportable range or control values.

Can lab compliance records stay in Excel?

Yes, for a small, single-site lab with one clear owner, controlled templates, and scheduled review. Once records need to link to the LIMS, instruments, or other sites, spreadsheets become hard to keep complete.

Is custom software for diagnostic labs CLIA certified?

No software is CLIA certified. CLIA certification belongs to the laboratory. Software can be engineered to support the records and controls a lab needs for its own compliance.

Does ISO 15189:2022 cover competency and equipment records?

Yes. Clause 6.2 covers personnel, including competence and personnel records, clause 6.4 covers equipment, and clause 6.6 covers reagents and consumables, including acceptance testing and records.

A Practical First Step for Your Lab Compliance Records

Pick the record that caused the most work at your last inspection. Write down where it lives, who owns it, and which other records it depends on. That one page is enough for a useful conversation about whether to keep it, buy for it, or build for it.