Agentic RAG · built for India's health stack
The health router that shows its work.
Setu AI answers clinical questions across your EHR, HIS, labs and claims — it verifies consent, redacts PII, and returns a grounded, cited answer. Every step traced. Nothing leaves Azure India.
Show me the full treatment & drug history for Aarav Sharma, ABHA 14‑3344‑2902‑1180. Flag any drug interactions and current adherence.
54M, primary care at Apollo Andheri. Active: T2DM, hypertension, dyslipidemia1. On Metformin SR, Telmisartan+Amlodipine, Atorvastatin and Empagliflozin2. NSTEMI Jul‑2024, treated medically; LVEF 48%3.
The problem
Health data is everywhere.
Trust is the hard part.
One patient's story lives across a dozen systems — ABDM, hospital HIS, lab LIS, imaging PACS, TPA claims. General-purpose AI will answer from any of it: no consent check, no citation, no record of where the answer came from. In a clinical setting, that isn't good enough.
How it answers
One question. Every source. One cited answer.
Setu routes a single question across every system you run — then returns one grounded answer you can check, line by line.
How it works
Every query takes the same six steps.
The router never improvises. Each question is parsed, consent-checked, routed, retrieved, guarded and grounded — in roughly a second, with a signed trace at the end.
Parse intent
Extract entities — ABHA, name, the actual question — before anything is retrieved.
Verify consent
Check the ABDM HIE‑CM consent artefact against the request scope. No valid consent, no data.
Route to sources
router‑v4 scores your indices and picks the top candidates for this exact intent.
Retrieve & rank
Hybrid search across FHIR, HIS and Rx; rerank down to the eight most relevant chunks.
Guardrail & purpose
Redact 23 PII entity types and enforce the declared DPDP §8 purpose before the LLM sees a thing.
Compose & ground
Stream a cited answer. Anything below grounding score 0.62 is never rendered.
Grounded, not guessed
If it isn't in your sources, Setu won't say it.
Every claim links back to where it came from — a FHIR resource, an HIS encounter, a cathlab PDF, an ICMR guideline. Below a grounding score of 0.62, it doesn't render at all. That's how a clinician knows the answer is real, not plausible.
See grounding in a live traceBuilt for India
Native to the country's health stack.
Setu speaks the systems and rules Indian healthcare already runs on — and keeps data in the country.
One grounded answer — in 15+ languages, Indian and international
Compliance posture
Compliant by construction, not by promise.
DPDP, ABDM and CERT‑In aren't a checklist bolted on afterward — they're how each query is shaped. Here's what's passing, with the controls behind it.
DPDP Act 2023
Every query carries a declared purpose mapped to the §8 schedule.
- Lawful purpose enforced
- Granular ABDM consent
- 23 PII types redacted
ABDM / NDHM
HIE‑CM certified on FHIR R4, with the milestone tracker green through M4.
- HFR + HPR linkage
- ABHA + consent
- Care‑context share
CERT‑In
Six-hour incident reporting SLA wired to a SOAR bridge. Zero open incidents.
- Last drill passed
- NTP sync ±4ms
- JIT reporting hooks
Data residency
All retrieval served from Azure India. No cross-border egress, ever.
- AES‑256 at rest
- TLS 1.3 in transit
- MeitY / STQC CSP
Audit & trace
Every query trace is cryptographically signed and written to a WORM bucket.
- Read-only replay
- Signed lineage
- 7‑year retention
Consent revocation
Consent pulled via ABDM is honoured across indices in under thirty seconds.
- Purpose limitation
- Data minimisation
- Storage TTL 180d
Connectors · across your stack
Connects to the systems you already run.
FHIR-normalised, ACL-aware, change-data-capture where it counts — across EHR, hospital systems, labs, imaging, claims and public health. Add any system with an API.
One router, three surfaces
Built for the people who run the floor.
Doctor
Treatment history, drug interactions and adherence — scoped to their own patients, grounded in real records, ready at the point of care.
Admin
OPD load forecasts, claim-denial root cause, network coverage — the operational questions that keep a hospital moving.
DPO
Live DPDP posture, consent revocations, data-principal requests and a signed audit ledger — proof, not assurances.
indexed
searchable
latency
grounded ≥0.62
egress events
FAQ
Straight answers for buyers.
The questions a hospital, insurer or health-tech team actually asks.
Does it store our patient data?
Setu is designed to run in your environment on Azure, India region, and was built and demonstrated on synthetic / de-identified data — never real patient PHI.
How do we know an answer is right?
Every claim is cited to its source passage and scored for faithfulness. When the evidence is thin, Setu flags the answer or defers to a clinician instead of guessing.
Can it handle our messy files?
Yes — scanned PDFs, borderless and nested-header tables, charts and prescriptions, across 26 formats.
What about counting and reporting questions?
"How many were denied? Which department is highest?" runs through a structured-analytics lane that computes exact figures over your tabular data — not a language-model estimate.
Which languages does it support?
Hindi and many Indian languages, plus English and other international languages — the same grounded answer, in the user's words.
Is it a finished product?
Setu AI is in build and demonstrated on synthetic data; we're setting up pilots. Talk to us about yours.
Bring AI to your health data — safely
See Setu route a real query on your stack.
A 30-minute walkthrough on your sources, your roles, your compliance posture. Built in India, for India's health stack.
or email kumar.j5098@zohomail.in