菜单
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.
用 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 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.
Understand ABDM (Ayushman Bharat Digital Mission), its registries (ABHA, HPR, HFR), roles (HIP/HIU/PHR), the four certification milestones M1-M4, and how Eka's ABDM Connect APIs map to them. Use when the user asks "what is ABDM", "what is ABHA/HPR/HFR", "which milestone do I need", "HIP vs HIU", "how does ABDM certification work", or at the start of any ABDM integration to decide scope.
| name | abdm-m1-abha |
| description | 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. |
Prereq: working auth (see abdm-auth skill). All M1 flows require an access token from the Session/Login API; the oid (Eka User ID) obtained is reused across all downstream flows.
@eka-care/abha, mounted via window.initAbhaApp(...). Exact mount contract, method/flow enums, theme shape, and native-bridge hooks: references/web-sdk.md. Also fetch /SDKs/web-sdk/abha-sdk/get-started.md for current docs.Ask the user which fits their HIS frontend. For branding (colours/logo/theme), check for a client config file first (abdm-auth/references/client-config.md) before asking piecemeal branding questions — also confirm embed point and language.
enrollment/aadhaar/.enrollment/mobile/{init,verify,resend,create}.md.enrollment/face-auth/* — init → capture (async, poll) → verify → create.skip_state = abha_end (done).skip_state = abha_create → Auto-Login API → abha_end.abha_end.Key state machine fact: on verify, inspect skip_state. If abha_create and len(abha_profiles) > 0, call Auto-Login to enter an existing ABHA rather than creating a duplicate.
profile/details/*), KYC upgrade (profile/kyc/*), ABHA card + QR (profile/cards/*), search (profile/search/search.md).does-health-id-exist, suggest-abha-address, pincode-details.abha.abha_created fires on successful creation — wire it to create/update the patient record in the client's HIS.abha/: token-authed proxy endpoints for each enabled flow (never expose Eka creds to the browser), txn-state handling (txn_id passthrough), webhook receiver for abha_created.{abha_address, abha_number, oid} onto the client's patient entity. Ask the user which table/model stores patients and add the columns/migration.Before writing any endpoint call, fetch its .md doc page for the exact schema (paths in ../abdm-overview/references/docs-map.md).
Sandbox happy paths: Aadhaar create, mobile create, each enabled login, duplicate-ABHA path (auto-login), wrong OTP (MIS-1013), OTP rate-limit (ABDM-1100).