Does UNMIRI replace a lab informatics platform like Velsera CGW?

No. UNMIRI is a vendor-report ingestion API, not a lab workbench. If you run the assay yourself and need pathologist sign-out, KB-driven annotation, and report generation in one tool, you want a lab platform. UNMIRI is for the vendor downstream that ingests your finished report.

Why is the schema open?

Buyers can verify the integration contract before signing. Closed-schema vendors require an NDA before sharing the data model, which lengthens evaluation cycles by weeks and costs deals. UNMIRI's CC-BY 4.0 schema lets a buyer's engineering team inspect and benchmark the contract over a weekend. The schema decisions (AMP/ASCO/CAP tiers, identifier-only citations, evidence.externalLevels extension hook) are the value, and we made them in the open.

Does UNMIRI cover the same vendors Velsera does?

Different angle. Velsera supports the assay-running lab. UNMIRI supports the vendor downstream of multiple labs. UNMIRI's coverage table at /coverage shows production-maturity parsers for Foundation Medicine, Tempus, Caris, Guardant, Natera, NeoGenomics, Strata Oncology, Personalis, OmniSeq, ARUP, LabCorp, Precipio, Veracyte, Exact Sciences, and Myriad. Some labs (Guardant) are flagged as exploratory in our table — we say that honestly.

What happens if our customer is also a Velsera customer?

Common. UNMIRI sits upstream of the customer's reporting workflow — we ingest a finished vendor report and normalize it. Whether the report came from a Velsera-powered lab or a different lab platform doesn't change UNMIRI's job. Customers can use both products without conflict.

Velsera (PierianDx) alternative · for EHR vendors, digital pathology platforms, oncology decision support tools

Velsera alternative: cross-vendor NGS report ingestion as an API, with an open schema

UNMIRI · See the NGS Interpretation API

Velsera was formed in 2023 from the merger of Seven Bridges, PierianDx, and UgenTec under Summa Equity. The flagship is Clinical Genomics Workspace (CGW): an end-to-end tertiary-analysis and reporting platform sold to clinical labs running assays. Strong at lab workflow — secondary-analysis hooks, variant calling, KB-driven annotation, pathologist sign-out UI, EHR push.

UNMIRI Engine 1 solves a different problem for a different buyer. Vendors — EHR companies, digital pathology platforms, oncology decision support tools — don't run the assay. They receive someone else's vendor PDF or XML and need to normalize it into structured data their software can use. UNMIRI is the API for that. The output schema is open on GitHub.

At a glance

Dimension	Velsera (PierianDx)	UNMIRI
Primary buyer	Clinical labs running the assay (academic medical centers, cancer centers, commercial reference labs, assay developers)	Vendors that ingest other labs' reports: EHRs (Epic, Athena, eCW), digital pathology (Paige, PathAI, Proscia, Indica), oncology CDS (Flatiron, Navigating Cancer)
Primary verb	Run a tertiary analysis on raw sequence + report it	Ingest a vendor's finished report (PDF/XML) and normalize it to FHIR Genomics
Output schema	Proprietary internal model + EHR push (HL7/FHIR exports available)	Open FHIR Genomics R4 schema published on GitHub (CC-BY 4.0)
Knowledge base	Velsera-curated proprietary KB (also powers the Illumina TSO Comprehensive IVD)	Open sources only: CIViC (CC0), ClinVar, ClinicalTrials.gov, openFDA, CPIC. Customers verify outputs on the source's own site.
Integration model	Workbench-first, with EHR pushes as an export	API-first. Vendors don't want a UI; they want JSON.
Compliance	Established lab IT integrations, FDA approvals on partnered assays	AWS BAA active 2026-05-09; Microsoft Online Services HIPAA BAA active. SOC-2 on roadmap.
Pricing	Enterprise sales, implementation-heavy, custom	$30-150K mid-market ACV / $250-750K top-tier (Engine 1 only)

Different buyer, different problem

CGW is a workbench. UNMIRI is an API. Most buyers shopping for "NGS interpretation" land on lab-platform vendors first because that's the established category. If you're a vendor (EHR, digital pathology, oncology CDS) who needs to ingest reports from many different labs without owning any of them, the lab-platform shape isn't the right tool. UNMIRI's API-first, vendor-agnostic, open-schema design is built for that buyer specifically.

The honest version: many serious clinical-genomics product teams might use both kinds of system in different parts of their stack. UNMIRI for vendor-report ingestion + EHR-grade FHIR output; a workbench platform for any in-house lab work. The evidence.externalLevelsmap in UNMIRI's schema is the documented extension hook for licensed proprietary KBs to plug in under their own licensing terms.

When Velsera (PierianDx) is the right pick

You are a clinical lab running the assay yourself and you need an end-to-end secondary-to-tertiary analysis platform.
You want a single workbench with pathologist sign-out UI, KB-driven annotation, and report generation in one tool.
You're an assay developer (e.g., partnering with Illumina or another instrument vendor) and need a curated KB-driven reporting layer that customers will trust under regulatory submission.
Your team is set up for enterprise procurement on a deeply-integrated lab informatics platform.

When UNMIRI is the right pick

You're a software vendor that doesn't run the assay — you receive vendor reports and need to normalize them to your data model.
You want to inspect the integration contract before signing anything. The schema is on GitHub at unmirihealth/unmiri-ngs-fhir-schema.
You need FHIR Genomics R4 output for downstream EHR integration, not a proprietary model.
You value open evidence sources your customers can verify (CIViC, ClinVar, openFDA) over closed proprietary curation.
Your customers' compliance teams will ask why a lab competitor's KB is sitting in your data path. Open sources side-step that question.

Frequently asked questions

Does UNMIRI replace a lab informatics platform like Velsera CGW?: No. UNMIRI is a vendor-report ingestion API, not a lab workbench. If you run the assay yourself and need pathologist sign-out, KB-driven annotation, and report generation in one tool, you want a lab platform. UNMIRI is for the vendor downstream that ingests your finished report.
Why is the schema open?: Buyers can verify the integration contract before signing. Closed-schema vendors require an NDA before sharing the data model, which lengthens evaluation cycles by weeks and costs deals. UNMIRI's CC-BY 4.0 schema lets a buyer's engineering team inspect and benchmark the contract over a weekend. The schema decisions (AMP/ASCO/CAP tiers, identifier-only citations, evidence.externalLevels extension hook) are the value, and we made them in the open.
Does UNMIRI cover the same vendors Velsera does?: Different angle. Velsera supports the assay-running lab. UNMIRI supports the vendor downstream of multiple labs. UNMIRI's coverage table at /coverage shows production-maturity parsers for Foundation Medicine, Tempus, Caris, Guardant, Natera, NeoGenomics, Strata Oncology, Personalis, OmniSeq, ARUP, LabCorp, Precipio, Veracyte, Exact Sciences, and Myriad. Some labs (Guardant) are flagged as exploratory in our table — we say that honestly.
What happens if our customer is also a Velsera customer?: Common. UNMIRI sits upstream of the customer's reporting workflow — we ingest a finished vendor report and normalize it. Whether the report came from a Velsera-powered lab or a different lab platform doesn't change UNMIRI's job. Customers can use both products without conflict.

Become a design partner

We're actively recruiting design partners for Engine 1. Inspect the schema on GitHub, run a sample report through the API, then talk to us about your specific vendor mix.

See the NGS Interpretation API →Get pricing