In one sentence
ChromaParse turns chromatography PDF reports back into structured data, so QC, CDMO, and R&D labs stop spending hours manually transcribing peak tables.
What it solves
The “standard export” of every major chromatography data system (Empower, OpenLab, Chromeleon, LabSolutions, etc.) is, in practice, a PDF. Which means:
- Downstream consumers (LIMS, ELN, Excel workflows, regulatory submissions) cannot get native structured data without paid vendor APIs or manual transcription
- Manual transcription of a 20-page batch report typically takes 60–90 minutes, with non-trivial error rate and audit-trail gaps
- Cross-vendor, cross-method, cross-site consolidation is nearly impossible to automate due to format fragmentation
ChromaParse uses a template fingerprint library to recognise the layout of each PDF, extracting peak tables, sample metadata, and method headers, and emits Excel / JSON / direct LIMS payloads. Every value links back to its location in the source PDF — meeting GMP audit-trail requirements.
Who it’s for
- Pharma QC labs: heavy daily volume of Empower / OpenLab reports needing a GMP-compliant, auditable data flow
- CDMOs / CROs: cross-customer, cross-method, cross-instrument data normalisation
- Food / third-party testing labs: high-throughput QC moving PDFs into LIMS
- R&D and method validation: ICH Q2 / USP <1225> statistics need structured data; manual entry isn’t practical
What it does not do
- Does not parse raw instrument data (
.dat/.raw) — that’s the chromatography data system’s job, usually under vendor licensing and validation regimes - Does not replace your CDS — we only handle “the report after it’s been exported to PDF”
- Does not modify the report — read-only. The original PDF stays the source of truth.
Next
- Quick start — run a PDF through in 5 minutes
- Supported instruments — check whether your equipment is covered
- Audit trail — how every value traces back to the PDF