Healthcare & Life Sciences

ABDM mandates. DPDP enforcement. Patient data trapped in legacy HMIS and LIMS.

Sammati is the consent and compliance rail that turns both mandates into working pipelines — certified, evidenced, and running in 90 days.

The 2026 reality

ABDM

NHA is progressively mandating ABDM compliance for PMJAY-empanelled hospitals — FHIR R4 or lose empanelment revenue

DPDP

The DPDP Rules are notified and the compliance clock is running: consent, purpose limitation, and erasure are now engineering requirements, not policy paragraphs

Legacy estates

Patient records live in HMIS/LIMS systems that predate every one of these mandates — and can't be replaced overnight

Why a privacy policy isn't compliance

Most healthcare providers 'comply' with DPDP the way most companies comply with anything new: a policy document and hope. But consent is a data engineering problem. Which records were accessed, under which consent, for which purpose? Can you prove erasure actually happened — everywhere, including backups and downstream copies?

When the audit or the breach investigation comes, the policy document is worth nothing; the evidence trail is worth everything. We build the trail.

Sammati (सम्मति) — the consent rail

  • Consent enforced in the pipeline, not promised in a policy: purpose limitation, consent artefacts, and verifiable erasure as code
  • ABDM/FHIR R4 compliance for HMIS and LIMS vendors — certified in 90 days
  • DPDP-ready record systems for hospitals and diagnostic chains, with evidence trails for every access

Sammati enforces consent in the pipeline itself: every data flow carries its consent artefact and purpose; access outside purpose is blocked, not logged-and-hoped; erasure is verifiable, not aspirational. It sits on the same evidence-grade chassis as our banking rail — because we learned provenance discipline in regulated pharma and Tier-1 banking, where every number must carry its evidence.

Pricing: Fixed-fee compliance sprint + monthly rail subscription per facility or per product.

Claims Desk · Suraksha Multispeciality
Submitting via NHCX to 6 insurers · powered by Pravah rails (Datadives) · fictional data
87.4%
First-pass acceptance
6.2 days
Avg TAT
214
Stuck > 7 days
₹2.1 Cr
Receivables at risk
Submitted today
186
auto-built from HIS discharge batch
With insurer
214
TAT clock running
Query raised
41
insurer wants documents
Approved / paid
2743
this month
Rejected → resubmit
118
root-caused by rupee impact
Where the ₹2.1 Cr is stuck — denial reasons by rupee impact (₹ lakh)
fix the top two reasons → recover ~64% of stuck receivables
Tariff / package code mismatch
46.2L
Pre-auth reference missing
31.8L
Policy inactive on admission date
18.4L
FHIR bundle validation failures
14.6L
Duplicates & others
10.9L
Pravah's fix for #1 and #2 is structural, not manual: package-code mappings are proposed once, confirmed by your billing lead, then frozen — and pre-auth waivers auto-attach evidence. Rejection classes get closed, not just cleared.

ABDM Compliance Rail — FHIR R4 in 90 days

We take HMIS/LIMS vendors through FHIR R4 certification in 90 days, and run compliance + incentive-recovery rails for diagnostic chains and hospitals — priced on outcomes.

Who we work with

HMIS/LIMS vendors

FHIR R4 certification in 90 days, then Sammati as your embedded DPDP layer — a selling point to every hospital you pitch.

Diagnostic chains & hospitals

ABDM incentive recovery, DPDP-ready record systems, and evidence trails for every access.

Health-tech & pharma

Consent-clean data pipelines for products and research — the difference between 'we anonymized it' and proving it.

The mandate has a date. Your data doesn't care.

Fixed-fee compliance sprint: know exactly where you stand on ABDM and DPDP in three weeks.