ZopulseDigital solution under Lailen

Zopulse puts your hospital on ABDM.

ABHA at the counter, records shared only on consent, and an integration your existing software vendor can finish in a week. None of the protocol work lands on you.

Talk to us Features
  • ABHA
  • CONSENT ARTEFACTS
  • FHIR R4
  • SCAN & SHARE

  • Hospitals and clinics

    Your staff keep the system they already use. The ABHA step is a QR code on the screen and a confirmation back.

    Arrange a walkthrough →

  • HMIS and software vendors

    Months of protocol work that earns you nothing your customers can see. Add one script tag instead.

    Request sandbox access →

  • NHM and State officials

    Certification status, registry identifiers and our compliance posture, handed over with a name attached.

    Request our profile →

Features

  • ABHA at the counter

    A patient without an ABHA gets one where they are standing, and one who has it is verified in the same breath.

    • Aadhaar OTP and mobile OTP journeys
    • ABHA number and ABHA address
    • Re-verification on a return visit

  • Linking and sharing

    Every record written at your facility becomes a care context the patient can find, and leaves only when they have said so.

    • Care context creation and linking
    • Consent artefacts honoured and expired
    • Gateway callbacks handled our side

  • Scan & Share

    The desk shows a QR. The patient shares their profile from their own app, and the visit lands against the counter that issued it.

    • A separate token per counter
    • Nothing typed, nothing dictated
    • Works on any screen the desk already has

  • SDK and REST API

    Whoever maintains the hospital's software adds one script tag, or skips our JavaScript entirely and calls the API from their own server.

    • Drop-in dialog over your existing screen
    • Server-to-server REST, keys per facility
    • Sandbox credentials on request

Scan & Share

  1. The QR appears

    Your counter screen shows a token. Nothing is typed, and nothing is asked of the patient beyond their own phone.

  2. The patient scans

    They share their ABHA profile from the app they already have, and consent to that sharing there.

  3. The visit is matched

    The profile lands against the right counter and the right facility, as a care context.

  4. Records follow, on consent

    When a record is written, it links to that care context — and leaves only against a consent the patient granted.

For whoever maintains the hospital's software

Simple SDK.

The SDK opens the ABHA dialog over your existing screen and hands back the result. If you would rather not run any of our JavaScript, every one of these steps is a REST call you can make from your own server.

Request sandbox access
Zopulse SDK 
<script src="https://<your-host>/sdk/v1/zopulse.js"></script>
<script>
  Zopulse.open({
    hipId: 'IN1510000104',
    counter: 'registration',
    onShare: (patient) => console.log(patient.abhaAddress),
  });
</script>