P1 Identity and profile
P1 is the patient side of M1 Create. M1 is how a hospital system creates an ABHA. P1 is how the patient's own PHR app does it, and how it maintains the account afterwards.
In short
- Every user needs an ABHA address,
username@abdm. Consent, notifications and record sharing all hang off it. - Build both creation paths: by mobile number, and by an existing 14 digit ABHA number.
- All four login routes are mandatory.
- A user can hold several ABHA addresses but only one ABHA number.
What you build
Registration and login, the profile the patient reads and edits, family members they manage on one account, and DigiLocker documents they pull in.
Creating an ABHA address
A person does not need an ABHA number, and does not need Aadhaar, to get an ABHA address here. A mobile number and the OTP sent to it are enough. What that buys is a Self-Declared profile: an address the network can route to, with no KYC behind it and no ABHA number until the person links one later.
| Path | Validated by | Profile details | Result |
|---|---|---|---|
| Mobile number | Mobile OTP | The user types them | Self-Declared, no KYC |
| 14 digit ABHA number | Aadhaar OTP or mobile OTP | Returned by the ABHA system | KYC Verified |
On the mobile number path, first name, year of birth, gender, address, state, district and pin code are mandatory. Middle name, last name, day and month of birth are optional.
After validation on either path, show the ABHA addresses already linked to that mobile number or ABHA number. The user then picks one instead of creating a duplicate.
A Self-Declared profile needs a "Link ABHA number" action. The user enters the 14 digit number and validates by Aadhaar OTP or mobile OTP. Profile details then follow the ABHA number, and the status changes to KYC Verified.
Login
Sign a user in to a PHR application by any of four routes, all of them mandatory.
| Route | Validated by |
|---|---|
| Mobile number | Mobile OTP, then the user picks which linked ABHA address to sign in as |
An address such as name@abdm | Password, mobile OTP or Aadhaar OTP, by auth mode |
The default 14digit@abdm address | Mobile OTP or Aadhaar OTP |
| The 14 digit ABHA number | Mobile OTP or Aadhaar OTP |
Resend OTP unlocks after 60 seconds in every flow. You also need a reset password screen behind login, secure storage of the refresh token, and more than one user profile per install with sign in and sign out.
Profile, card and QR code
| Element | What it holds |
|---|---|
| Profile screen | Editable demographics, marked KYC Verified or Self-Declared |
| ABHA number | Visible only on a KYC Verified profile |
| ABHA address card, a PDF | Photo, full name, ABHA number, ABHA address, QR code, date of birth, gender, mobile number |
| Editable, KYC Verified | Mobile number, with an OTP to the new number, and address |
| Editable, Self-Declared | The same, plus photo, full name, gender and date of birth |
Next
- The calls and base URLs: P1 API reference.
- The next milestone: P2 Linking and records.