EngagementLive · in the productPatient-facing

HealthWallet

The records this clinic holds, shared by the patient, with a log of every time it was opened.

Get HealthWallet Open the appAvailable nowHow pricing works →

What it is

A share the patient asks for: which slice of their record — the summary, prescriptions, reports, bills or all of it — goes to which named person or organisation, for a stated purpose, until a date they choose. Every share is backed by a real consent record on the same engine the rest of the product uses, is revocable at the desk, and carries a log of every time it was actually opened, which the patient can see over their own portal link. The same share can also be served as FHIR R4 through FHIRBridge, which carries the patient’s name, sex and birth date and nothing more identifying than the plain view does — and states on the exchange what FHIR could not carry, the allergy list among it. The wallet stores no clinical data of its own — the records stay in the schemas that own them. It also records the ABHA address a patient is known by, once, as a note.

Who uses it: Built for: Every specialty
Reads: This clinic’s own patient record, consents
Writes: Share grants, consent records, an access log
Never: It does not aggregate records from other hospitals, and it is not connected to ABDM: recording an ABHA address writes down what the patient told the desk after linking it on their own app, and nothing is fetched from or sent to the national network.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

How it works

Find the patient and open a walletSearch by name or MRN under Wallet, open the patient and Open a wallet.
Record a shareUnder Shares: what — summary, prescriptions, lab reports, bills or everything — who it is shared with, why, and until when. Record share writes a consent record behind it. The database refuses a share ending more than 180 days out or in the past, and one without a purpose.
Preview, and see it countedPreview serves what the share shows and adds a row to the access log, which the patient can read over their own portal link.
Cancel itCancel withdraws the consent with it. A cancelled or expired share serves nothing from that moment.
Record the ABHA addressOnce, as a note with how the desk knows it, kept masked. Nothing is sent to or fetched from ABDM.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It never widens who can see data without the patient asking, and a revoked share serves nothing from the moment it is revoked.

AI in HealthWallet

AskQuestions about what is on screen — “What needs attention in HealthWallet today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

HealthWallet — Health Wallet — Patients carry their own records on ABHA — 01Health Wallet — Patients carry their own records on ABHACaptured from the running demo clinic

01Health Wallet — Patients carry their own records on ABHACaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 2

ConsentVault Patient Registry

Hands to · 2

ABDMLink ConsentVault

See the whole clinic →

Questions clinics ask

What does HealthWallet do?

The records this clinic holds, shared by the patient, with a log of every time it was opened. A share the patient asks for: which slice of their record — the summary, prescriptions, reports, bills or all of it — goes to which named person or organisation, for a stated purpose, until a date they choose. Every share is backed by a real consent record on the same engine the rest of the product uses, is revocable at the desk, and carries a log of every time it was actually opened, which the patient can see over their own portal link. The same share can also be served as FHIR R4 through FHIRBridge, which carries the patient’s name, sex and birth date and nothing more identifying than the plain view does — and states on the exchange what FHIR could not carry, the allergy list among it. The wallet stores no clinical data of its own — the records stay in the schemas that own them. It also records the ABHA address a patient is known by, once, as a note.

What data does HealthWallet read and write?

HealthWallet reads this clinic’s own patient record, consents and writes share grants, consent records, an access log. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does HealthWallet deliberately not do?

It does not aggregate records from other hospitals, and it is not connected to ABDM: recording an ABHA address writes down what the patient told the desk after linking it on their own app, and nothing is fetched from or sent to the national network. It never widens who can see data without the patient asking, and a revoked share serves nothing from the moment it is revoked.

What happens to our data if we uninstall HealthWallet?

Every record stays; only the workflow leaves.

Is HealthWallet available today?

Yes — HealthWallet is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see HealthWallet running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Engagement

All 106 →