菜单
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.
用 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.
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-m4-nhpr |
| description | 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. |
M4 is mostly one-time setup per professional/facility, but HMIS/LMIS products should embed it so new doctors/facilities self-onboard.
check-hpr-exist — if an HPR ID exists, done. Else suggest-ids → create-hpr.Always search-facility FIRST. Exists → link-facility. Not found → onboard-facility → link. (Facility registration itself may require the ABDM portal with document upload and NHA approval — programmatic APIs cover search/onboard/link; set expectations with the user that HFR approval is asynchronous and human-reviewed by NHA.)
OHPL_001 for Eka-managed credentials; BYOA clients use their own credential/bridge id). This is a manual portal step — instruct the user precisely.POST /abdm/v1/hip/onboard (nhpr-abdm/onboarding.md) to register the facility in Eka's system. Only after this can the facility link care contexts (M2)./SDKs/web-sdk/nhpr-sdk/get-started.md. Ask which the client wants for M4 specifically — the console's integration_method is stored per facility, not per milestone, so a client that used raw APIs or a different SDK for an earlier milestone may still want the NHPR SDK here (or vice versa). Don't assume continuity from a prior milestone; ask fresh.{hpr_id, doctor_id} and {hfr_id, facility_id, link_status} against the client's own entities; ask which tables. If using the NHPR Web SDK: pass the console-issued clientId at mount, and capture {hpr_id, hip_id, bridge_id} from the SDK's unmount callback — the SDK does not return the created clinic id any other way. hip_id is required later for M2 linking and Scan & Share.facility.onboarded == true to avoid confusing ABDM-1035 (Invalid HIP ID) errors later.Fetch each endpoint's .md before coding (paths: ../abdm-overview/references/docs-map.md).
HPR exists-path and create-path, HFR search hit/miss, onboard API success, and an M2 link attempt from a freshly onboarded facility.