AZMedAppzTrust centre● All regions operational

What “certified for MedAppz” actually means.

It means a named clinician in the app's own specialty read its hazard log and signed it off. It means the data it says it touches is the data it touches, verified against live traffic. It means when it broke, we published what happened. Certification is a claim we can be held to, not a badge we sell.

Verified appIN · ap-south-1DPDP · ABDM

The five stages an app passes

01Automated checksManifest validity, accessibility scan, dependency vulnerabilities, no undeclared network calls.
02Data disclosureWe run the app against a sandbox and compare real traffic to what it declared. Mismatch fails.
03Clinical safetyA DCB0129-style hazard log reviewed by a clinician in that specialty. Named, not anonymous.
04Region packsResidency proof and per-country evidence. Packs expire; apps must re-attest.
05Staged release5% → 25% → 100%, halted automatically by a safety signal or a crash spike.

Permission disclosure standard

Four rules every listing obeys, enforced by review:1Name the exact resources read and written — not “health data”.2Say why each one is needed, in a sentence a receptionist understands.3State retention per resource, and where it is stored.4List what it never touches, so absence is explicit.New scopes in an update force a re-consent — practices approve the change before the version reaches them. Silent scope creep is the single most common reason we reject an update.

Clinical safety statement

MedAppz is not a clinician and does not practise medicine. What we commit to:Safety-critical UI — allergy flags, doses, critical alerts, data freshness, the patient identity band — is rendered by the platform, not the app, so it looks and behaves the same everywhere.No app may suppress a contraindication, truncate a drug name, or clear a critical alert without a recorded human action.Overrides are always possible and always recorded, with the clinician's name and reason, visible to their practice.Read the full standard (PDF)

Status by region

90-day uptime · updated every minute
ServiceIndiaEUUSUAE
App shell & record● 99.99%● 99.98%● 99.99%● 100%
Alerts & escalation● 99.97%● 99.99%● 99.95%● 100%
Messaging · WhatsApp, SMS◑ 99.4%● 99.9%● 99.9%● 99.9%
Interop bridges● 99.9%● 99.9%◑ 99.6%◌ n/a
Planned maintenanceap-south-1 · database version upgrade, read-only for 6 minutesSun 09 Aug 02:10–02:40 ISTeu-west-1 · certificate rotation, no downtime expectedWed 12 Aug 01:00–01:30 UTCMaintenance never lands during local clinic hours, and read-only windows keep the cached record and the print pack available.

Incident history

■ Safety · RxCanvas renal-dose banner could be scrolled past29 May 2026 · resolved in 9 h
On 13-inch screens the banner scrolled out of view, so a renal-adjusted dose could be signed without the warning visible. No patient harm was reported. We made the banner sticky and blocking, notified 1,090 practices with the affected version, and added a viewport-height case to the review checklist.Full postmortem
▲ Availability · SMS delivery delayed in India11 Jul 2026 · 3 h 40 m
An upstream gateway queued messages without failing. Token calls and appointment reminders were late; no critical clinical alert relies on SMS alone. We now fail over to a second gateway after 90 seconds and show a sync-status chip in QueueFlow.
Security advisory · dependency in an ISV app04 Apr 2026 · no exploitation
A PDF library with a known CVE shipped in two catalog apps. Both were suspended from new installs within 4 hours and patched within 48. Existing tenants were told the same day, with the exact exposure.
Report a safety concernAnyone — clinician, patient, developer, or a stranger — can report. No account needed. Clinical safety reports are triaged within 4 hours, around the clock, by a clinician.safety@medappz.health · +91 80 4718 0000
Responsible disclosureSafe harbour for good-faith research, 90-day coordinated disclosure, and a bounty. Never test against a live tenant — ask us for a sandbox and we will give you one the same day.