Designed for the Ayushman Bharat Digital Mission ecosystem, subject to NHA approval.
CareLite captures a patient's ABHA number and ABHA address, links it to their hospital UHID after OTP verification through the ABDM gateway, can publish visits and admissions as care contexts so they appear in the patient's own health app, and logs every gateway request and response for NHA review. Live operation depends on the hospital's own registration with the National Health Authority.
ABDM participation is the hospital's own registration, not the software's. A hospital needs to be listed on the Health Facility Registry and hold client credentials from the National Health Authority. Once those exist they are entered against the hospital and the module is switched on. Moving from the ABDM sandbox to production is a setting, not a software change.
If the gateway is unreachable, the credentials are not yet issued, or the patient simply does not want an ABHA, registration and billing carry on exactly as normal. An ABHA can always be recorded by hand and verified later. The UHID remains the hospital's identity for the patient; ABHA sits beside it. A patient who declines ABDM is not a second-class record.
CareLite is ABDM-ready in the sense described above. Formal certification and milestone approval rest with the National Health Authority and with the hospital's own application. Health information exchange beyond care-context linking, and clinical document sharing, belong to the clinical modules that sit outside Phase 1.
CareLite is ABDM-ready: it captures the ABHA number and address, verifies and links an ABHA to the hospital UHID through the ABDM gateway, can publish visits and admissions as care contexts, and logs every gateway transaction. Formal certification and milestone approval rest with the National Health Authority and with the hospital's own application.
Registration on the Health Facility Registry and client credentials issued by the National Health Authority. Once those exist they are entered against the hospital and the module is switched on. Moving from the ABDM sandbox to production is a setting, not a software change.
Nothing changes. Registration and billing carry on exactly as normal, and the UHID remains the hospital's identity for that patient. ABDM is additive and never stands between a patient and treatment.
No. The system refuses it and names the record the ABHA is already linked to, so duplicate patient records are caught rather than created.
Tell us your bed count and we will walk your team from registration to settlement.
Request a demo See pricing