Why Sandbox Testing Exists
ABDM's sandbox environment lets facilities test their entire integration — ABHA verification, HIP registration, consent flows, FHIR formatting — against a safe, non-production version of the network before touching real patient data. Skipping thorough sandbox testing is the most common cause of go-live delays.
The Full Checklist
1. Facility & Provider Registry Setup
- Facility registered and verified on the Health Facility Registry (HFR).
- Relevant doctors/staff registered on the Healthcare Professionals Registry (HPR), where applicable.
2. M1 — ABHA Verification
- New ABHA creation flow tested for patients without an existing ID.
- Existing ABHA verification tested via OTP and ABHA address lookup.
- Graceful fallback tested for patients who decline or fail verification.
3. M2 — HIP Integration
- Encounter/visit records generated correctly in FHIR R4 format.
- Records successfully synced to the sandbox gateway on save.
- Historical record backfill strategy confirmed, if required.
4. M3 — Consent-Based Sharing
- Consent request, approval and revocation flows tested end-to-end.
- Audit log confirms every record access ties back to a valid consent artefact.
- HIU data-request handling tested, if your facility also consumes records.
5. Resilience & Error Handling
- Network failure and retry behaviour tested — especially important for offline-capable deployments.
- Invalid or duplicate ABHA number handling tested.
- Rate-limit and timeout behaviour confirmed against expected patient volumes.
6. Production Credential Issuance
- Production API keys requested and stored securely, separate from sandbox keys.
- Staff trained on any new registration desk workflow changes.
- Monitoring and support escalation path confirmed — see our uptime & support features.
How Long Does This Actually Take?
With a connector handling the technical implementation, most facilities complete this checklist within days rather than months. Publishing the final sandbox configuration itself can take as little as 15 minutes; the milestone certification review is what typically determines total timeline.
What Happens After Go-Live?
Production doesn't mean "set and forget." ABDM specifications evolve, and your connector provider should track those changes for you. At Cortexa, this ongoing maintenance is included, backed by a 99.98% uptime SLA and regional support from our Noida, Delhi, Chennai and Patna offices.
Key Takeaways
- Sandbox testing exists to catch integration issues before they affect real patients.
- M1, M2 and M3 milestones each have specific, checkable criteria.
- Error handling and resilience testing matter as much as the "happy path."
- A connector-backed rollout compresses this timeline from months to days.