Q-Cyber Magazine
ABDM's federated design: Health data sharing with a consent artefact
The Health Data Management Policy that underpins India's digital health mission requires a federated architecture, voluntary participation, and machine-readable consent before personal health data is collected or shared.

India's national digital health architecture was designed, in its own words, as federated rather than centralised. The Health Data Management Policy that still sits on the Ayushman Bharat Digital Mission website is the public statement of that design, and it has to be read today alongside the DPDP Act and Rules.
Why federation was chosen
The Policy states its purpose plainly. A centralised architecture was not the chosen model for managing digital health data. Federation is intended to support interoperability, technological flexibility and independence, and to protect personal data. Interoperability must comply with the Policy's consent rules. That is the trust design: records can move, but only as the individual has agreed, and they are not, in the architectural principle, poured into a single national clinical store.
The Policy also sets a "security and privacy by design" guiding principle and describes itself as a minimum standard, to be read with applicable law. After 11 August 2023 and the Rules of 14 November 2025, that applicable law includes the DPDP framework. Nothing in the Policy's earlier language displaces those later duties.
Consent is given operational form. A consent artefact is a machine-readable document that specifies the parameters and scope of a data-sharing transaction. A consent manager is the electronic system that obtains that consent. Health Information Providers generate, store and distribute records; Health Information Users may request access only with the data principal's consent. Collection must be limited to data necessary for specified purposes, and data principals are to retain control over how their personal data is collected and further processed.
Exhibit 1
Design choices in the Health Data Management Policy
| Choice | What the Policy states |
|---|---|
| Architecture | Federated, not centralised, as recommended by the National Digital Health Blueprint, 2019 |
| Participation | Voluntary; a Health ID may be issued to an individual who chooses to take part |
| Aadhaar | May be used to verify a Health ID; refusal must not result in denial of a health facility or service |
| Consent instrument | A machine-readable consent artefact defining the parameters and scope of each sharing transaction |
| Consent manager | An electronic system that interacts with the data principal and obtains consent for intended access |
| Providers and users | Health Information Providers generate and hold records; Health Information Users may access them only with consent |
| Collection limit | Personal data collected by a data fiduciary shall be limited to what is necessary for specified purposes |
| Later law | The Policy must be read with applicable law, which now includes the DPDP Act, 2023 and the DPDP Rules, 2025 |
Source: Ministry of Health and Family Welfare, National Digital Health Mission: Health Data Management Policy, official PDF hosted at abdm.gov.in; DPDP dates from Press Information Bureau, 14 November 2025.
Implications
- Keep clinical records with the accountable provider, and treat the national layer as an exchange, not as a default archive.
- Implement consent as an artefact, with purpose, scope and a manager, not as a paper form reused forever.
- Honour refusal of Aadhaar without blocking care, as the Policy requires.
- Overlay DPDP duties — notices, 90-day rights, breach notice, safeguards — on every Health Information Provider and User.
What this means for healthcare
The public design of India's digital health mission is already a privacy design: federated systems, voluntary entry, and consent before share. Hospitals and health-tech firms that implement that design faithfully, and then meet DPDP, will be aligned with both the mission and the statute. Those that assemble parallel, centralised stores of identifiable records will not.


