Switching LIS vendor: a migration checklist for small labs
Labs stay on software they have outgrown because switching feels risky. It does carry risk, but most of it is predictable and manageable. This checklist covers what a small lab or clinic should plan when moving from one LIS or lab system to another: the contract, the data, the interfaces, validation and the cutover day.
Written and reviewed by the Catenix team. How these guides are written and checked.
In brief
- Read your current contract first: notice period, renewal date and the terms for exporting your data.
- Decide what history you need: full historical results for cumulative views, or an archive you can search.
- Rebuild interfaces in parallel; analysers and EHR links can usually be tested against the new system before cutover.
- Validate the new system with a defined test plan, then cut over on a quiet day with a rollback plan.
- Catenix can run alongside your current system during migration. It can bulk import historical results from a CSV export, and we plan the migration with you, including what history to bring across.
Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).
Step 1: the contract
Find the notice period, renewal date and any minimum term. Many labs discover too late that notice had to be given months before renewal. Check whether data export is included or charged, and in what format. If the contract is silent, ask for a written export commitment now, while you are still a customer.
Step 2: the data
Decide what must come across:
| Data | Usually needed? | Notes |
|---|---|---|
| Patient demographics | Yes | Needed for matching and cumulative views |
| Historical results | Often | Needed if clinicians compare with previous values |
| Reports already issued | Retain | Can be an archive rather than live data |
| QC history | Retain | Needed for inspections covering the past period |
| Competency and training | Yes | Current status at least, with history archived |
| Audit trail | Retain | Keep the old system's audit accessible for your retention period |
| Test catalogue and ranges | Rebuild | Usually rebuilt and verified rather than imported |
Ask the old vendor for a sample export early, so you can test the import before the deadline. Common formats are CSV, database extracts, HL7 messages or PDF archives.
What a usable results export looks like
For results you will bring across, a delimited file with one row per result is the easiest to check and import. A sample:
patient_id,test_code,test_name,value,unit,timestamp MRN12345,TSH,Thyroid stimulating hormone,2.15,mIU/L,2026-03-02T09:45:00 MRN12345,FT4,Free thyroxine,14.2,pmol/L,2026-03-02T09:45:00 MRN20877,HBA1C,HbA1c,48,mmol/mol,2026-03-02T10:10:00
Before you import anything, check five things. The patient identifier must be stable and must match the patients in the new system. Test codes must map to the new test catalogue, one to one. Units must be present on every row, and any change of units between systems must be converted deliberately, not silently. The timestamp must be the collection or result time, not the date of the export. And the row count must reconcile with a count from the old system. Qualitative results, comments and issued reports often need separate handling, so ask for them separately. All values above are invented for the example.
Step 3: interfaces
List every analyser and every outbound link. For each analyser, confirm the new vendor's driver and the protocol. Analyser not on the new vendor's list? Catenix builds the driver, usually within a couple of days. Our analyser connection guides and the open connectivity dataset list the protocol for 130 analysers, which helps you check each one quickly. For the EHR, ask the EHR vendor whether changing the lab system needs a new interface project, and start it early. Where possible, connect analysers to the new system in a test mode before cutover, so the first live day is not the first test. See how lab orders and results interfaces work.
Step 4: validation
Write a test plan covering every test on every analyser, QC filing, review and release, report layout, delivery to the EHR, corrected results and an outage. Run it in the new system and record the outcomes. Compare a sample of real reports from the old and new systems. Validation evidence belongs in your quality system and will be asked for at your next inspection.
Step 5: cutover
Pick a quiet day. Agree a cutover time after which all new samples go to the new system. Decide what happens to samples in progress at that moment. Have a rollback plan and a named person who decides whether to use it. Keep read-only access to the old system for your retention period, or a searchable archive.
Step 6: after go-live
Review the first week daily: missing results, mismatches, delivery failures and user questions. Then review weekly for a month. Close the old contract only when you are sure everything you need has been exported and checked.
A realistic timeline for a small lab
| When | Step |
|---|---|
| Week 0 | Give notice under the contract; ask the old vendor for a sample export |
| Weeks 1 to 2 | Test the sample export; agree what history comes across |
| Weeks 2 to 3 | Set up the test catalogue, ranges, report templates and users in the new system |
| Weeks 3 to 4 | Connect analysers in test mode; test the EHR interface; import history |
| Weeks 4 to 5 | Run the validation plan and sign it off |
| Cutover day | New samples go to the new system from an agreed time |
| Four weeks after | Daily, then weekly reviews; old system kept read-only or archived |
The EHR vendor's interface process is the item most likely to stretch this, so request it in week 0.
Common mistakes
- Missing the notice window, and paying for another year of the old system.
- Importing history without checking units, so old and new values cannot be compared.
- Loose test code mapping, so a trend joins results from different methods.
- Cutting over before a weekend, when fewer people are around to fix problems.
- Switching off the old system too early, before the archive and audit trail are safe.
- Forgetting to tell people: partner clinics, the EHR vendor and staff need the date.
Questions to ask both vendors
Ask the old vendor: which export formats are available, what the export costs, how long it takes, whether the audit trail can be exported, and whether read-only access continues after the contract ends.
Ask the new vendor: what can be imported and in which format, how patients are matched, who maps test codes, whether the systems can run side by side for validation, what validation support is included, and what the rollback plan is.
The validation plan for a migration
Validate the new system as if it were new to the lab, and add migration checks:
- every test on every analyser, including QC at each level
- report layout for each client or partner clinic, compared with a real report from the old system
- delivery to each EHR, GP route and patient portal, including a corrected result
- imported history: row counts reconciled, a sample of patients checked value by value, units confirmed
- user roles: each person can do what they should, and cannot do what they should not
- an internet outage during a run
Who to tell, and when
Partner clinics and referring clinicians need the cutover date, any change to report layout, and who to call with problems. The EHR vendor and any GP practices receiving results need the date of the interface switch. Staff need the cutoff time for new samples and the rollback plan. Patients rarely need to know, unless the portal or app they use is changing.
Where Catenix fits
Catenix can run alongside your current system during migration, connect your analysers through its on-site gateway in ASTM E1394, HL7 v2 or POCT1-A2, and be validated before you cut over. Catenix includes a bulk import for historical results from a CSV file, and we plan the migration with you, including what history to bring across and how patients are matched. Your test catalogue, ranges and report templates are rebuilt with you. It is priced per site with no per-test fees, and a full export of your own data in standard formats is available to you at any time. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device.
Questions people ask
How long does it take to switch LIS?
For a small lab, a few weeks is realistic once the data export and EHR interface are arranged. The longest steps are usually the old vendor's export and the EHR vendor's interface process.
Do we have to move all our historical results?
Not always. Many labs import recent history for cumulative views and keep older records in a searchable archive.
Can the old and new systems run at the same time?
Yes, for testing and validation. Avoid running both live for long; one system of record is safer.
What if our old vendor will not export our data?
Check your contract and data protection rights. You are the controller of patient data, and your vendor processes it on your behalf.
What format should we ask our old LIS vendor to export?
Ask for a sample first. For results, a delimited file with one row per result, a stable patient identifier, test code, value, units and collection time is the easiest to check and import. PDF archives are fine for issued reports you only need to view.
When is the best time to cut over to a new LIS?
On a quiet day with full staff, not before a weekend or holiday, and only after validation is signed off. Agree the cutoff time for new samples and a rollback plan in advance.
Can we keep read-only access to our old LIS?
Ask your old vendor before you give notice. Some offer read-only access for a fee; otherwise, export the reports, results and audit trail you must keep into an archive you control, and test that you can search it.
Who maps the old test codes to the new system?
The lab approves the mapping, and the new vendor usually prepares it from the old catalogue. Check each line, especially where units or methods differ, before any history is imported.
Sources and further reading
Read next
More for coordinators.
All Catenix integrations
Plain-language guides to connecting point-of-care analysers to your LIS or EHR, and the messaging standards they use: HL7, POCT1-A2, ASTM.
Read →LIS requirements checklist for small labs
A practical LIS requirements checklist for small labs and clinics: workflow, analyser connectivity, QC, compliance, EHR delivery, security and...
Read →How much does a LIS cost?
What drives the cost of a laboratory information system: licences, per-test fees, interfaces, implementation and support, and how to compare quotes.
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.