Assign an owner to every record
Decide which system owns sample identity, plate worklist, raw instrument file, analysis settings, calculated result, disposition, report, and downstream status. Duplicating authority creates reconciliation problems.
An analysis service should return the scientific results together with the records needed to understand them: fingerprints for the source data file and analysis configuration, method and settings versions, software version, units, flags, exclusions, and report identifiers.
Document the data exchanged between systems
Use stable field names and identifiers, explicit units and time zones, defined statuses, format versions, and machine-readable errors. Keep calculated observations separate from human review decisions.
Store the exact data sent and the acknowledgement received. A unique request key prevents duplicate results when delivery is retried after a timeout.
| Area | What to define |
|---|---|
| Identity | Run, sample, method, plate, and result identifiers |
| Versioning | Data format, method, settings, and software versions |
| Source traceability | Fingerprints for the source data file and analysis configuration; exclusions and reasons |
| Delivery | Duplicate prevention, retries, acknowledgement, and reconciliation |
| Linked outputs | Report location, checksum, and structured-result link |
Automated delivery needs more than an export format
CSV and JSON exports can establish the data contract and support reviewed manual workflows. Automated integration also needs secure access, reliable delivery, monitoring, failure handling, change control, and validation appropriate to its intended use.
Define and test those controls for the actual LIMS, network, identifiers, operating procedures, and assay result flow before relying on automatic delivery.
Frequently asked questions
Does Provenarium replace a LIMS?
No. Provenarium is focused on assay analysis and the records behind each result. A LIMS may remain the official source for samples, worklists, inventory, and laboratory status.
What should a first integration deliver?
Start with one clearly defined result flow. Agree on record ownership, identifiers, fields, units, delivery confirmation, duplicate handling, and how the systems will identify and correct missing or mismatched records.