No re-photographing what's digital
A discharge summary a hospital already issued digitally can be pulled directly into your timeline, rather than photographed a second time from a paper printout of the same record.
Coming soonHealth-record Organization Assistant
Link records via ABHA health ID
The person can pull in records that a hospital, lab, or clinic already issued digitally through India's national health ID system, instead of manually photographing every paper copy.
Works with
What it does
How Doctor handles this
The user creates or links their existing ABHA (Ayushman Bharat Health Account) address inside Doctor, and consents, through the government's own HIE-CM consent flow, to import records that participating facilities (Health Information Providers) have issued against that ABHA. Doctor acts strictly as a Health Information User (HIU) requesting records with the user's explicit, logged consent for each request.
A hospital's own system already issued a discharge summary digitally through India's national health ID framework, but the family still photographs the paper printout by hand because nobody's shown them a way to pull the digital version straight from where it was originally issued in the first place.
ABHA linking connects a person's Ayushman Bharat Health Account address inside Doctor, and every record fetched afterwards goes through the government's own consent flow — a fresh, individually logged permission for each specific request, never a one-time blanket approval covering everything. Doctor acts strictly as a Health Information User requesting records that already exist at the hospital, lab, or clinic that issued them; it never becomes a source of clinical data itself in any way.
Where link records via abha health id happens
Doctor runs this directly on the platforms your customers already use — no separate app for them to install.
- Google Drive
- Adobe Acrobat Reader
- Google Calendar
How it works
Step by step
- 01
Create or link your ABHA address
Set up a new ABHA health ID or link an existing one inside Doctor, connecting your identity to India's national digital health framework for the first time, or simply continuing to use it as before.
- 02
Consent to each specific fetch
When a participating facility has a record to offer, the government's own consent-manager flow asks for your explicit approval for that specific request — never a standing permission that covers everything, forever, in one go.
- 03
The record arrives from its source
Once consent is fully granted, the health record is retrieved directly from the hospital, lab, or clinic that issued it originally, in the standard exchange format India's national health data framework clearly defines for use.
- 04
It's tagged and filed automatically
A record pulled in this particular way carries a clear 'source: ABDM' tag on the timeline, so you always know whether a document came from your own upload or an external, consented fetch instead of that.
Why it matters
What you get out of it
Consent for every fetch
Each request to pull a record requires its own explicit approval through the government's consent system, so nothing arrives without your knowledge and agreement at that specific moment in time.
Clear where records come from
A document pulled via ABHA carries a visible tag showing it came from an external source, so it's never confused with something the family uploaded themselves directly.
The detail
What to know before you rely on it
This capability works entirely inside India's federated health data model, in which no central body — including Doctor — ever stores medical records on the ecosystem's behalf. A person's ABHA address simply threads together consent-gated links to records that stay held at whichever facility originally issued them, and Doctor's role is to request access to those records, with the person's fresh, explicit, individually logged permission, exactly as India's Ayushman Bharat Digital Mission requires of any registered Health Information User.
Consent here is deliberately scoped narrowly rather than broadly. Each artefact of consent covers a specific facility, a specific set of data categories, and a specific time window — it is never translated inside Doctor's own interface into a single 'always allow' toggle, because doing so would quietly undermine the purpose-limitation the entire government framework is built around. A family managing a father's ongoing care might request records from the same hospital several times over a year, and each request goes through its own consent step.
Becoming a certified Health Information User carries real operational obligations that exist specifically to protect the person whose records are being requested: Doctor never retains ABDM-sourced data beyond the consented purpose or duration, and every record pulled this way carries a provenance tag making clear it came from an external fetch rather than the family's own upload. A failed or partial conversion from the exchange format into Doctor's own filing system is treated as a data-integrity risk worth guarding against carefully.
Industry use cases
Where this earns its keep
1 industries where Doctor applies this directly.
More from Doctor
Everything else it handles
Build a chronological health timeline
The person sees every report, prescription, and visit they've uploaded laid out in date order instead of as a loose pile of files.
Learn moreCapture records from a photo
The person adds a paper prescription or report to their record in seconds by taking a photo, instead of typing it in by hand.
Learn moreManage records for family members
One person — often a caregiver — can organize records for their parents, children, or in-laws separately, without mixing up whose test is whose.
Learn moreGrant and revoke caregiver access
A person managing an elderly parent's records can invite a sibling to view or help, and can cut off that access instantly if circumstances change.
Learn moreExtract structured data from lab reports
The person can see a lab report's parameter names, values, units, and reference ranges as clean text instead of squinting at a scanned PDF.
Learn moreChart the same test over time
The person can see how one specific lab value has moved across multiple visits without manually flipping between old reports.
Learn moreQuestions
Straight answers.
Does linking my ABHA address mean Doctor now stores my medical records centrally?
No — India's ABDM framework is deliberately built so no central system, including Doctor, ever stores medical records on behalf of the wider ecosystem itself, at any point. Records stay held at the hospital, lab, or clinic that originally issued them, and Doctor only requests access to specific ones with your fresh, explicit consent for each individual request that gets made.
Do I have to approve every single record fetch, or can I set it to allow everything automatically?
Every fetch requires its own separate consent through the government's own consent-manager flow — there's no 'always allow' setting inside Doctor, by deliberate design, since a blanket approval would go against the purpose-limitation the national framework is carefully built around. This means slightly more taps for you, but it also means nothing is pulled about you or a family member without a specific, logged approval each time it happens.
How do I know if a document in my timeline came from my own upload or from an ABHA fetch?
Every record pulled through ABHA carries a visible 'source: ABDM' tag on the timeline, distinguishing it clearly from anything the family uploaded or captured by photo themselves directly at any point. This tag stays permanently attached to that record going forward, so its actual origin is never left ambiguous or unclear to anyone looking at it later on, however much time has passed.
If I link my father's ABHA address to manage his records, does that give me any say over his treatment?
No — linking an ABHA address only affects which records can be requested and filed on his behalf; it has absolutely nothing to do with treatment decisions, which remain entirely between your father and his own treating clinicians going forward. This capability is purely about record access and organisation, not about any role whatsoever in his actual care or its direction.
The rest of your stack
It plugs into what you already run.
Doctor connects to your tools
No rip-and-replace — link records via abha health id works alongside the systems already running your business.
- Dropbox
- Google Sheets
- Google Forms
- Gmail
- Telegram
Coming soon