Custom LIMS Requirements: A Six-Stage Specification Playbook for Diagnostic Labs

Before anyone writes a line of code for a custom LIMS, five people in your lab need to agree on the same document.

Those five are the lab director, the quality lead, the operations manager, the informatics lead, and whoever owns billing. When that agreement is missing, the build does not fail on day one. It fails in month six, when the engineering team asks a question about rejected specimens or corrected reports that nobody can answer without a meeting.

That document is your custom LIMS requirements specification. This playbook walks through writing it in six stages, in the order a good build team would ask for it. It targets labs in the US, UK, and Europe that have already decided a commercial LIMS will not fit their test menu or workflow.

Short answer

Custom LIMS requirements are numbered, testable statements of what the system must do at every workflow step, which regulation or procedure each one serves, how important it is, and how it will be proven before go-live. A strong specification also covers downtime, security, data migration, and validation, because those decide whether the system survives inspection.

In this article, we'll explore how to:

  1. Map the workflow your lab actually runs before listing any features.
  2. Write custom LIMS requirements that a tester can pass or fail, using a ready-made register format.
  3. Attach the right US, UK, and EU regulations to each requirement.
  4. Specify how the system behaves on its worst day as well as its best.
  5. Plan data migration and validation as one track instead of two afterthoughts.
  6. Read cost and timeline from your requirements, and spot weak proposals before signing.
Stage 1 of 6

Stage 1: Map Your Workflow Before Writing Custom LIMS Requirements

Stage 1Map the workflow you actually run
Who
One representative from accessioning, each testing bench, review, reporting, client services, quality, and billing.
Output
A step-by-step map from requisition to corrected report, with every hand-off, exception, and workaround marked.
Time box
Short, focused workshops per area rather than one long meeting.

Requirements written from memory describe the procedure manual. Requirements written from observation describe the lab.

Walk a real specimen through every step and record what people do when something goes wrong, because the exceptions are where a custom build earns its cost.

Nobody needs to start from scratch. ASTM E1578-18, the Standard Guide for Laboratory Informatics, was reapproved in 2026 and describes the functions a laboratory informatics system typically covers. LIMSpec, a free specification on LIMSwiki under a Creative Commons license, turns that guide into requirement statements and supports each one with regulations or standards. Its edition for medical diagnostics labs draws on more than 130 documents, including 42 CFR Part 493, the CAP accreditation manual, ISO 15189, and 21 CFR Part 11.

Use those references to check for gaps after the workflow map exists. A template tells you what a LIMS could do. Only your map tells you what yours must do.

Stage 2 of 6

Stage 2: Write Custom LIMS Requirements a Tester Can Pass or Fail

Every requirement needs five parts. If any part is missing, people will argue about the requirement later.

  • An ID
  • A single testable statement
  • The source that justifies it
  • A priority
  • The test that will prove it

The register below shows that format for the stages where diagnostic labs most often under-specify. Copy the structure, then replace the statements with your own.

IDRequirementSourcePriorityProven by
ORD-01Reject any electronic or manual order without an authorized requester, a patient identifier, and a requested test, and name the missing field.42 CFR 493.1241MustSubmit orders with each field missing; confirm rejection and message
ORD-02Flag an order as a suspected duplicate when patient, test, and collection date match an open order, and route it to a named reviewer.Lab procedureMustResubmit an identical order; confirm no second accession
ACC-01Assign one accession ID per specimen at receipt and record receipt date and time.42 CFR 493.1283(a)MustReceive specimens; inspect record and label
ACC-02Record rejection reason, specimen condition, and disposition for every specimen failing acceptance criteria.42 CFR 493.1283(a)(3)MustReject test specimens; confirm fields and retrievability
ACC-03Block testing on any specimen without a matched order.Lab procedureMustAttempt to start testing on an unmatched specimen
CFG-01Version assay definitions, reflex rules, and QC rules, and store the version used with every result.Lab procedure; change controlMustChange a rule; confirm old and new results show different versions
CFG-02Require recorded approval before a configuration change applies to patient testing.42 CFR 493.1251(d)MustAttempt to activate an unapproved change
INS-01For each analyzer, handle no response, partial results, and reruns without silent data loss.Lab procedureMustSimulate each failure per instrument
INS-02Generate sequencer sample sheets and link each result to its run metadata.Lab procedureShouldTrace a result back to its run
RPT-01Issue a corrected report as a new version, send it to every destination that received the original, and keep both versions.42 CFR 493.1291(k)MustCorrect a released result; check every destination and the archive
INT-01Treat a result as delivered only when the destination confirms it processed the message.42 CFR 493.1291(a)MustSend to a test endpoint that accepts but fails processing
INT-02Route unmatched or rejected messages to an exception queue with a named owner.Lab procedureMustSend unmatched messages; confirm queue entry and owner

Several requirements cite lab procedure rather than a regulation, which is expected. Regulations set a floor; your procedures describe how your lab meets it, and the system has to support both. Where several existing systems will sit around the new LIMS, settle which one owns each record before writing the integration rows. The LIS vs. LIMS vs. middleware guide covers that ownership decision.

Stage 3 of 6

Stage 3: Attach US, UK, and EU Regulations to Your Custom LIMS Requirements

Regulations do not design the system for you. They define the records and behaviors the system must prove. Read the next three subsections by region and add a source to every register row they touch. Whatever the region, certification and accreditation stay with the laboratory.

US Labs: CLIA, CAP, and HIPAA Requirements for a Custom LIMS

RegionUnited States
Retention
42 CFR 493.1105: keep test requisitions and authorizations for at least 2 years and pathology test reports for at least 10 years, so retention rules must be configurable by record type.
Change approval
42 CFR 493.1251(d): procedures and their changes are approved, signed and dated by the laboratory director before use.
CAP accreditation
Map each applicable item in the current CAP checklist edition to a register row during specification.
HIPAA technical safeguards
45 CFR 164.312: unique user identification, audit controls, integrity, authentication, and transmission security for ePHI.
21 CFR Part 11
Only where records fall under FDA records requirements or go to FDA, such as clinical trial work (21 CFR 11.1).

UK Labs: ISO 15189:2022 and UK GDPR Requirements for a Custom LIMS

RegionUnited Kingdom
ISO 15189:2022
ISO 15189:2022 clause 7.6: control of data and information management, including information systems management, downtime plans, and off-site management.
Transition
UKAS set December 2025 as the deadline for labs accredited to ISO 15189:2012 to move to the 2022 edition (UKAS), so specify against the 2022 edition.
UK GDPR
The same accuracy and security-of-processing principles as the EU regulation below.

EU Labs: GDPR and IVDR Requirements for a Custom LIMS

RegionEuropean Union
GDPR Article 5(1)(d)
GDPR Article 5(1)(d): personal data must be accurate and, where necessary, kept up to date, which needs a defined correction workflow.
GDPR Article 32
GDPR Article 32: ongoing confidentiality, integrity, availability, and resilience; timely restoration after an incident; and regular testing of security measures.
EU IVDR Article 5(5)
EU IVDR Article 5(5): in-house devices are exempt only under conditions that include EN ISO 15189 compliance and no transfer to another legal entity, so keep any result-interpretation logic that could qualify as a device separate and documented.
Stage 4 of 6

Stage 4: Specify How Your Custom LIMS Behaves on a Bad Day

Feature lists describe good days. These questions describe the days that decide whether the system survives its first year. Turn each answer into a register row.

  • The LIMS is down for six hours. What happens to specimens arriving now? Specify downtime intake, labeling, and the reconciliation step when the system returns.
  • An inspector asks who changed this result and why. Specify an audit trail that records who, when, what changed, and why, that cannot be edited, and that auditors can search and export.
  • The server room floods tonight. Specify recovery time and data loss limits, and how often restores are tested.
  • Volume doubles next year. Specify expected daily specimens, peak hours, and response times for the busiest screens, with headroom.
  • A patient asks where their data is stored. Specify hosting location and, for UK and EU labs, whether personal data may leave the region.
  • A technologist leaves the lab tomorrow. Specify role-based permissions, unique accounts, electronic signatures where procedures require them, and same-day access removal.
  • A second site opens. Specify whether sites share an accession space, test menu, and reporting identity.
  • The lab wants to add a new assay without calling engineers. Specify which changes staff make through configuration and which need engineering and revalidation.
Stage 5 of 6

Stage 5: Plan Custom LIMS Data Migration and Validation Together

Most labs plan migration and validation separately and late. They belong on one track because validation must prove the migrated data is correct. The timeline below shows what happens in each phase.

PhaseData migrationValidation
Before the buildInventory every source, including spreadsheets; map every field, code, and unit; agree cleansing rules in writingRank register rows by risk to patient results; agree test depth per risk level
During the buildRun trial migrations; reconcile record counts and key values; investigate every differenceLink each register row to at least one test; test interfaces with failure paths
Before go-liveMigrate or archive legacy audit trails in a readable, linked form; freeze the sourceUser acceptance testing on real cases, including rejected specimens, reruns, and corrected reports; parallel run until outputs match
Go-live decisionFinal reconciliation sign-offLaboratory director approval recorded under 42 CFR 493.1251(d)
After go-liveKeep a read-only archive searchable for the full retention periodChange control: every later change is tested and approved the same way

CLIA does not prescribe a software validation method. FDA's Computer Software Assurance guidance, final since September 2025, offers a useful model even though it is written for device manufacturers.

Put the most testing effort where a failure could affect a patient result, and keep lighter evidence for low-risk features.

Stage 6 of 6

Stage 6: Read Custom LIMS Cost and Timeline From Your Requirements

Once the register exists, cost can be estimated row by row. Each row has a size, and a few row types dominate the total.

Requirement typeImpact on scopeWhy
Test menu breadth and assay complexityHighEvery assay needs definitions, rules, reports, and validation
Instruments and integrationsHighEvery interface needs mapping, failure handling, and testing
Data migration volume and qualityHighMessy legacy data multiplies cleansing and reconciliation work
Validation depthMedium to highHigher-risk functions need more evidence
Multi-site or multi-entity needsMediumShared or separate access spaces and reporting identities add design work
Hosting, residency, and securityMediumSelf-hosted, regional, or high-availability setups add infrastructure work
No-code configurability for staffMediumCosts more to build, saves engineering time later

Be skeptical of published numbers. One vendor article cites USD 200,000 to USD 1.5 million for mid-to-large labs (Ideas2IT), and another cites 9 to 18 months (Velvetech), and neither shows a source. From the other side of the argument, an Illumina customer story reports one genomics center estimating that building its own LIMS would have taken tens of person years (Illumina).

Better estimator

A finished register is a better estimator than either. Remember the running costs too: a custom LIMS avoids per-sample licensing but needs hosting, maintenance, and change control for its whole life.

Questions That Expose a Weak Custom LIMS Proposal

Put these to every vendor. Vague answers tell you where the requirements work was skipped.

  1. Who writes the requirements, and who signs them? The lab should own and approve them, even if the vendor drafts.
  2. Which register rows are out of scope? Migration and downtime are usually omitted.
  3. Who owns the source code, data, documentation, and hosting accounts after go-live? The answer should be the lab, in the contract.
  4. How will configuration changes be controlled once we are live? There should be a defined test-and-approve path.
  5. Is the software CLIA-compliant? A credible vendor explains which features support your compliance, because compliance belongs to the lab.

Where NonStop Fits in a Custom LIMS Build

NonStop's custom LIMS development work is aimed at diagnostic and genomic testing labs with no usable LIMS today, or a test menu and workflow no commercial product fits. The table maps what NonStop publishes about that work to the six stages above.

StageWhat NonStop brings
1. Workflow mapAccessioning rules, specimen types, and chain-of-custody tracking tailored to the lab's own intake process
2. Requirements registerAssay configuration through test definitions, reflex rules, QC rules, and report templates, with each new assay still validated by the lab
2. Integration rowsHL7 v2 and FHIR R4 to EHR and billing through Mirth Connect; analyzers over ASTM/LIS2-A or vendor middleware; sequencer sample sheets and run-metadata ingestion
3. RegulationsAudit trail and role-based access built in from day one, designed for the evidence a CLIA or CAP inspection asks for
4. Bad-day behaviorSelf-hosted deployment on-premise or in a lab-controlled cloud, keeping PHI inside that environment
5. MigrationSamples, results, and audit history migrated and reconciled against source records before go-live
OwnershipA system the lab owns outright as it grows

Intake can begin from NonStop's pre-built, production-tested software: SmartReq reads requisitions and flags low-confidence fields for staff to confirm, and Intergenix validates orders and catches duplicates before they reach the LIMS. If the current LIMS mostly works, legacy LIMS modernization is often the better route than a new build.

For a U.S. genetic testing leader, NonStop rebuilt sample management around a LIMS-driven architecture for traceability and modernized ordering and reporting while the platform stayed live; turnaround time fell by 55%. NonStop's work is engineered for HIPAA, SOC 2, GDPR, and the CLIA and CAP environment.

Custom LIMS Requirements: Questions Lab Leaders Ask

What should a custom LIMS requirements document include?

Numbered, testable requirements for every workflow step from order intake to corrected reports, each with a source, priority, and test, plus requirements for compliance, audit trail, access control, downtime, backup, performance, hosting, retention and data migration.

Is there a free LIMS requirements template?

Yes. LIMSpec on LIMSwiki is a free, Creative Commons-licensed specification based on ASTM E1578-18, with an edition for medical diagnostics labs. Use it to check for gaps after mapping your own workflow.

What drives the cost of a custom LIMS?

Test menu breadth, the number of instruments and integrations, data migration volume and quality, validation depth, multi-site needs, hosting and security choices, and how much staff need to configure without code.

Does a custom LIMS need to be validated under CLIA?

CLIA does not prescribe a software validation method, but the laboratory director must approve procedure changes before use, and the lab must show the system works as its procedures describe. Risk-based testing traced to each requirement produces that evidence.

Is 21 CFR Part 11 required for a custom LIMS in a CLIA lab?

Not automatically. Part 11 applies to electronic records kept under FDA records requirements or submitted to FDA. Labs doing only CLIA testing follow CLIA, while labs supporting clinical trials may need Part 11 controls for those records.

Can a custom LIMS support ISO 15189 accreditation?

Yes, if it is specified for it. ISO 15189:2022 clause 7.6 covers control of data and information management, including information systems management, downtime plans and off-site management. The lab holds the accreditation; the system supplies controls and records.

How do you migrate data into a custom LIMS without losing audit history?

Inventory sources, map fields, agree cleansing rules, reconcile counts and key values, migrate or archive legacy audit trails in a readable linked form, run in parallel until outputs match, and keep a read-only archive for the retention period.

The Next Step for Your Custom LIMS Requirements

Take the workflow map and the first draft of your register, even if half the rows are still empty. That draft is enough for a useful 45-minute architecture review: a NonStop architect will go through it with your team, flag the rows most likely to stall a build, and suggest how to phase the work.