In this article, we'll explore how to:
- Map the workflow your lab actually runs before listing any features.
- Write custom LIMS requirements that a tester can pass or fail, using a ready-made register format.
- Attach the right US, UK, and EU regulations to each requirement.
- Specify how the system behaves on its worst day as well as its best.
- Plan data migration and validation as one track instead of two afterthoughts.
- Read cost and timeline from your requirements, and spot weak proposals before signing.
Stage 1: Map Your Workflow Before Writing Custom LIMS Requirements
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: 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.
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: 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
UK Labs: ISO 15189:2022 and UK GDPR Requirements for a Custom LIMS
EU Labs: GDPR and IVDR Requirements for a Custom LIMS
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: 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.
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: 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.
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).
Questions That Expose a Weak Custom LIMS Proposal
Put these to every vendor. Vague answers tell you where the requirements work was skipped.
- Who writes the requirements, and who signs them? The lab should own and approve them, even if the vendor drafts.
- Which register rows are out of scope? Migration and downtime are usually omitted.
- Who owns the source code, data, documentation, and hosting accounts after go-live? The answer should be the lab, in the contract.
- How will configuration changes be controlled once we are live? There should be a defined test-and-approve path.
- 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.
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.
