Vitaloop is pre-launch. No ABDM milestone certification has been granted to Vitaloop, and Vitaloop has no live hospital deployments at present. Nothing on this website says otherwise. When that changes, this page will say exactly what was granted, when, and for which product version.
1. Status at a glance
| Item | Status |
|---|---|
| ABDM Milestone 1 (M1)Creating and verifying ABHA numbers | Not yet certified. Planned. |
| ABDM Milestone 2 (M2)Acting as a Health Information Provider, sharing records with the patient’s consent | Not yet certified. Planned. |
| ABDM Milestone 3 (M3)Acting as a Health Information User, fetching and showing records with the patient’s consent | Not yet certified. Planned. |
| Health claimsThrough the National Health Claims Exchange (NHCX) | Not started. Planned after M1 to M3. |
| Independent security assessmentWeb application assessment by a CERT-In or STQC empanelled auditor | Not yet carried out. NHA requires it before ABDM production go-live. |
| NABH / QCI ratingRating of the HMIS | Not applicable yet. It is open only to solutions that have completed ABDM integration. |
| Live hospital deployments | None at present. |
| Medical-device licensingMedical Devices Rules, 2017 | Not required for the intended use described in section 6. |
2. What “designed for ABDM” means
We build Vitaloop around ABDM’s published specifications:
- creating, verifying and linking ABHA numbers, with the patient’s informed consent;
- records in HL7 FHIR R4, using the ABDM profiles published by NRCeS;
- sharing and fetching records only through the ABDM consent manager, on the patient’s consent;
- encryption of the health information exchanged over ABDM;
- audit and disclosure logs for every access and release; and
- a consent model that also meets India’s data-protection law.
This describes what we are building to. It is not a certification. The National Health Authority (NHA) grants approval milestone by milestone, after testing.
3. How we will describe certification
- We will state each milestone separately (M1, M2, M3), with the date NHA approved it and the product version it covers.
- We will not describe Vitaloop in general terms as “ABDM certified”, “ABDM compliant” or “NHA approved”.
- We will keep the approval on file and give a copy to hospitals on request.
- If an approval lapses, or does not cover a version or module, we will say so here.
- Certification attaches to the Vitaloop software. A hospital’s own registration in the Health Facility Registry, and its clinicians’ registration in the Healthcare Professionals Registry, are separate and belong to the hospital.
If you see a claim about Vitaloop’s ABDM status anywhere that does not match this page, please tell us at nihar@vitaloop.in.
4. Roles, and what we will commit to
| Party | Role |
|---|---|
| A hospital or clinic that uses Vitaloop | The data fiduciary for its patients’ data. It is the Health Information Provider and User in ABDM and registers itself in the Health Facility Registry. |
| VITALOOP LLP (Vitaloop) | The software provider and data processor for hospital data. A data fiduciary in its own right only for its website, staff-user and prospect data. See the Privacy Policy. |
| The patient | The data principal. Controls sharing through consent, using an ABHA-linked consent manager. |
Software providers that complete the ABDM sandbox sign an undertaking with NHA before they move to production. We expect it to bind us to follow NHA’s Health Data Management Policy, the HIP/HIU guidelines and NHA’s data privacy and security policies; to use data only for the purpose stated in the patient’s consent; not to share it with third parties without consent; to keep the service highly available; and to report cyber security incidents. We are building to those commitments from the start.
5. Laws and standards we build to
- ABDM Health Data Management Policy; ABDM HIP/HIU guidelines; the ABDM minimum viable product guidance for compliant HMIS.
- The ABDM FHIR Implementation Guide (NRCeS) and the EHR Standards for India, 2016.
- Digital Personal Data Protection Act, 2023 and DPDP Rules, 2025.
- Information Technology Act, 2000, section 43A, and the SPDI Rules, 2011, until they are replaced.
- CERT-In Directions of 28 April 2022.
- Health-sector laws that shape hospital record-keeping, such as the PCPNDT Act, the MTP Act and the Clinical Establishments Act, which hospitals must follow and the platform is designed to support.
Listing a law or standard here means we build to it. It does not mean we have been audited or certified against it.
6. Medical-device position
Vitaloop’s clinical suggestion features are designed to show registered medical practitioners reference information and structured documentation prompts, drawn from published clinical guidelines and from the practitioner’s own earlier documentation. They do not diagnose, do not recommend a specific treatment for a specific patient, do not control any device, and take no action on their own. The clinician remains the decision-maker.
On that basis we do not currently treat the software as a medical device under the Medical Devices Rules, 2017. That view is specific to the intended use described here, and we reassess it before releasing any feature that would change it.
7. No endorsement
ABDM, ABHA and NHA are names of the Government of India and its bodies. Vitaloop is an independent company. The National Health Authority has not endorsed, approved or recommended Vitaloop or its products, and nothing on this website should be read as saying so.
8. Where to check, and who to ask
- ABDM: abdm.gov.in. Patient grievances: grievance.abdm.gov.in.
- Our status, or a copy of an approval once we hold one: nihar@vitaloop.in.
- Data protection: Nihar Bholane, Data Protection Officer and Grievance Officer.
Changes to this page
| Date | Change |
|---|---|
| 21 September 2026 | First publication of this page. |