Setting up an immunoassay analyzer for test menu expansion in a reference lab usually means treating it as a new assay introduction + new platform verification/validation + operational integration project. The exact steps depend on whether the assay is FDA-cleared/CE-marked vs laboratory-developed, and on your country’s regulatory framework, but the workflow is broadly similar.

1) Define the business and clinical scope

Start by documenting:

• Which analytes you want to add
• Intended use and clinical utility
• Expected test volume, turnaround time, and sample types
• Target population and reference lab client needs
• Competitive fit: why this assay/platform vs send-out or existing method

Deliverable: a brief menu expansion business case.

2) Check regulatory and accreditation requirements

Confirm requirements for your lab system, such as:

• CLIA/CAP (US) or equivalent local accreditation
• ISO 15189 or national quality standards
• Manufacturer’s instructions for use (IFU)
• Requirements for verification vs validation
• Any LDT rules if the assay is modified or not FDA-cleared for your use

Deliverable: a regulatory classification of each assay.

3) Assess instrument and workflow fit

Verify the analyzer can support:

• Throughput and STAT/priority handling
• Sample tube compatibility, dead volume, and aliquoting needs
• Reagent storage, onboard stability, calibration frequency
• Barcode/LIS connectivity
• Maintenance and uptime expectations
• Cross-contamination risk and carryover controls

Deliverable: an instrument suitability assessment.

4) Build the assay implementation plan

For each test, define:

• Methodology and manufacturer claims
• Specimen type(s) and collection requirements
• Calibration materials and frequency
• QC materials, levels, and acceptance criteria
• Reportable range, dilution rules, and reflex testing
• Interferences: hemolysis, lipemia, icterus, heterophile antibodies, biotin, etc.
• Critical values and comments

Deliverable: a test implementation worksheet.

5) Perform verification/validation

Typical studies include:

If an FDA-cleared/CE-marked assay

You usually verify key performance claims:

• Precision
• Accuracy/comparison against comparator or reference method
• Reportable range/linearity
• Analytical sensitivity if applicable
• Reference interval verification
• Carryover
• Interference
• Method-specific QC performance

If an LDT or modified assay

You need a fuller validation:

• Precision
• Accuracy
• Analytical sensitivity/specificity
• Linearity/reportable range
• Reference interval establishment/verification
• Interference studies
• Robustness/precision across operators/instruments/lots
• Stability of specimens and reagents

Deliverable: a signed validation/verification report.

6) Set up quality control and calibration

Establish:

• Control materials and levels
• QC frequency and rules
• Westgard or other decision rules
• Calibration intervals and triggers
• Lot-to-lot verification for reagents/calibrators/controls
• Proficiency testing enrollment if available
• Delta checks or trend monitoring where useful

Deliverable: updated QC SOPs and acceptance criteria.

7) Integrate LIS and reporting

Make sure you configure:

• Test codes, units, reference ranges, flags
• Result comments and interpretive text
• Reflex algorithms and auto-verification rules
• Interface mapping from analyzer to LIS
• Critical result notification workflow
• Result formatting for send-out clients

Deliverable: LIS build and interface testing sign-off.

8) Update SOPs and train staff

Create or revise SOPs for:

• Sample receipt and preparation
• Analyzer startup/shutdown
• QC and calibration
• Troubleshooting
• Result review and release
• Maintenance and troubleshooting escalation

Train and competency-assess:

• Medical technologists/MLS
• Supervisors
• Pathologists/clinical consultants
• Client service staff if results will be communicated externally

Deliverable: training records and competency documentation.

9) Run a controlled go-live

Use a phased launch:

• Limited sample volume
• Parallel testing if needed
• Daily review of QC and result trends
• Enhanced oversight by senior staff/vendor support
• Temporary manual result review before auto-release

Deliverable: go-live checklist and stabilization review.

10) Monitor post-implementation performance

Track:

• QC failure rates
• Calibration frequency
• Rework and repeat rates
• TAT
• Inventory and reagent wastage
• Complaints or discordant results
• Ongoing method performance against known cases

Deliverable: a post-launch quality dashboard.

---

Practical reference lab considerations

Because you’re a reference lab, pay special attention to:

• High sample diversity and complex matrices
• Send-out-client harmonization of reference ranges and units
• Reflex testing logic
• Specimen stability during transport
• Communicating method changes to clients because results may shift vs prior platforms
• Inter-laboratory comparability if you have multiple sites

---

A simple project structure

You can manage it as:

1. Feasibility review
2. Regulatory review
3. Method verification/validation
4. IT/LIS build
5. SOP/training
6. Go-live
7. Post-go-live monitoring

---

Useful documents to prepare

• Business case
• Regulatory gap assessment
• Assay implementation worksheet
• Validation/verification protocol
• Validation summary report
• SOPs
• Training competency forms
• LIS build specification
• Go-live checklist
• Post-implementation review

If you want, I can also give you:

1. a step-by-step implementation checklist,
2. a validation protocol template, or
3. a CAP/CLIA-style checklist for immunoassay menu expansion.