--- title: "abdm-integrators-assistant" description: "Agent skills for ABDM integration from the ABDM Developer Portal, compiled from the Catalogue. One skill per module: abdm-m1 to abdm-m4 on the provider side, abdm-p1 to abdm-p3 inside a PHR application, abdm-phr-services" canonical: https://agentpluginsdirectory.com/plugins/abdm-integrators-assistant last-updated: 2026-09-18 --- # abdm-integrators-assistant Agent skills for ABDM integration from the ABDM Developer Portal, compiled from the Catalogue. One skill per module: abdm-m1 to abdm-m4 on the provider side, abdm-p1 to abdm-p3 inside a PHR application, abdm-phr-services for what a PHR app may offer on top, and abdm-fhir for NRCES compliant bundles. Each carries its work as sections that load on demand: scaffold builds the module flow by flow against the sandbox, integrate holds the calls and headers, debug walks a failed call to a named fix and lists every recorded code, test carries the matrix. Every step cites the atom it came from, and nothing has been run against the sandbox. Three commands open the work from the terminal: /abdm-preflight checks what must be true before any call, /abdm-prove-encryption settles the RSA padding before a flow is built on it, and /abdm-decode-error turns a response into the named fix. The abdm-call-debugger agent takes one failing call to a fix and verifies it by the original call succeeding. - Slug: abdm-integrators-assistant - Publisher: ABDM Developer Portal - Repository: https://github.com/nha-in/docs - Manifest: plugins/abdm-integrators-assistant/plugin.json - Version: 0.5.0 - License: MIT - Category (editorial): other - Skills: 9 (abdm-fhir, abdm-m1, abdm-m2, abdm-m3, abdm-m4, abdm-p1, abdm-p2, abdm-p3, abdm-phr-services) - MCP servers: 0 - Stars: 0 - Repository created: 2026-08-25 - Repository last pushed: 2026-09-18 - Publisher type: Organization - Listing: https://agentpluginsdirectory.com/plugins/abdm-integrators-assistant - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What abdm-integrators-assistant does, in the publisher's words The developer portal for India's Ayushman Bharat Digital Mission (ABDM): documentation, an interactive API reference, an MCP server for coding agents, and an AI assistant that answers from the same content a human reads. All four are generated from one source, so they cannot drift apart. Today only the HIE-CM gateway (ABDM V3) is populated. UHI and NHCX have empty scaffolding reserved for later phases. The catalogue is the source of truth: hand-authored knowledge (concepts, step-by-step flows, endpoint guides, error explanations, callbacks, test cases, decisions) plus NHA's own OpenAPI specifications. NHA's files are kept byte-for-byte as published; anything wrong or missing in them is recorded as a dated correction, never silently edited. See catalogue/README.md for how content is organised and catalogue/openapi/CONVENTIONS.md for how the specs are structured. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/nha-in/docs/HEAD/README.md ## Skills - abdm-fhir: Use when producing or checking FHIR for ABDM: building NRCES compliant document bundle generation into a codebase, or auditing the bundles an existing FHIR store already emits. Covers the resource profiles ABDM requires, the Composition rules, and the validator to check against. - abdm-m1: Use when building, debugging or testing ABDM Milestone 1: creating an ABHA number or address, ABHA login, profile management, or the gateway session token. Carries the endpoints, the required headers, the two token rule, the encryption rule, every recorded error code and the M1 test matrix. Also ca… - abdm-m2: Use when building, debugging or testing ABDM Milestone 2: care contexts, HIP initiated linking, discovery, and pushing encrypted health records to a requester. Carries the endpoints, the prerequisites, every recorded error code and the M2 test matrix. Also carries the scaffolding loop that builds i… - abdm-m3: Use when building, debugging or testing ABDM Milestone 3: raising a consent request, tracking its status, reading consent artefacts, and fetching encrypted health records as an HIU. Carries the endpoints, the consent rules, every recorded error code and the M3 test matrix. Also carries the scaffold… - abdm-m4: Use when building, debugging or testing ABDM Milestone 4, the NHPR: creating an HPID, registering a healthcare professional on the HPR, onboarding a facility to the HFR, and linking that facility to its HIP or HIU bridges. Carries the operations NHA has published, the registration order, every reco… - abdm-p1: Use when building, debugging or testing ABDM P1, the patient side of Milestone 1: registration in a PHR application, the four login routes, profile management, the ABHA card, and the family members a user manages. Carries the endpoints, the required headers, every recorded error code and the accoun… - abdm-p2: Use when building, debugging or testing ABDM P2, the patient side of Milestone 2: discovering records held elsewhere, linking care contexts to an ABHA address, and pulling those records into a PHR application. Carries the endpoints, the timing rules the network enforces, every recorded error code a… - abdm-p3: Use when building, debugging or testing ABDM P3, the patient side of Milestone 3: subscriptions, auto approval policies, granting and revoking consent, and fetching the records a grant covers. Carries the endpoints, the notification rules, every recorded error code and the consent rules. - abdm-phr-services: Use when building services a PHR application offers on top of ABDM: teleconsultation, nearby facility search, ambulance booking, blood bank search, scan and pay, PMJAY facility discovery and NHCX coverage lookups. None of it is required to certify as a PHR application. Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.