What it covers
The records MeristemLab keeps for a tissue-culture lab, and how they connect.
Record
The records a lab keeps, linked so a question about one is answered from the others.
- Cultures and lineage
- Mother plants
- Media
- Contamination
- Locations
Run
The daily work: labels, scanning, what is due, and the records around orders, stock and equipment.
- Vessel labels and scanning
- What is due
- Orders, customers and production batches
- Inventory and equipment
- Protocols and quality tests
Prove
What matters when someone asks how you know.
- Audit trail
- Roles
- Export
- Your terminology, stages, codes and fields
- Isolation and security
Record
The records a lab keeps, linked so a question about one is answered from the others.
Cultures and lineage
Every culture is a record with a code from your numbering format, a species and variety, a stage, a location, a media batch and a history.
- Lineage from the mother plant through every subculture, with passage numbers, shown as a tree
- Subculture from a culture: the children get the next codes in your format and record the parent, the technician, the media batch and the counts
- Health score, observations and photos on the culture
- Move a culture between locations with the location history kept
- Status for active, contaminated, quarantined, disposed and archived
Mother plants
Where every line starts. Provenance, source, health notes, and every culture taken from the plant.
- Accession code from your format
- Species, variety, source and collection details
- A progeny view of every line taken from the plant
Media
Recipes, stock solutions and prepared batches, with each culture linked to the batch it was started or transferred on.
- Recipes with ingredients, concentrations and notes
- Batches prepared from a recipe with date, volume, pH, sterilisation notes and expiry
- Stock solutions with concentration and expiry
- From a batch, the list of every culture on it
Contamination
Log the event against the culture and the media batch, and see rates over time.
- Type (bacterial, fungal, yeast, other) and severity
- Culture and media batch involved
- Contamination rate over time on the analytics page
- Quarantine status on the culture
Locations
Rooms, cabinets, shelves and positions, each with a code and a QR label, and a list of what is on each.
- Parent and child locations
- A label for each location
- What is here: the cultures and other items at a location
Run
The daily work: labels, scanning, what is due, and the records around orders, stock and equipment.
Vessel labels and scanning
The phone camera reads the labels. Tell us which scanner you use and we will check it.
- Labels for cultures, mother plants, media batches and locations, single or as a sheet
- One scan page that accepts a culture, mother plant, media batch or location label and opens the record
- Works with the phone camera; no scanner hardware needed
What is due
Stage durations set the next subculture date when a culture is created or subcultured, and the dashboard lists what is due and overdue.
- Subculture queue for the next fourteen days
- Overdue in the lab’s time zone
- Tasks with an assignee, a due date and a priority, and a list of your own tasks
Orders, customers and production batches
Customer records, orders with a species, quantity and due date, and production batches linked to the cultures that fill them.
- Customer codes and contact details
- Orders with status and due date
- A planner that works back from an order using your stage durations and a multiplication rate
Inventory and equipment
Chemicals and consumables with quantities and reorder levels; equipment with maintenance and calibration dates.
- Chemicals with supplier, quantity, unit and storage location
- Consumables with reorder level
- Equipment register with maintenance and calibration records
Protocols and quality tests
Written protocols and quality test records kept alongside the cultures they apply to.
- Protocols with steps and notes
- Quality tests against a culture with result and date
Prove
What matters when someone asks how you know.
Audit trail
Changes to cultures, mother plants, customers, orders, contamination events and team membership are written to an append-only log with the person and the time.
- History page on each of those records
- Lab members can read the log; nobody can edit or delete it
Roles
Owner, admin, technician and viewer. Viewers can read and nothing else.
- Invite by email
- The last admin cannot be removed
Export
Any list to CSV, or the whole lab as a ZIP, from Settings, whenever you want it.
- CSV per record type for admins
- A full ZIP of the lab for the owner or an admin
Your terminology, stages, codes and fields
The lab configures the product once and every screen follows.
- Rename any record type; navigation, headings, buttons and messages change with it
- Your own stages, in order, with a colour and a typical duration
- Your numbering format for each record type, assigned on save
- Your own fields on cultures, mother plants, media and the other main records
- Dates in your format and time zone; temperatures and volumes in your units
- Your name, logo and colour in the header and on labels
Isolation and security
Each lab’s data is separated in the database, encrypted in transit and at rest, and backed up automatically. Details on the security page.
- Support access to a lab is limited, used only for a request, and recorded in that lab’s audit log
- Details on the security page
On the roadmap
Next: self-service spreadsheet import, a work list for each person and station, planning that schedules the week’s subcultures and the media they need, loss reports by cause and hood, PDF and Excel reports, costing and invoicing, and offline use on a phone. Ask us where any of these sits.
See it with your own records
Send us a sample of your records and we will load it into a lab for you to look at, and email you a link.