CLS Platform-Wide · Case study

Designing a Shared Laboratory Experience

Clinisys wanted a single, discipline-agnostic Laboratory Information System instead of separate builds per specialty: identify what's shared across laboratory disciplines, design one experience for it, then layer in what's genuinely discipline-specific. I built the framework, and the research behind it, that made that judgment possible across twelve laboratory domains.

Laboratory discipline taxonomy mapping for healthcare domains

01 · Executive summary

One platform had to serve laboratory disciplines that do not look alike on the surface.

Clinisys was consolidating its laboratory products onto CLS, bringing disciplines as different as anatomic pathology, clinical pathology, genomics, reproductive medicine, environmental testing, pharmaceutical QC, and forensic science into a single platform. The challenge was determining what could genuinely be shared across those disciplines, and what could not.

I conducted weekly SME interviews and workshops over three months and developed a four-lens framework for comparing the work: who does it, what they work with, how it happens, and what the system must support.

The analysis mapped 16 role families, 12 laboratory domains, 15 workflow models, and 29 application flows, providing evidence for where the CLS experience could be shared and where it needed to branch.

Team members knew their own disciplines deeply but had little visibility into the others, and capabilities assumed to be discipline-specific exposed gaps that caused rework as CLS expanded into healthcare.

The framework was used for Clinical Microbiology and Clinical Pathology, and finishing its shared workflows first let Microbiology move forward.

Research question

What can genuinely be shared across CLS's twelve laboratory domains, and where must the experience diverge?

02 · Approach

Systems research: understanding the domains well enough to know what could safely be generalized.

Method

I met weekly for three months with a rotating group of three to seven SMEs across Anatomic Pathology, Clinical Pathology, Microbiology, and Scientific.

The framework emerged from early SME conversations, then became the standing interview guide for subsequent workshops: who is doing the work, what are they working with, how does the work happen, and what must the system support?

03 · Context

The apparent differences were real, but so was the structure underneath them.

Underneath the domain-specific vocabulary, both move material through receipt, processing, testing, interpretation, and reporting, with results that must remain traceable to their source. The challenge was proving that structural similarity existed precisely enough to act on it before making application-design decisions.

Challenges

  • No existing framework for comparing disciplines with different vocabulary, regulation, and workflow shape
  • Twelve domains, sixteen role families, and years of discipline-specific knowledge to reconcile
  • A premature shared decision could force genomics into a workflow built for pathology, or vice versa

Constraints

  • One application and design system for healthcare and scientific laboratories
  • SME time limited to weekly sessions across many disciplines
  • Findings had to translate directly into product and engineering input

04 · Framework

A consistent way to compare work that shared neither vocabulary nor workflow shape.

Who

Role

Who performs the activity, what they are accountable for, and where authority changes hands.

What

Objects & entities

The source, order, sample, derivatives, results, reports, and the states connecting them.

How

Process

The steps, decisions, handoffs, exceptions, and recurring workflows around the laboratory lifecycle.

Support

System capabilities

Automation, validation, integration, permissions, notifications, configuration, and traceability.

Object lifecycle

Source→Sample→Derivative→Result→Report

Each object also moves through operational states: collected, transported, received, processing, completed, stored, and disposed.

Recurring workflows

  • Identification and labeling
  • Transportation and chain of custody
  • Storage and retrieval
  • Quality control and nonconformity
  • Add-on and reflex testing
  • Reference laboratory workflows
  • Disposal

The question asked at every step

Is this shared across disciplines or different? And what causes the difference? The science, workflow, sample type, regulation, instrumentation, organizational model, or another business rule? That answer was made flow by flow, not in the abstract.

Who

People came first, because what can be shared depends on who is using it and what they are responsible for.

Bench & specialist

Hands-on laboratory work

  • Laboratory Technician / Technologist
  • Specialist Technologist
  • Specimen / Accessioning Staff
  • Phlebotomist / Collection Staff

Clinical & scientific authority

Interpretation and expertise

  • Pathologist / Physician
  • Pathologists' Assistant
  • Scientist / Researcher
  • Clinical / Scientific Specialist
  • Bioinformatics / Data Scientist

Leadership & quality

Operations and governance

  • Laboratory Manager / Supervisor
  • Laboratory Director
  • Quality / Compliance

Systems & support

Application infrastructure

  • Application / LIS Administrator
  • Systems / Integration Specialist
  • IT / Informatics Leadership
  • Administrative / Support Staff

Why the grouping mattered

The same functional categories (bench, authority, leadership, and systems) recurred in every domain even when the titles inside them changed. That consistency made a shared permissions and role model possible.

Role familyWhat they doExamples
Laboratory Technician / TechnologistPerforms routine specimen preparation, testing, instrument operation, QC, and result documentation according to established procedures.

Lab Technician, Medical Laboratory Technician (MLT), Medical Laboratory Scientist/Technologist (MLS/MT)

Specialist TechnologistPerforms technically specialized laboratory work requiring domain-specific expertise.

Histotechnologist, Cytotechnologist, Microbiology Technologist, Molecular Technologist, Cytogenetic Technologist

Pathologist / PhysicianProvides medical oversight, interprets laboratory findings, establishes diagnoses, and authorizes clinical reports where required.

AP Pathologist, Clinical Pathologist, Hematopathologist, Molecular Pathologist

Pathologists' AssistantPerforms and documents gross examination, specimen dissection, tissue selection, and other AP activities under pathologist supervision.

Pathologists' Assistant

Scientist / ResearcherDesigns and conducts experiments, develops methods, analyzes data, and interprets scientific findings.

Scientist, Research Scientist, Molecular Biologist

Clinical / Scientific SpecialistProvides advanced interpretation and subject-matter expertise within a specialized testing domain.

Clinical Scientist, Clinical Chemist, Clinical Microbiologist, Geneticist

Bioinformatics / Data ScientistProcesses, analyzes, interprets, and manages complex laboratory datasets, particularly genomic and other high-dimensional data.

Bioinformatician, Computational Biologist, Variant Scientist

Quality / ComplianceManages laboratory quality systems, audits, nonconformances, documentation, accreditation, and regulatory compliance.

Quality Manager, QA Specialist, Compliance Officer

Laboratory Manager / SupervisorOversees day-to-day laboratory operations, staffing, workload, resources, quality, and operational performance.

Section Supervisor, Lab Manager, Operations Manager

Laboratory DirectorHolds overall scientific, clinical, regulatory, and/or operational responsibility for the laboratory.

Laboratory Director, Medical Director, Scientific Director

Specimen / Accessioning StaffReceives, identifies, registers, labels, routes, tracks, and prepares specimens for laboratory workflows.

Accessioner, Specimen Processor, Sample Coordinator

Phlebotomist / Collection StaffCollects patient specimens and ensures correct patient identification, labeling, and specimen handling.

Phlebotomist, Collection Technician

Application / LIS AdministratorConfigures and maintains laboratory applications, users, workflows, rules, dictionaries, reports, and application-level integrations.

LIS Administrator, LIMS Administrator, Application Analyst

Systems / Integration SpecialistMaintains technical infrastructure and interfaces connecting laboratory applications, instruments, middleware, EHRs, and other systems.

Systems Administrator, Interface Analyst, Integration Engineer

IT / Informatics LeadershipDefines laboratory informatics architecture, governance, security, interoperability, and technology strategy.

Laboratory Informatics Manager, IT Manager

Administrative / Support StaffSupports scheduling, documentation, billing, customer service, records, logistics, and other non-testing laboratory activities.

Administrative Assistant, Client Services, Billing Specialist

What

Twelve domains formed the comparison set across healthcare and scientific laboratories.

The taxonomy extended from domains into sub-disciplines and methods, down to test types such as NGS and PCR variants, so it had enough resolution to drive design decisions rather than remain abstract.

View healthcare taxonomy ↗View scientific taxonomy ↗

Healthcare4 domains
  1. Anatomic Pathology
  2. Clinical Pathology
  3. Genomics / Molecular Diagnostics
  4. Reproductive Medicine / IVF
Scientific8 domains
  1. Environmental
  2. Pharmaceutical / Biopharmaceutical
  3. Food & Beverage
  4. Veterinary
  5. Forensic Science
  6. Agriculture
  7. Research / Biotechnology
  8. Industrial / Materials Testing

How

A shared lifecycle held across every discipline; the work underneath each stage did not.

Order→Collect / Receive→Prepare→Analyze→Interpret→Report

15 workflow models

The library tied each model to the specialties it served and documented its characteristic sequence. Four models (Transplant / Histocompatibility, IVF / Embryology, Pharmaceutical QC, and Research / Biotechnology) also made gaps outside the disciplines Clinisys applications currently supported visible.

Workflow modelPrimarily applies toTypical flow
01 · Histopathology / Surgical PathologyHistopathology, Surgical Pathology
Accession→Grossing→Processing→Embedding→Microtomy→Staining→Slide Review→Diagnosis→Report→Archive
02 · CytopathologyGYN Cytology, Non-GYN Cytology, FNA
Accession→Preparation→Staining→Screening→Pathologist Review→Diagnosis→Report
03 · Clinical LaboratoryChemistry, Hematology, Immunology, Urinalysis
Order→Collection→Preparation→Analyzer / Testing→QC→Validation→Report
04 · Clinical MicrobiologyBacteriology, Mycology, Mycobacteriology
Accession→Processing→Culture→Incubation→Identification→AST→Interpretation→Report
05 · Molecular Diagnostics / PCRPCR, qPCR, RT-PCR, dPCR
Accession→Preparation→Extraction→Amplification→Detection→QC→Interpretation→Report
06 · SequencingSanger, NGS, WES, WGS, RNA-seq
Accession→Extraction→Library Preparation→Sequencing→QC→Bioinformatics→Interpretation→Report
07 · CytogeneticsKaryotyping, FISH, CMA
Accession→Preparation / Culture→Assay→Imaging→Analysis→Interpretation→Report
08 · Flow CytometryClinical and research flow cytometry
Accession→Cell Preparation→Antibody Staining→Acquisition→Gating / Analysis→Interpretation→Report
09 · Transfusion MedicineBlood Bank
Order→Identification→ABO/Rh→Antibody Screen→Selection→Crossmatch→Issue→Transfusion
10 · Transplant / HistocompatibilityHLA, antibody testing, transplant crossmatch
Registration→Specimen→HLA / Antibody Testing→Crossmatch→Compatibility→Interpretation→Report
11 · ToxicologyClinical and forensic toxicology
Accession→Preparation→Screening→Confirmation→Quantitation→Interpretation→Report
12 · IVF / EmbryologyAndrology, Embryology, IVF
Patient / Cycle→Collection→Preparation→Fertilization→Culture→Assessment→Transfer / Cryopreservation
13 · Environmental / Food / IndustrialEnvironmental, Food, Agriculture, Materials
Registration→Chain of Custody→Preparation→Analysis→QC→Review→Certificate→Retention / Disposal
14 · Pharmaceutical QCPharma / Biopharma QC
Sample / Lot→Sampling→Preparation→Testing→QC→Review→Approval / Release→Stability
15 · Research / BiotechnologyResearch laboratories
Study Setup→Registration→Preparation→Procedure→Acquisition→Analysis→Review→Storage

Four-domain comparison

The same nineteen stages ran through each representative discipline. What changed was the vocabulary, the artifacts, and where the emphasis sat.

StageAnatomic PathologyClinical PathologyGenomicsScientific
Request / Order

Patient case or pathology procedure

Patient test order

Test or assay request; clinical or research context

Customer, project, study, sample, batch, or method

Collection

Tissue or cells collected during a clinical procedure

Patient-centric blood, urine, swab, or fluid collection

Clinical or research sample; assay-dependent

Field, production, facility, or laboratory sampling

Transport

Specimens, blocks, or slides between locations

Specimen transport to laboratory or reference lab

Controlled transport for samples or extracts

Shipment, preservation, chain of custody, conditions

Receiving

Accession to patient and case

Match specimen to patient and order

Associate sample with request and assay

Associate sample with customer, project, or study

Preparation
Grossing→fixation→embedding→sectioning
Centrifuge→separate→aliquot→dilute
Extraction→QC→normalization→library preparation
Weigh→homogenize→extract→digest
Derived material
Specimen→cassette→block→slide

Specimen or aliquot / derivative

Sample→extract→library→pool

Aliquot, extract, digest, culture, or preparation

Testing

Microscopy and ancillary stains / IHC / ISH

Automated analyzer or manual testing

PCR, molecular assays, sequencing

Instrumental or manual analytical method

Work grouping

Case, processor, or stain run

Test, analyzer rack, or batch

Plate, assay, pool, or sequencing run

Method, batch, run, or worklist

Raw output

Morphology, image, or observation

Instrument measurement or manual result

Signals, reads, sequence or run data

Measurements, observations, analytical data

Quality control

Tissue, section, and stain quality

Controls, calibration, analyzer and test QC

Extraction, library, assay, run, and data QC

Controls, blanks, standards, system suitability

Analysis

Morphologic assessment and correlation

Calculations, ranges, flags, and rules

Bioinformatics and computational analysis

Quantitation, calculations, statistics

Interpretation

Pathologist diagnosis is central

Technical validation; clinical interpretation as needed

Scientific interpretation of molecular findings

Scientific or technical review

Result

Diagnosis or findings

Patient test result

Molecular or genomic finding and interpretation

Analytical result, determination, or conclusion

Reporting

Diagnostic report; narrative and structured

Structured results to downstream clinical systems

Structured findings and interpretive report / data

COA, analytical report, dataset, or regulatory output

Corrections

Addendum or amended report

Corrected result

Amended report or reinterpretation

Revised result or report

Storage

Tissue, blocks, and slides

Specimens and aliquots

Samples, extracts, libraries, and data

Samples, preparations, materials, and data

Retrieval / Reuse

Review, recut, additional stains or tests

Add-on or repeat testing

Retest, rerun, or reanalysis

Retest, investigation, additional analysis

Disposal

Retention-based tissue or material disposal

Specimen and biohazard disposal

Requirement-based sample disposal

Material-specific and regulatory disposal

Traceability
Patient→case→specimen→cassette→block→slide
Patient→order→specimen→test→result
Sample→derivatives→run→data→finding
Material→preparation→method / run→result

Application-flow translation

The model became 29 application flows across nine stages of work.

Shared stages used a common flow, while variants captured meaningful differences among healthcare, genomics, and scientific work.

Workflow diagram legend

Legend

Conventions used across the workflow diagrams: user actions, system actions, decisions, physical/scientific activities, and status handoffs.

Order entry flow, Healthcare Request submission flow, Scientific

1. Order Entry

  • Order Entry · Healthcare
  • Request / Work Submission · Scientific
Collection flow, shared across domains Scheduled collection flow, shared across domains

2. Collection

  • Collection · Shared Where Applicable
  • Scheduled Collection · Shared Where Applicable
Transport out flow, shared across domains Transport in / shipment receipt flow, shared across domains External result/report receipt flow, shared across domains Specimen/sample receiving flow, all domains

3. Transport & Receiving

  • Transport Out · Shared
  • Transport In / Shipment Receipt · Shared
  • External Result / Report Receipt · Shared
  • Specimen / Sample Receiving · All
Specimen processing flow, Anatomic Pathology Specimen processing flow, Clinical Pathology Sample processing flow, Genomics/Molecular Sample processing flow, Scientific

4. Specimen / Sample Processing

  • Specimen Processing · Anatomic Pathology
  • Specimen Processing · Clinical Pathology
  • Sample Processing · Genomics / Molecular
  • Sample Processing · Scientific
Examination/testing flow, Anatomic Pathology Testing flow, Clinical Pathology Testing flow, Genomics/Molecular Testing/measurement flow, Scientific

5. Examination / Testing

  • Examination / Testing · Anatomic Pathology
  • Testing · Clinical Pathology
  • Testing · Genomics / Molecular
  • Testing / Measurement · Scientific
Diagnosis/interpretation flow, Anatomic Pathology Result validation/interpretation flow, Clinical Pathology Data analysis/interpretation flow, Genomics/Molecular Data analysis/interpretation flow, Scientific

6. Diagnosis / Interpretation & Data Analysis

  • Diagnosis / Interpretation · Anatomic Pathology
  • Result Validation & Interpretation · Clinical Pathology
  • Data Analysis & Interpretation · Genomics / Molecular
  • Data Analysis & Interpretation · Scientific
Report generation, review, and distribution flow, shared across domains Corrected/amended result report flow, shared across domains

7. Reporting

  • Report Generation, Review & Distribution · Shared
  • Corrected / Amended Result or Report · Shared
Material storage flow, shared across domains Material retrieval/movement flow, shared across domains Material disposal flow, shared across domains

8. Storage & Disposal

  • Material Storage · Shared
  • Material Retrieval / Movement · Shared
  • Material Disposal · Shared
Quality control/nonconformity flow, shared across domains Critical result notification flow, Healthcare Reflex testing flow, Healthcare and Genomics Additional/add-on testing flow, shared across domains

9. Quality & Exceptions

  • Quality Control / Nonconformity · Shared
  • Critical Result Notification · Healthcare
  • Reflex Testing · Healthcare / Genomics
  • Additional / Add-On Testing · Shared Where Applicable

Support

The final lens separated platform capabilities from any single role, object, or workflow.

Identity & access

Users, roles, permissions, and authorization.

Configuration

Terminology, workflows, rules, and application behavior.

Integration

Instruments, external systems, applications, and services.

Security

Protection of laboratory and sensitive data.

Quality & compliance

Auditability, quality processes, and regulatory requirements.

System administration

Application maintenance and management.

05 · Outcome

The research gave product teams evidence for deciding where the experience should converge, and where it must branch.

Key discovery

Team members had deep expertise in their own disciplines but limited visibility into how other disciplines worked. As CLS expanded from scientific into healthcare, capabilities such as permissions, configuration, and integrations that had been assumed to be discipline-specific exposed gaps that caused rework.

CLS already had a Microbiology workflow built for scientific labs, and the plan was to reuse it for healthcare. Healthcare stakeholders opposed it, and the first Microbiology designs created conflict because neither group understood the other's requirements. When I took over Microbiology, I went back and finished the shared workflows first so the framework could be applied to it. Without that foundation, those decisions had been adding time to the design schedule. With the shared workflows in place, Microbiology moved forward.

DeliveryThe four-lens framework and 29 application flows were delivered to product and engineering as a discipline-by-discipline starting point for translating the research into CLS interface behavior.
StatusThe framework was used for Clinical Microbiology and Clinical Pathology. At the time, we had not tested broader adoption because no other domain had required it.
ReuseThe framework remained accessible and was structured to extend to additional domains without being rebuilt.

06 · Conclusion

Shared versus specific was decided flow by flow, sometimes step by step.

Testing and interpretation diverge sharply because that is where domain expertise lives. Collection, reporting, and storage converge because the underlying operations (receive it, document it, release it, keep it) do not depend on what "it" is.

The deliverable was not a screen or prototype. It was a way of thinking that made subsequent screen decisions faster and more defensible.

Next case studyGlobal Compliance & Accessibility Framework →