zMed in India
Built to India's healthcare standards — not adapted to them.
ABDM in the chart, scheme desks from KYC to claim, statutory registers that survive inspection, and government returns generated from the record itself. Compliance is a property of the platform, not a project after go-live.
ABDM
ABDM is not a portal we open. It's part of the chart we write.
A registered ABHA in zMed means the patient's record is portable to any other ABDM-enrolled facility from day one — under the patient's own consent.
ABHA at the counter
Create or link an ABHA from the same screen that captures demographics — aadhaar, mobile or driving-licence mode, consent OTP included.
Consent artefacts
Every cross-facility fetch recorded with grantor, grantee, scope, validity window and revocation handle — the consent is the audit token.
Facility registry
Every discharge summary, prescription and clinical document linked to an ABHA carries the hospital's HFR ID.
Practitioner registry
Each clinician's HPR ID and council registration validated and stamped on every chart entry and prescription.
Government schemes
Scheme-aware from registration to claim.
KYC at the counter gates everything; the package master attaches rates, pre-auth requirements and documentation at admission; the claim generates from the bill at discharge — every step audit-logged.
PMJAY · Centre
Ayushman Bharat — card verification at the counter, package selection at admission, pre-authorisation in the order, claim generated from the bill.
MJPJAY · Maharashtra
State package codes, empanelment compliance, and the 25% specialty bed reservation tracked continuously against live data.
CGHS · Central
Central Government Health Scheme cards — recognised, packaged, billed and reconciled with the same workflow as PMJAY and MJPJAY.
Empanelment is continuously tracked — bed counts, specialty reservation, dedicated OPD — and flagged before an inspector finds it. For charitable-trust hospitals, the Indigent Patient Fund is a first-class ledger: 10% bed reservation visible in real time, 2% of gross billing accrued monthly, reconciled patient by patient.
Statutory registers
Complete, in order, tamper-evident.
Every register serially numbered, every entry hashed against the previous one, every retention window enforced by the platform.
MLC
Medico-legal cases — brought-by, complaint, police notification, examining clinician. Three-year retention, every entry hashed.
MTP Form III
Authorised practitioner, indication, gestational age, consent — retention per the MTP Act and Rules.
PCPNDT
Radiologist credentials, indication, referring practitioner, findings — centrally inspectable.
BMW Form IV
Daily category-wise biomedical waste generation, segregation, treatment and dispatch.
Government returns
Generated from the record. Submitted with acknowledgement.
Monthly and weekly returns generate from the canonical record — no separate data entry, no spreadsheet reconciliation. Definitions are versioned, submissions carry the portal acknowledgement, and rejected filings re-submit in one action.
Compliance vault
The expiry calendar is the renewal calendar.
Nursing-home registration, fire certification, biomedical-waste authorisation, drug licences, clinician council registrations, NABH accreditation — one vault with renewal calendars, 60/30/15-day alerts, and one-click inspector answers. OPD priority queues (senior · PwD · pregnant) carry audit-grade timestamps, so priority is demonstrated, not just claimed.
Data residency
Indian patient data, on Indian terms.
On-premises (data never leaves the hospital), sovereign India-region cloud, or hybrid — every option DPDP-aligned, the choice is the hospital's.
Deployment topologies in detail — including the edge appliance — explained here →