The infrastructure layer for digital healthcare.
Embed financial services, digital screening, patient engagement and health analytics without rebuilding the infrastructure from scratch.
Running today with healthcare software partners across 5 African markets.
What the infrastructure has handled so far.
- Transactions processed
- 130K+
- Unique financial services users
- 90K+
- People screened
- 15K+
- Active community pharmacies
- 30
- African markets
- 5
Our own operating figures, not market estimates. Transactions counted since June 2024.
One infrastructure. Multiple healthcare capabilities.
Each module carries a label for what it actually is today: available, in development, or on the roadmap. One of the four is in production.
- Available
Financial services
Collection, payouts, wallets and an immutable double-entry ledger through one API. Money movement is executed by licensed payment institutions and mobile money operators — AZ54 never holds funds.
Executed by licensed payment institutions and mobile money operators
- In development
Digital screening
Camera-based screening that turns devices staff already own into first-line risk identification tools. Deployed in the field today; programmatic access is in development.
- In development
Patient engagement
Reminders, follow-up and referral messaging that extend care beyond the point of interaction. In development — there is no public API for it today.
- Roadmap
Health data & analytics
Cross-network intelligence built on routine dispensing data: availability, price movement, stock-out risk, screening coverage. On the roadmap. Transaction-level reporting, on the other hand, is available today.
Three steps, from integration to distribution.
Integrate
One REST API, one set of scoped keys, one dashboard. Signed webhooks tell your system what happened, and when.
Activate modules
Turn on the capabilities your product needs, market by market, without a second integration.
Distribute
Every point of care you already serve can offer the new capability the week it ships.
We don't build distribution from scratch. We plug into it.
Healthcare software vendors already reach the pharmacies, clinics and health workers we would otherwise spend years reaching. AZ54 sits one layer below them: we ship the capability, they carry it into their network, the network serves patients. That is the whole thesis, and it is why a single integration matters more than a single sale.
- AZ54 · Infrastructure layer
- Healthcare software partner
- Healthcare network · pharmacies, clinics
- Patients
Infrastructure that translates into healthcare access.
The same integration that moves money also carries screening. In a community pharmacy, that turns a purchase into a health interaction.
Infrastructure that translates into healthcare access.
Measurement
A physiological measurement is taken with a device the pharmacy already has.
Risk identification
The measurement identifies whether the person may be at risk. It concludes nothing about their health.
Health alert
When a threshold is crossed, an alert is raised for the pharmacy staff, in plain language.
Referral
The person is directed to a health professional, with what was measured and when.
Confirmatory testing
The professional decides. Confirmation, diagnosis and care stay entirely with them.
Screening identifies people who may benefit from confirmatory testing. It is not a diagnosis, and it replaces no one.
- Health alerts generated
- 3,500+
- Conjunctival screenings
- 2,000+
- Suspected anaemia cases identified
- ~550
Private by default. Shared by choice. Open when it serves the public good.
Make health data useful — without giving up control.
We don't want to own healthcare data. We build the infrastructure that makes it safer and more useful to collaborate around it.
| Scroll to compare the three modes | Private | Shared | Open |
|---|---|---|---|
| Who can see it | Only the organization that produced it. | A defined circle, under a written agreement. | Anyone, as aggregates that identify no one. |
| What it is for | Your own operations and reporting. | Benchmarks and early signals, returned to contributors. | Public-good uses: shortage monitoring, research, policy. |
| Who decides | You. | You, per data type and per circle. | You, aggregate by aggregate. Opt-in, never a default. |
Scroll to compare the three modes
These three modes describe how the infrastructure is designed. The governance controls behind them are on the roadmap, not in production.
One infrastructure. Different levels of openness.
- Pharmacy software
- Screening deployments
- Health networks
- 01Connect
- 02Standardize
- 03Govern
- 04Aggregate
- 05Analyze
- 06Share
- Private output
- Shared output
- Open output
Governance is a step in the pipeline, not a policy document bolted on at the end. The pipeline itself is on the roadmap.
See healthcare markets as they actually operate.
Routine dispensing data, aggregated across a network, shows availability, price movement and stock-out risk while there is still time to act. Surveys arrive months later.
ILLUSTRATIVE DATA
ILLUSTRATIVE DATA
Contribute data. Get better intelligence back.
What you contribute
Routine records you already produce: dispensing, stock, prices, screening volumes. Nothing extra to collect, nothing about a named patient.
What you get back
Your own position against a wider network, stock-out signals earlier than your own data can show them, and price movement you would otherwise learn from a supplier.
Who this infrastructure is for.
Current
Infrastructure clients
Healthtechs, pharmacy software vendors and healthcare networks that embed our modules into their own product.
Target
Data contributors
Organizations that already hold routine health data and want more out of it than their own reporting.
Potential
Data users
Ministries, researchers and funders that need to see a health market as it operates, not as it was surveyed.
Where the infrastructure runs today.
{{markets}} markets, named one by one. Nothing beyond them, and no country counted twice.
Cameroon
XAFDemocratic Republic of the Congo
CDFRepublic of the Congo
XAFTogo
XOFCôte d'Ivoire
XOF
The map is a drawing, not data. The list is the source of truth.
From one software partnership to real-world deployment.
Meditect publishes pharmacy management software used by pharmacists in French-speaking Africa. Through that one integration, capabilities we built reach pharmacy counters we have never visited. A single healthcare software partnership can distribute new infrastructure across multiple healthcare access points — which is why we build for integrators rather than for end customers.
Meditect is an independent company and a commercial B2B partner. Neither company owns any part of the other, and no Meditect figure appears on this site: the numbers here are AZ54's own deployment.
Your request
POST /v1/payments
Signed webhook
payment.succeeded
- Active community pharmacies
- 30
- African markets
- 5
Built in Africa. Designed to scale.
The constraints we build under — intermittent connectivity, mobile-first payments, thin margins per transaction, health systems where the pharmacy is the first point of contact — are not African peculiarities. They describe most of the world's healthcare, and infrastructure that works here transfers more easily than infrastructure that assumes a hospital and a card terminal.
We do not operate in Europe. We describe the adaptation path openly, without dates.
Build the next generation of digital healthcare.
Tell us what you are building. We will tell you what is available today, what is in development, and what we would be inventing.