Moving a small lab off paper and spreadsheets: a step-by-step plan
Plenty of small labs still run on a request form, a printout from the analyser, a spreadsheet of results, a QC binder and a temperature log on the fridge door. It works until volume grows, a result goes to the wrong patient, or an inspector asks to see the QC behind a specific result. This guide is a practical plan for moving to connected software without stopping the lab.
Written and reviewed by the Catenix team. How these guides are written and checked.
In brief
- The biggest risks in a paper and spreadsheet lab are transcription errors, QC that is not linked to results, and records that cannot prove who did what.
- Start by listing every record you keep today and where it lives; most map directly to a module in modern lab software.
- Connect the analysers first; removing typed results gives the fastest win in time and safety.
- Run paper and software in parallel for a short, defined validation period, then stop the paper.
- Catenix replaces typed results, QC binders, competency spreadsheets and paper logs with one connected record, set up in days for supported analysers.
Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).
What paper and spreadsheets cost you
Transcription errors. Every number copied from an analyser printout into a spreadsheet or an EHR can be mistyped, put against the wrong patient or skipped. Our guide to POCT transcription errors looks at how often this happens and what it costs.
QC that floats free. If QC is recorded in a binder, nobody can show without effort that a given patient result was released after QC passed on that analyser that day. Inspectors ask exactly that.
No reliable audit trail. A spreadsheet can be edited by anyone with no record of what changed. Paper can be lost.
Time. Typing results, filing printouts, chasing signatures and building monthly QC charts by hand consumes hours each week that scientists could spend on testing.
Growth limits. Adding a site, an analyser or a partner clinic multiplies the paperwork.
Step 1: list what you record today
Walk through a normal day and list every record:
| Paper or spreadsheet today | Where it goes in lab software |
|---|---|
| Request forms | Registration, requests and accession numbers |
| Analyser printouts | Results received directly from the analyser |
| Results spreadsheet | The results record, linked to patient and request |
| QC binder and charts | QC module with Levey-Jennings charts and Westgard rules |
| Training records | Operator competency records |
| Fridge temperature sheets | Environmental monitoring |
| Maintenance log | Equipment and maintenance records |
| Incident book | Nonconformities and corrective actions |
| Reports typed in a word processor | Report templates filled from the record |
This list becomes your requirements and your validation plan.
Step 2: connect the analysers first
The fastest, safest win is stopping the typing. Confirm which protocol each analyser uses and whether it supports bidirectional host query. Connect each one so results arrive in the software matched to the right patient and request, with QC runs filed separately. Analyser not on the list? We build the driver, usually within a couple of days. See connecting an analyser to a LIS. Check each analyser in our analyser connection guides or the open connectivity dataset, or ask the question in ChatGPT or Claude through our AI assistant connector.
Step 3: build the test catalogue and reports
Enter each test with its units, reference ranges and comments as your lab defines them. Build report templates with your branding and the details your clients and regulators require. Decide who may release which results.
Step 4: move QC and competency
Enter QC lots and target values, set the Westgard rules you use, and decide whether a QC failure should hold patient results. Enter each operator's training and competency, and decide whether an untrained operator should be blocked. This is the step that turns software into inspection evidence.
Step 5: run in parallel, then stop the paper
Run software and paper side by side for a short, defined period, often one to two weeks. Compare every result, report and QC record. Record discrepancies and fix their causes. When the comparison is clean, sign off the validation and stop the paper. Keep old paper records for your retention period. Do not let parallel running drift on for months; two systems are worse than one.
A worked example: a two-analyser lab, week by week
An illustrative clinic lab runs a chemistry analyser and a haematology counter, records results in a spreadsheet and keeps QC in a binder. A realistic plan looks like this:
| Week | What happens | Output |
|---|---|---|
| 1 | Every record listed; analyser models and protocols confirmed; software chosen | Requirements list and a validation plan |
| 2 | Gateway installed; both analysers connected; first results traced end to end | Connection evidence for each analyser |
| 2 | Test catalogue, units, ranges, report template and user roles set up | Approved catalogue and template |
| 3 | QC lots and rules entered; operator competency entered | QC and competency live |
| 3 to 4 | Parallel running, with every result compared against the paper record | Signed comparison and discrepancy log |
| 5 | Validation signed off; paper stopped for new work | Go-live record |
The plan stretches if an analyser needs a new driver, if an EHR interface needs vendor approval, or if staff can only spare a few hours a week. It shrinks if the analysers are already supported and the test menu is short.
What the validation plan should cover
- Every test on every analyser, with values inside and outside the reference range.
- QC at every level, confirming it files as QC, and that a failure holds patient results if you chose that rule.
- A result run by an operator without current competency, if you chose to block.
- Manual entry for anything not connected, with the same review step.
- The report layout and every delivery route: print, email, portal or EHR.
- A corrected result after release.
- An internet outage during a run.
Record each check, the expected outcome, the actual outcome and who confirmed it. That record is your validation evidence.
Common mistakes
- Digitising the paper process instead of improving it. Use the move to remove steps such as double entry and hand-drawn QC charts.
- Letting parallel running drift on. Set an end date and the criteria for stopping before you start.
- Shared logins to save time. Each person needs their own login from day one, or the audit trail means nothing.
- Moving everything at once. Connect analysers first; add billing, stock and other modules once results are stable.
- No owner. Name one person responsible for the project and the validation sign-off.
Questions to ask vendors
- Which of our analysers are supported today, by model?
- What can we configure ourselves, and what needs the vendor?
- What validation support and test scripts do you provide?
- How long until our first real result, and what do you need from us?
- Does it work on the small screens next to our analysers?
Step 6: use the data
Once records are connected, you can see turnaround times, QC trends, workload by analyser and competency due dates on a dashboard instead of building them by hand. See POCT KPIs worth tracking.
What to do with the records you already have
Paper and spreadsheets do not need to come across line by line. Keep paper records in a labelled, secure archive for the retention period your regulator and accreditation body require, with a simple index of what is where. Lock old spreadsheets as read-only and store them with the archive, so nobody keeps adding to them after go-live. If clinicians need recent history for comparison, bring across a defined period of results, such as the last year, as a structured import rather than retyping, and check it against the source.
Bringing the team with you
The people at the bench decide whether the move works. Involve them in the record inventory in step 1, because they know where the workarounds are. Train each person on their own login before parallel running starts, not on the day. Give one named person the job of collecting questions and problems during the first weeks, and review that list every day until it is short.
Where Catenix fits
Catenix replaces the paper and spreadsheet stack in one platform: registration and accession numbers, analyser connectivity over HL7 v2, POCT1-A2 and ASTM E1394, QC with Levey-Jennings charts and Westgard rules, operator competency, temperature and maintenance logs, nonconformities, review and release, branded reports and a tamper-evident audit trail. For supported analysers, set-up takes days: install the gateway, connect the analysers, confirm the first traced result, go live. It is priced per site with no per-test fees. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device. See lab equipment and temperature logs.
Questions people ask
How long does it take to move a small lab off paper?
With supported analysers, the software can be live in days. Allow one to two weeks of parallel running for validation.
Do we have to digitise old paper records?
Usually not. Keep them for your retention period and start digital records from go-live.
What should we move first?
Analyser connectivity, because removing typed results gives the biggest gain in time and safety.
Can staff without IT experience run lab software?
Yes. Modern cloud lab software is run through a web browser; the vendor supports the gateway and connections.
What if one of our analysers cannot connect?
Results can be entered manually with the same QC and audit controls, and in most cases a driver can be built for the analyser.
Do we need to validate lab software in a small lab?
Yes. Whatever the size, you need evidence that the system does what you rely on it to do, for your tests, analysers and reports, before it replaces the paper record. Keep the plan and the results in your quality system.
Can we keep using spreadsheets for some records?
You can, but every spreadsheet that holds part of the record weakens the audit trail. Move results, QC and competency first, because inspectors link those three most often.
How do we show an inspector that the new system was validated?
Show the validation plan, the test records with expected and actual outcomes, the parallel-running comparison, the discrepancies and how each was resolved, and the dated sign-off. Keep them in your quality system with the change record for go-live.
Sources and further reading
Read next
More for coordinators.
Catenix quality control and governance
Quality control that runs itself: QC captured from the analyser, Westgard rules and Levey-Jennings per device and analyte, lockouts and monthly...
Read →Cloud LIS for small and private labs
What a cloud laboratory information system should do for a small or private lab: analyser connectivity, QC, review, reports, EHR links, security and...
Read →POCT transcription errors
POCT transcription errors occur whenever a result is re-keyed by hand. The error types, why they are under-reported, what they cost and how to end...
Read →Take it with you
The buyer's guide, in your inbox.
Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.
Get the POCT connectivity buyer's guide
Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.
See it done in software.
A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.