Engine 1 · NGS Interpretation API
Inspect the parse + tier API
Browse the request and response shape for vendor parsing, evidence join, and FHIR Genomics output.
Open the API explorer →Demo
Take the tour
Five stops, about ten minutes, no signup. Each step links to a live page on the demo. The disclaimer below is the canonical one. It appears on every result surface.
The synthetic demos parse vendor fixtures server-side. None of the source vendor PDFs are mirrored here. The fully-rendered example output lives on the sample report page; everything else on this tour is the API returning structured data.
Educational use only. Synthetic data, demonstration only. Not a medical device. Not for unsupervised clinical decision-making.
- 1
Watch the parser run on a vendor sample
Foundation Medicine, Tempus, and Caris fixtures. Each runs through the parser server-side and returns gene calls, biomarker values, FDA-approved drug flags, and trial NCT IDs with the raw source-text quote intact.
Why this matters: The parser stage is where cross-vendor normalization happens. Different report layouts; identical output schema.
Open the sample showcase → - 2
See cross-vendor parsing side by side
Pick two synthetic fixtures and the page diffs them at the gene, biomarker-type, drug, and trial level. Common findings highlighted; vendor-only findings flagged.
Why this matters: Cross-vendor normalization is the core promise of Engine 1. The diff shows it concretely.
Compare two vendors → - 3
Look up the evidence join
CIViC evidence, ClinVar significance, openFDA-approved drugs, ClinicalTrials.gov NCT IDs, and CPIC guidance joined on (gene, variant, tumor type). Returns the AMP/ASCO/CAP tier with full rationale and the Li MM et al. citation.
Why this matters: This is the step that turns a parsed variant into actionable evidence with PMIDs you can verify.
Try the lookup → - 4
Render the evidence as a CDS surface
Therapy matches, resistance warnings, PGx dosing, trial recommendations, and evidence-gap callouts derived deterministically from the lookup output. Every card carries its CIViC, openFDA, ClinicalTrials.gov, or CPIC citation.
Why this matters: Engine 2 in production adds rule-engine logic for contraindications and combined-predicate triggers; this view shows the deterministic core.
See the recommendations → - 5
Browse the publications behind the evidence
CIViC-curated PubMed citations grouped by PMID and ranked by evidence-item count and CIViC level. Click any PMID to open the paper.
Why this matters: Closes the loop between the variant, the evidence, and the underlying literature.
Open the literature view →
Done with the tour?
The honest matrix of what we extract today and what we don't yet is on the vendor coverage matrix. The interactive API reference is at the API explorer. For pilot conversations, email partnerships@unmiri.com.
Now run it live
The tour above runs against synthetic public fixtures. When you're ready to evaluate the actual engine for your workflow, here's the entry point per product surface.
Engine 2 · Genomics-aware CDS
Look at the CDS endpoints
Same API explorer, CDS endpoints documented inline. Five reasoning categories. FDA CDS-exempt.
Open the API explorer →Engine 3 · Literature Intelligence
Start a 14-day trial
Variant-aware literature feed and KOL ranking for precision-oncology medical affairs. No credit card.
Create a med-affairs account →Engine 4 · Pathologist Tool
Request beta access
Free for individual clinical use. Institutional email required. Closed beta opens Q4 2026.
Join the pathologist beta →