Skip to content
YellowParrot ABDM DevKit
examples/python, mock environment
Consent request to approve:
  Request consent from asha.rao1@sbx for Care Management
  Records: Prescription, DiagnosticReport
Waiting for the simulated patient to respond...
Granted by HIP-DEMO-01
Fetch to approve:
  Fetch health records from HIP-DEMO-01
Waiting for the encrypted records...
Received Prescription (1691 bytes,
  decrypted by the DevKit)

YellowParrot ABDM DevKit

Build, simulate and validate ABDM integrations without starting with live credentials.
QuickstartView on GitHub

ABDM is India’s national system for sharing a patient’s health records between hospitals, clinics and labs, only with the patient’s consent. Building software for it is hard to start: you need test credentials, a public server, special encryption and records in a specific format before anything works.

The DevKit gives you all of that in one free, open-source toolkit, with a practice version of ABDM built in, so you can see and test the whole flow on your own computer in minutes. New to ABDM? Read ABDM in plain words first.

Start here

Section titled “Start here”
Show me how it worksClick through a consent request and a record fetch in your browser, and see every message sent and received. Nothing to install.
I'm new to ABDMABHA, consent, hospitals and clinics: the whole system explained in plain words.
I use an AI assistantAsk Claude to request consent and fetch records, with you confirming each step.
I'm building an appCall the REST API from Python, Java, PHP or anything that speaks HTTP.

What you get

Section titled “What you get”

Practice ABDM, built in

A stand-in for ABDM and a hospital, with made-up patients. Try approvals, refusals, expiry, lost and repeated messages, and encrypted record transfer, all offline.

Consent done right

A person approves every request before it is sent. The DevKit refuses anything outside what the patient agreed to, and deletes records when consent ends.

ABDM's encryption, ready to use

Records are encrypted exactly the way ABDM requires, checked against ABDM’s published reference examples.

Works with your stack

TypeScript libraries, a REST API for any language, and tools for AI assistants such as Claude.

How it fits together

Section titled “How it fits together”
AI assistantClaude, other MCP clientsYour app, any languageover the REST APIYour TypeScript codeimports the packagesDevKit workflowsYour user approves every request · the patient's consent is checked at every step· each user sees only their own work · every action is logged without patient detailsConsent ruleswho may see whatEncryptionABDM's schemeHealth recordsbuild and checkABDM clientV2 and V3 APIsMock ABDMbuilt in, synthetic dataABDM sandboxyour own test credentialsCertified servicefor production use
Three ways in, one set of rules, three places to connect. Mock ABDM (highlighted) is the default and needs nothing.
Where it connects You need Status
Practice ABDM (mock) Nothing Works today
ABDM’s test system (sandbox) Your own sandbox account from NHA Being built
Real ABDM (production) A service certified by NHA Planned

Using real patient data always requires your own registration and certification with NHA. The DevKit helps you build and test; it does not replace that.

Built by YellowParrot Technologies · Open source under Apache-2.0