The trust engine
Eight things the system checks so you don't have to.
Most software warns you. These are refusals — enforced in the workflow and in the data model, and not switchable off by any clinic, any administrator, or Marg's own support team.
Consent
Captured per purpose, never as a blanket agreement. The patient can withdraw any of it from their own app, immediately.
Identity
Patient identity verified before a teleconsultation starts, and your registration number shown to them throughout.
Prescription rules
Schedule X is hard-blocked on telemedicine with no override, and the permitted drug lists resolve from mode and consult type.
Audit trail
Append-only, with tamper detection. A signed note is never edited — change happens by addendum, and the original stays visible.
Data access
Sensitive identifiers masked by default for every role, including in exports, reports and the API. Unmasking is logged with a reason.
ABDM
ABHA identity, facility and practitioner registries, and FHIR R4 sharing that cannot happen without a logged consent.
Privacy by design
No field anywhere can record fetal sex — not in a template your own clinic builds, not in a search filter, not in an export.
Retention
Configured per record type with the statutory clock tracked, and an erasure request that meets a legal minimum is flagged, never silently resolved.
Try the prescribing rules engine.
Pick how the consultation is happening. What you may prescribe changes — because under the NMC telemedicine guidelines it does.
This is the live rule set, not a diagram of one. Marg maintains it centrally and versions it with an effective date.
How it is put together
Five layers. The compliance core is the bottom one.
Most clinic software bolts compliance on above the clinical record, which is why it can be switched off. Here it sits underneath everything, so consent, audit and the prescribing rules are load-bearing rather than optional.
Move your cursor to rotate · click a layer to isolate it
Straight answers
Questions doctors ask us.
Is my patients' data safe under the DPDP Act?
Consent is captured per purpose rather than as a blanket agreement, and patients can withdraw any of it themselves. Sensitive identifiers are masked by default for every role, including in exports, reports and the API, and any unmasking is logged with a reason. Patient health data, backups and AI processing stay within India, and that is not configurable. There is a published grievance route, a processor register for every vendor that touches patient data, and an append-only audit trail with tamper detection.
How does it handle telemedicine compliance?
Consent type and patient identity are captured before a session can begin, and your registration number is shown to the patient throughout. What you may prescribe resolves from the consultation mode and whether it is a first consult or follow-up, checked against the NMC drug lists — and you see those limits before the consult starts rather than at the point of being blocked. Records are retained for the period your clinic configures, with a three-year minimum.
Keep exploring
Not another clinic management tool. An operating system.
Twenty-two modules, ordered the way a visit actually happens rather than the way a feature list is usually written. Each one is a real working surface, not a checkbox.
Learn more →AI that understands the consultation — not just the words.
Six stages, two of which are hard stops requiring a human. Consent has to be captured before a microphone opens, and the doctor has to accept every drafted section before anything can be signed.
Learn more →We integrate rather than reinvent.
A clinic OS that also tried to be a pharmacy and a lab would be worse at all three. Each capability lives in exactly one place, and the boundary is written into the specification rather than left to whoever builds it.
Learn more →Book a demo
See it against your own clinic's day.
Thirty minutes, in English or Hindi, run against the way you actually see patients — not a scripted tour. Bring your prescription pad and your worst Monday.