HealthPass · beckn protocol · October 2026

HealthPass gives every patient a record. Beckn connects that record to every clinic, lab and pharmacy.

HealthPass is a health record that belongs to the patient and opens inside WhatsApp. Beckn is an open, free-to-use set of rules (a protocol) that lets clinics, labs, pharmacies and patient apps find each other, agree on a service and send each other results, with no single company or ministry in the middle. On a beckn network, HealthPass can work with any clinic, lab or pharmacy on the network, not only the ones it has connected to one at a time.

Today a patient’s records are split across the places she visits

Take Thandi, a 34-year-old in Soweto being treated for high blood pressure. Over a year she sees a public clinic and a private doctor, has blood tests at a lab and collects medicine from a pharmacy. Her history ends up in four places that don’t talk to each other: the clinic’s paper file, the doctor’s computer system, a lab result sent to her by SMS, and a photo of a prescription on her phone. Each new provider starts from nothing. Tests get repeated, and no one has the full list of what she takes.

Today: no shared record

Four providers each hold a piece of the record, and none are connected Thandipaper and phone photos Clinica paper file Doctorits own system Labresult by SMS Pharmacyprescription photo

No shared record. Each provider keeps its own piece, and Thandi carries the rest on paper and on her phone.

HealthPass on its own

HealthPass holds one record but is connected to only one provider HealthPassher record in WhatsApp Clinicconnected Doctornot connected Labnot connected Pharmacynot connected

One record that Thandi owns, opened in WhatsApp. It fills in only where HealthPass has built a connection to that provider’s system.

HealthPass on a beckn network

HealthPass, other wallets and every provider connect through one network HealthPassone wallet Other walletsher choice beckn networkshared registries, signed messages Clinicany clinic Labany lab Pharmacyany pharmacy

Each provider connects once, to the network. Results and prescriptions reach her record from any of them, in whichever wallet she chooses.

Key points

01

HealthPass today

HealthPass gives each patient a personal health record that they control. It has three parts.

  • The record. A private, secure store for one patient’s health data. It uses FHIR, the international standard that modern clinic, lab and pharmacy systems already use to exchange health data. At its core is the International Patient Summary (IPS), a standard short summary of the patient: allergies, conditions, medicines, vaccinations and recent results.
  • WhatsApp as the way in. The patient opens the record from a link in WhatsApp, as a secure page inside the chat. There is no app to download, and it works on the phones people already have.
  • An access log. Every time someone opens the record, HealthPass logs who it was and when.

How a nurse sees the record today

  1. Thandi shows a QR code.She opens HealthPass in WhatsApp and shows the nurse the QR code on her screen.
  2. She gives the nurse a one-time PIN.She receives a short PIN in WhatsApp that works once. It shows she agreed to share her record for this visit.
  3. The nurse enters their own access code.HealthPass sends each health worker an access code over WhatsApp. The code expires after a few hours, so an old one can’t be reused.
  4. The nurse reads the summary and adds the visit.The access is written to the log.

What HealthPass can’t do on its own

  • It can’t tell who is a real health worker. The access code proves that someone got a code from HealthPass. It doesn’t prove they are a licensed nurse at a real clinic, because HealthPass has no shared list of licensed providers to check against. Sending and typing codes also adds a step to every visit.
  • Every clinic, lab and pharmacy has to be connected one by one. For results to arrive by themselves, HealthPass has to build a link to each provider’s software. A country has hundreds of these systems, so this is slow and costly, and it starts again in every new country.
  • So most care never reaches the record. When Thandi has a blood test at a lab HealthPass isn’t connected to, the result reaches her on paper or by SMS. Her record doesn’t change unless someone types it in.

What joining a beckn network fixes

  • A shared register of who is licensed. Clinics, labs, pharmacies and health workers are listed in a registry with a digital key, and every message they send is signed with that key. HealthPass checks the signature instead of handing out codes.
  • Connect once. A lab connects its system to the network once. From then on, any patient app on the network can order tests from it, HealthPass included.
  • Records fill in as care happens. When a lab or pharmacy completes an order placed over the network, the result goes back to the patient’s record as part of the same exchange.

FHIR is the format of the record. Beckn is the set of rules for how independent organisations find each other, agree on a service and trust each other’s messages.

02

India built national systems this way

Over fifteen years India built a series of shared digital systems that the government provides and any company can build on. They are often called digital public infrastructure (DPI). Each reached national scale. Two of them, ONDC and Namma Yatri, use beckn.

  1. 2010AadhaarNational digital ID1.45 billion numbers issued1
  2. 2016UPIPayments between any app and any bank24 billion payments in Sept 2026; 741 banks connected2,3
  3. 2021Account AggregatorSharing financial records with the customer’s permission338 million accounts linked; 566 million permissions given4
  4. 2021ABDMhealthSharing health records between providers, with no central database978 million health IDs; 1.2 billion records linked7
  5. 2021ONDCbecknOnline shopping: any shopping app can buy from any seller500 million orders by July 20265
  6. 2022Namma YatribecknA ride-hailing app that charges drivers no commission150 million trips6
The government provides the shared partsA national ID, registers of who is who, a common set of rules for how systems talk to each other, and the rules everyone must follow.
Companies build the appsPeople use apps made by companies, which compete to be the best.
Every app must work with every providerSo no app owns its users, and no provider has to connect to each app separately.

Other countries are adopting the same approach. The G20 endorsed a framework for digital public infrastructure in 20238, and MOSIP, an open-source national ID system, is being rolled out in Uganda and eight other African countries9.

03

How beckn works

Beckn is an open set of rules (a protocol) that lets independent apps and providers find each other, agree on a service, and follow it through to the end. Any app on a beckn network can place an order with any provider on it, without the two having to build a connection to each other and without a company in the middle.

The roles on a beckn health network The patient talks to HealthPass over WhatsApp. HealthPass searches a search service, which indexes the catalogues providers publish. HealthPass and the provider use beckn messages to agree the order, and FHIR to read and write health records. A registry lists everyone on the network and their digital keys. PatientWhatsApp Search serviceIndexes signed catalogues HealthPassConsumer node + record ProviderClinic, lab or pharmacy RegistryWho is on the network chat search publish catalogue beckn: price, book, confirm, track FHIR: read and add records, with permission check identity look up

Beckn handles the order or booking. Every message is digitally signed, so the receiver can check who sent it and that it wasn’t changed, and the receiver sends back a signed receipt. Both sides can later prove who asked for what, and when. FHIR, the international standard for health records, handles the records themselves, and only with the patient’s permission. Health records never travel inside a beckn message.

Every service goes through the same stages:

Find
search
Agree
check pricegive detailsconfirm
Deliver
updatestrackingcancel
Afterwards
ratesupport

In the latest version of beckn (May 2026), each provider publishes its own signed catalogue and search services read those catalogues, so there is no central hub that every message has to pass through18.

HealthPass does two jobs: it stores the record, and it is the app patients use

These two jobs are easy to mix up. On a beckn network they are separate, and a patient can swap either one.

Storing the record (the “wallet”)The patient’s health record and summary. With her permission, providers read from it and add to it.
The app the patient usesThe WhatsApp chat and assistant that searches, books, orders and shows her the record. In beckn terms it is the consumer node.

India’s payments work the same way. Your bank holds your money; that’s the wallet. PhonePe or Google Pay is the app you pay with, and it holds no money. Because the two are separate, you can change apps and still pay the same shops the next day.

A patient can switch in two ways:

  • Keep the record, change the app. Another app reads and adds to the same HealthPass record, with the patient’s permission. Nothing moves, just as you can use a different email program on the same email account.
  • Move the record. The patient moves her full record to another wallet. South Africa’s data protection law (POPIA) already gives patients the right to get their personal information, including health records, but not yet a right to move it between services11. The network’s rules would need to require that.

Either way she keeps her ID, which is a national ID rather than an app account, and she keeps her providers, who join the network rather than any one app. HealthPass does both jobs but keeps them separate. That is what makes the promise of no lock-in believable to governments and funders, and it lets other apps work with records kept in HealthPass.

04

Ordering a lab test, filling a prescription and booking an appointment

The same beckn rules handle all three.

Flow diagram

    Thandi, Kopano Clinic, Thuso Lab and Imbali Pharmacy are made up for these examples. Prices are rough estimates.

    Every service follows the same steps

    StepLab testPrescriptionAppointment
    Search, without saying who you areLabs offering HbA1c within 5 kmPharmacies that deliver within 5 kmAntenatal clinics within 5 km
    Ask for today’s offerPrice, collection timesStock, price, cheaper genericFree appointment times
    Give only the details neededTime, address, which orderAddress, which prescriptionName, phone, medical aid
    Confirm, and give permissionThe lab may see this one orderThe pharmacy may see this one prescriptionThe clinic may see her summary for 7 days
    Provider reads what it needsThe test orderThe prescription, then checks the doctor’s licenceHer health summary
    UpdatesCollector arriving, sample at the labRider on the way, deliveredReminder the day before
    Result added to her recordLab resultWhat medicine was given; prescription marked as filledVisit summary

    A provider that sets up these steps once can serve every patient app on the network, for every service it offers.

    05

    How India shares health records

    India’s Ayushman Bharat Digital Mission (ABDM), launched in September 2021, is the largest working example of a national system for sharing health records. There is no central database of records. Records stay with the hospital, clinic or lab that created them, and are shared only when the patient approves14.

    ABHA numberA 14-digit health ID. It’s voluntary. People get one by confirming who they are with a one-time code, sent through Aadhaar (India’s national ID) or to their phone. It holds no health information; records from different providers are linked to it24.978 million created, Sept 20267
    ABHA addressAn easy-to-read name such as priya@abdm. Patients use it to sign in to health-record apps and to approve requests for their records24.
    RegistriesNational lists of health facilities and of health professionals, so everyone can check who they are dealing with.533,000 facilities · 985,000 professionals, July 202622
    Consent managerA service that passes requests between providers and keeps track of what the patient approved. It never sees the health records themselves21,28.

    How India shares a health record

      Where the records are kept

      Every hospital, clinic and lab keeps its own records in its own software. To take part, that software must be certified for ABDM, so it can link visits to an ABHA and answer requests for records. Nothing is copied to a national database. The system knows where records are, not what they say.

      WhoWhat it keepsWhat it never sees
      Hospital, clinic or labThe health records, in its own system
      Consent managerA list of which providers hold records for each ABHA address, and every approval the patient has givenHealth records
      ABDM gatewayNothing lasting. It passes messages on and checks that senders are registered.Health records
      Provider asking for recordsA copy of what the patient approved, until the permission endsAnything she didn’t approve
      Patient’s appHer ABHA address, her approvals, and if she chooses, her own copy of her records

      How a record is shared

      1. Records are linked to the ABHA.This happens in one of two ways. The hospital links a visit when it happens, often after the patient scans a QR code at the registration desk23. Or the patient finds older records from her app: she chooses the hospital, the hospital matches her by name, age and phone number, and she confirms with a one-time code29. Either way, the consent manager learns that this hospital has records for this person. It doesn’t learn what they say.
      2. A provider asks.The clinic that wants the records sends a request to the consent manager with the patient’s ABHA address. It says why it wants them, which kinds of record (prescriptions, lab reports, discharge summaries and so on), from which dates, and how long it will keep them.
      3. The patient approves.She sees the request in her app and can narrow it to particular hospitals, visits or kinds of record. The consent manager then issues a signed consent artefact for each hospital involved, listing exactly what may be shared and when the permission ends26.
      4. The clinic asks the hospital for the records.The request includes the consent artefact, a one-time encryption key, and the address the hospital should send the records to26.
      5. The hospital checks and sends.It checks that the consent artefact is genuine, covers this request and hasn’t expired, then takes the approved records from its own system. It converts them into the FHIR format using India’s national standards25, encrypts them with the clinic’s one-time key, and sends them straight to the clinic. It then tells the consent manager the transfer happened, so there is a record of it. The gateway and the consent manager never see the contents.
      6. The clinic uses the records, then deletes them.It decrypts the records and shows them to the doctor. Every permission has an end date, after which the clinic must delete the records or remove anything that identifies the patient27.
      Strengths
      • No central database to be hacked or controlled
      • Providers stay in charge of their own records
      • The patient approves every share, and every share is logged
      Weaknesses
      • The hospital’s software has to be online and certified when a request comes in
      • Every request waits for the patient, and most patients don’t respond
      • No one has the complete history unless someone keeps a copy

      How far adoption has got

      India measures adoption in three stages. The first two have reached very large numbers. The third, which needs the patient to approve a request, is where it is stuck16.

      StageWhat it coversWhere it stands
      1Creating ABHA IDs978 million IDs (Sept 2026)7
      2Providers linking records to ABHA IDs1.2 billion records linked (Sept 2026)7
      3Providers requesting and receiving records with the patient’s approval“Extremely low” use (July 2026)16

      India keeps records and services separate, as we propose

      ABDM shares records, using FHIR. A separate network called UHI uses beckn to find and book services such as doctors, ambulances and blood banks14,20. India kept the two apart, which is the same split we propose for South Africa.

      IndiaSouth Africa
      Patient IDABHA number and addressNumber from the Health Patient Registration System (HPRS), used in public facilities: 68.6 million registrations, 37.2 million verified12
      Registers of facilities and staffNational facility and professional registriesMaster Health Facility List (over 55,000 facilities)12; registers of the Health Professions Council, Pharmacy Council and Nursing Council
      Where records are keptWith each provider; nothing centralWith each provider. An electronic record for public clinics is being rolled out from 202636, and a national exchange is being built19,35
      How patients give permissionA consent manager, for each requestNo national system yet. POPIA allows health information to be shared only with consent or another legal basis11
      Patient’s appGovernment ABHA app or private health-record appsAny wallet, including HealthPass on WhatsApp
      Finding and booking servicesUHI, which uses becknThe proposed network

      Lessons for HealthPass

      • Use the national systems that exist; don’t rebuild them. IDs and registries are public goods. In South Africa, HealthPass should use the Department of Health’s Health Patient Registration System and Master Health Facility List12, and the public registers of the Health Professions Council and the Pharmacy Council.
      • The approval step needs an app people already use. ABDM is weakest at the stage where the patient has to act. HealthPass is on WhatsApp, which people already open every day.
      • Keep the patient’s own copy. In ABDM terms, HealthPass is a health-record app that keeps a copy of each record as it is created. That gives the patient the complete history the ABDM model leaves out, and a summary she can show at any clinic, including one that isn’t connected.
      06

      Why a network

      The prescription shows the difference most clearly.

      Today: a photo of a prescription

      A photographed prescription is filled at two pharmacies Prescription photoforwarded on WhatsApp copy 1 copy 2 Pharmacy Afilled it Pharmacy Bfilled it again
      • A photo can be edited, and nothing shows who wrote it.
      • The same prescription can be filled twice.
      • The prescriber never learns what was actually given.

      On a beckn network: a signed digital prescription

      A signed prescription is checked and filled once HealthPasssigned prescription checked, filled refused: already used Pharmacy Arecords what it gave Pharmacy Bnothing to fill
      • The doctor’s signature and licence are checked against the registry.
      • Once filled, the prescription is marked as used, so it can’t be filled twice.
      • A record of what was given, including any cheaper generic, goes back to the doctor.

      Problems a beckn network solves

      Finding care without one company in control
      HealthPass on its ownHealthPass can only offer the providers it has connected to.
      On a beckn networkProviders publish their own signed catalogues, search services index them, and no one owns the listings.
      Connecting once
      HealthPass on its ownOne connection per provider, in each country.
      On a beckn networkA lab joins the network once and can serve every patient app.
      Trusting providers you have never dealt with
      HealthPass on its ownA one-time PIN from the patient and a short-lived access code for the provider. Neither shows that the provider is licensed.
      On a beckn networkEvery organisation is listed in a registry with a digital key, every message is signed, and the receiver sends back a signed receipt.
      The same steps for every service
      HealthPass on its ownBooking, lab orders and pharmacy are each built separately.
      On a beckn networkThe same steps handle all three, and any new service.
      Permission for one order, not the whole record
      HealthPass on its ownThe QR code and PIN open the whole record for the visit.
      On a beckn networkThe provider can see only what one order needs, for a set time, and the permission is tied to that order.
      Records fill in as care happens
      HealthPass on its ownInformation arrives only where a connection exists.
      On a beckn networkEvery completed order adds its result to the patient’s record.
      AI assistants can act safely for patients
      HealthPass on its ownAn assistant acting for a patient would have to work through provider websites.
      On a beckn networkIt works with structured catalogues and signed agreements, and every step is recorded.

      Three ways to build a health record system

      A central government recordOne company’s platformAn open network
      Who builds itThe government, usually through one supplierOne companyThe government runs the shared parts; many companies build apps
      Who the patient depends onThe government’s systemThe company: her account, history and providers are all inside its platformNo single app. She keeps her ID and record, and can change app or wallet without losing her providers
      Adding a providerA separate connection to the central systemOn the company’s terms and feesJoin once
      Booking, ordering and deliveryUsually not includedYes, inside the platformYes, between everyone on the network
      What usually goes wrongSlow, one supplier, one point of failurePatients get stuck and fees riseSomeone has to set and enforce the rules, and patients need an app they already use

      Being able to switch doesn’t mean people will. On UPI, two apps handle about 79% of payments10. But those apps win by being better, and they can’t hold people’s money or shops hostage, so leaving stays easy. The same will be true for health only if the network’s rules require every wallet to hand over the record in a standard format. Setting that rule is the government’s job.

      07

      Patients aren’t tied to HealthPass

      HealthPass is one place a patient can keep her record. We call such a place a wallet. HealthPass shouldn’t be the only one. On a beckn network any company, hospital or NGO can run a wallet, and every wallet reaches every clinic, lab and pharmacy on the same terms. A patient can change wallet and take their record with them, the way people in India change payment app without changing bank.

      Many wallets on one health network Thandi uses HealthPass and can switch to another wallet. When a wallet places an order, the provider sends the result back to that wallet. An optional patient registry, which she joins only if she chooses, tells a provider that has only her ID which wallet to send to. Every wallet connects to the same beckn health network, which reaches every clinic, lab and pharmacy. if she opts in switch optional: finds her wallet when a provider has only her ID order out, result back Thandipicks her wallet Patient registryoptional · ID → wallet HealthPassone wallet Wallet Banother company Wallet Ca hospital or NGO beckn health networka public good: open rules, shared registries Clinicsserve every wallet Labsserve every wallet Pharmaciesserve every wallet
      When a wallet places an order, the provider sends the result back to that wallet, because every beckn message carries its sender’s address. The patient registry is optional: it is only needed when a provider has nothing but the patient’s ID, and it holds no health data.

      How a wallet joins

      A wallet joins the network once, the same way a lab does. It registers in the network registry, which lists every organisation on the network and its digital keys, and it is approved under the network’s rules, including the rule that it must hand records over when asked. From then on it can search, order and receive results for all of its patients. Patients don’t join one by one; their wallet acts for them. There are three ways to run a wallet:

      • Run your own node, as HealthPass does.
      • Use a hosted node run by someone else. This suits a hospital or NGO that wants its own wallet without running servers.
      • Build an app with no storage of its own, working on top of a wallet that someone else runs.

      Finding a patient’s wallet

      Usually no lookup is needed, because the wallet starts nearly every order or booking. When HealthPass orders a lab test, the order carries HealthPass’s network address, so the lab sends the result straight back to it. Any other wallet works the same way.

      A lookup only matters when the provider starts the contact and has nothing but the patient’s ID. For example, she walks into a clinic without booking through her wallet, or a doctor sends a prescription a week after the visit. There are two ways to handle that:

      She shares her wallet addressShe shows a QR code at the clinic, or gives an address such as thandi@healthpass. Like an email address, it says which wallet to send to, and nothing central is involved.
      The provider asks the patient registryAn optional registry answers one question: which wallet holds this person’s record? It holds her ID, name, contact details and the name of her wallet, and no health data. Patients choose whether to be listed.

      These are two registries with two jobs. The network registry lists organisations, and every beckn network needs one. The patient registry lists people, and it is optional. A central list of who uses which health wallet is sensitive, so if one exists it should be opt-in and held by the government. India’s ABHA works this way (see How India did it): the ID is voluntary and issued by a national registry, and a consent manager tracks which hospitals hold each person’s records without seeing what they say.

      South Africa’s Department of Health already runs a national patient register, the Health Patient Registration System. It is used in 3,265 public facilities and holds 37.2 million verified registrations12. The network could add an optional note of each patient’s wallet to that register rather than building a new one. Where a country has no national register, one can be built as part of the network, as a public good.

      Switching wallets

      1. She asks the new wallet to take over.It confirms her identity with a one-time PIN sent to her phone.
      2. HealthPass hands over her full record.It sends it to the new wallet in the standard format: FHIR, with her International Patient Summary.
      3. Results find the new wallet.If she is listed in the patient registry, the registry records her new wallet, and providers find it from her ID. If she isn’t, HealthPass forwards anything sent to her old address for a set period, and she gives providers her new address at her next visit.

      Using more than one app or wallet

      Several apps, one walletThe simplest choice, and the one we recommend. Her record lives in one wallet, and any number of apps read and add to it with her permission, using the standard method for secure access to health records: a pregnancy app, a pharmacy app, or an app a family member uses to help with her care. It’s like using two payment apps on the same bank account.
      Two walletsPossible, but it splits the record again, which is the problem we started with. It works if she picks one as her main wallet, where providers send results by default, and the other keeps a copy that stays in sync with her permission.

      What keeps patients free to switch

      • The patient’s ID belongs to the patient. It is a national ID, not an account with any wallet.
      • The record is in a standard format. Every wallet stores FHIR and must hand the record over when the patient asks. That is a network rule, not a promise from any one company, including us.
      • Providers join the network, not a wallet. A lab connects once and serves patients from every wallet.
      • The rules are open. The health domain pack and the adapters we build are published for anyone to use, including competing wallets.
      08

      Our role and business model

      What South Africa already has

      The Department of Health already runs much of what a network needs. Its Health Patient Registration System has 68.6 million registrations, 37.2 million of them verified, across 3,265 public facilities, and its Master Health Facility List covers more than 55,000 public and private facilities12. Both are being made available through a national exchange that uses FHIR19. Doctors can already sign prescriptions electronically, as long as they use an advanced electronic signature13.

      People already use health services on WhatsApp at national scale. MomConnect, the Department of Health’s service for pregnant women and new mothers, has 5.2 million users31, and the department describes WhatsApp as a “game-changer” for it12.

      The government has also committed to shared digital systems. Its Digital Transformation Roadmap, launched in May 2025, covers digital ID, data sharing between systems and payments, and names health for its second phase, from mid-202730. PayShap, the instant payment system launched in 2023, passed one billion payments in June 202632.

      What’s missing is a shared way for patient apps, clinics, labs and pharmacies to find each other, place orders and send results. A beckn network adds that, and HealthPass is one of the wallets on it. It would work alongside the national exchange rather than replace it. It also has to serve public clinics as well as private providers: 15.5% of South Africans belong to a medical aid33.

      Who does what

      Government and donors
      • Pay for and oversee the network as a public good
      • Registers of patients, facilities and health workers
      • The network’s rules, and approving who can join
      • National record sharing and data protection
      Other organisations
      • Other wallets and patient apps
      • Clinics, labs, pharmacies and medical aids
      • Search services
      HealthPass team
      • Build the network with government and donors: the open beckn health domain pack (the health-specific rules for the network), based on FHIR and South Africa’s national health data standards, and open FHIR-to-beckn adapters for existing health software
      • Help organisations join the network
      • Run HealthPass as one wallet on it

      How we make money

      • The network is not the business. We build it with government and donors as a public good, and no one owns it, including us. That is what lets a government adopt it and other companies build on it.
      • Helping organisations join. Clinics, labs, pharmacies, medical aids and health software companies need help to get on the network: connecting their software, getting approved to join, running a hosted node for those who don’t want to run their own, and support afterwards. We charge for this work.
      • Services through HealthPass. HealthPass competes as one wallet among several. Because every provider on the network can be reached without building a separate connection, HealthPass can offer services on top of the record, such as booking, lab tests and medicine delivery. It earns from these by being the easiest to use, not by holding patients’ data.
      • Who pays for what. Government and donors pay for the shared parts: the domain pack, the open adapters, links to national registers, and pilots. Our income comes from helping organisations join and from HealthPass services.
      • Examples from India. Moving Tech built Namma Yatri, a commercial app on an open beckn network, to 150 million trips6. On UPI, two apps handle about 79% of all payments10. Open networks still leave room for successful businesses.

      What gets built first

      1. A draft health domain pack covering lab orders, prescriptions and appointments.
      2. FHIR-to-beckn adapters, so clinics, labs and pharmacies with modern (FHIR-based) software can join without rebuilding it.
      3. An optional link from the network to the Health Patient Registration System, so a patient who chooses to can be found from her ID.
      4. A pilot in South Africa with one group of clinics, one lab and a few pharmacies.
      09

      Risks

      • Health networks have been slow to start. India’s health network on beckn, UHI, was first proposed in 2021 and formally launched in June 2026, with five services live14,20. It sends every message through a central government hub and has published no usage figures. The latest version of beckn doesn’t need a central hub.
      • Subsidies don’t create demand. On ONDC, shopping orders fell from 6.5 million to 4.6 million a month after incentives were cut. Ride-hailing, where a commission-free app met real demand, grew to 56% of all orders15.
      • Getting patients to approve requests is the hard part. In India’s ABDM, providers still rarely share records with the patient’s approval, because patients don’t complete the approval step16. An app patients already use, on WhatsApp, is the missing piece. That’s where HealthPass fits.
      • Other wallets can join the same network. That is intended. HealthPass has to win on WhatsApp’s reach, its assistant and being first, and the business of helping organisations join doesn’t depend on HealthPass winning.
      • The health domain pack doesn’t exist yet. We found no published guide to using beckn and FHIR together for health. Writing one is real work.
      • The rules are still changing. POPIA treats health information as specially protected, and new rules for health information took effect in March 202634. Because HealthPass reaches patients through WhatsApp, it has to show how it meets POPIA when messages pass through Meta’s service. The National Health Insurance Act, signed in May 2024, is before the Constitutional Court, which reserved judgment in May 2026, and none of its sections is in force17. The network has to work whatever the outcome. The national digital health strategy expired in 2024 and its replacement has not been published35.