Orchestration LayerFor diagnostic labsDeterministic · Auditable · No LLM in routing path
The infrastructure diagnostic labs plug into. One VCF in, one clinical report out.
PetriDish is not a report vendor — it is the routing layer that sits underneath your existing lab pipeline. Ingest raw VCF / 23andMe / CSV, normalize to a common schema, apply a deterministic rules table to route each variant to the right India-calibrated interpretation module (IndoPGx, IndoG6PD, IndoAutoImmune), and return one standardized clinical report envelope. Your reporting system handles final presentation to the patient.
Auditability contract: given the same input variant list, the router produces the same routing decisions on every call. No LLM call is made in the routing path. See /methods for the data ledger.
Four-layer architecture
LAYER 1
Ingestion & normalization
Any Indian lab's variant output (VCF, PDF-extracted, proprietary CSV) → common HGVS + rsID schema.
LAYER 2
Orchestration router
Deterministic rules table — no LLM. Each variant is gated on gene / rsID and routed to matching module(s).
LAYER 3
Interpretation modules
IndoPGx · IndoG6PD · IndoAutoImmune (live). AyurBridge · EpiOnco (Phase 2 flags).
LAYER 4
Standardized report
One envelope schema. Your reporting system parses it once. No per-lab format variants.
📁
Drop a lab-format file to see the orchestration in action
VCF · 23andMe .txt · CSV · TSV · 25 MB max
Why labs plug in instead of build
India-calibrated by default
97.9% G6PD Orissa · 23% CYP2C19 IM · 18% NUDT15 — frequencies gnomAD misses.
CPIC-graded, not vibe-based
Every dosing action string traces to CPIC 2024/2025. No hallucinated guidance.
Deterministic router
No LLM in the routing path. Regulator-auditable. Reproducible on every call.
One schema, not per-lab formats
Your reporting system parses one envelope. No custom integration per PetriDish module.