メニュー
Test ABDM Connect integrations end-to-end - sandbox setup, per-milestone test suites, webhook testing with tunnels, FHIR validation, and go-live checklists. Use when the user says "test the integration", "run sandbox tests", "verify M1/M2/M3/M4", "is this ready for production", or after any integration work completes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Diagnose and fix ABDM Connect integration failures - error code decoding (ABDM-xxxx, MIS-xxxx, EKA-xxxx), webhook non-delivery, OTP/rate-limit issues, linking failures, consent stuck states, and FHIR rejections. Use when the user reports any ABDM error, a failing test, "webhook not received", "linking stuck", "consent not granted", "data not arriving", or asks to debug the integration.
Integrate ABDM Milestone 2 - care context linking, record discovery, HIP data sharing, webhook handling, and ECDH encryption for pushing FHIR bundles to HIUs. Use when the user says "integrate M2", "link care context", "HIP", "share records", "hip_data_fetch webhook", "discovery", or is connecting a hospital/lab system that generates health records.
Set up Eka ABDM Connect authentication - developer console signup, client_id/client_secret provisioning, access/refresh token lifecycle, long-lived tokens, sharing keys, and BYOA. Use when the user needs credentials, gets 401/403 errors, asks about tokens, or at the start of any milestone integration (auth is always step one).
Integrate ABDM Milestone 1 - ABHA creation (Aadhaar OTP, mobile OTP, face auth), ABHA login, profile management, KYC, ABHA card/QR generation, and the M1 web SDK. Use when the user says "integrate M1", "create ABHA", "ABHA login", "Aadhaar OTP flow", "ABHA card", or is building patient registration for an HIS/LMIS/PHR.
Integrate ABDM Milestone 3 - consent lifecycle (create, list, approve, deny, revoke), auto-approval policies, HIU data fetching, hiu_data_push webhook, and decryption keysets. Use when the user says "integrate M3", "consent request", "HIU", "fetch patient records", "consent artefact", or is building an insurer/referral/analytics/PHR consent feature.
Integrate ABDM Milestone 4 - HPR ID creation for healthcare professionals, HFR facility search/onboarding/linking, software linkage via Eka Bridge, and facility onboarding to Eka. Use when the user says "integrate M4", "HPR", "HFR", "register doctor", "onboard facility", "NHPR", "bridge linkage", or is setting up providers before go-live.
| name | abdm-testing |
| description | Test ABDM Connect integrations end-to-end - sandbox setup, per-milestone test suites, webhook testing with tunnels, FHIR validation, and go-live checklists. Use when the user says "test the integration", "run sandbox tests", "verify M1/M2/M3/M4", "is this ready for production", or after any integration work completes. |
Principle: sandbox-first, automated, evidence-producing. Every integrate-* command ends by running the relevant suite here and showing the user a pass/fail report.
https://api.dev.eka.care with sandbox credentials (do not mix env/creds).ngrok http <port> or cloudflared tunnel), register the URL with Eka, and log every inbound event during tests.abha_created webhook received and patient upserted.hip_data_fetch → encrypted push accepted; idempotency: same webhook delivered twice → one side effect.