Private by default. Shared by choice. Open when it serves the public good.
Make health data useful — without giving up control.
Health data is stuck between two bad options: locked in systems that never speak to each other, or handed to whoever offers to analyse it. There is a third design.
We don't want to own healthcare data. We build the infrastructure that makes it safer and more useful to collaborate around it.
That sentence is a constraint on us, not a slogan. It rules out the business model where a platform accumulates data and resells the view. What is left is narrower and more useful: the connection layer, the standardization, the governance controls, and the aggregation — with the organizations that produced the data deciding, at every step, how far it travels.
| 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. |
| What it takes | A connection. Nothing else changes. | An agreement with a named circle, and a data type you choose. | An aggregate you approve, published without anything that identifies a person, a pharmacy or a customer. |
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
- 01ConnectRead from the systems that already produce the data: pharmacy software, screening deployments, health networks.
- 02StandardizeProduct names, units and codes differ everywhere. Without this step nothing downstream is comparable.
- 03GovernWho sees what, at which level of aggregation, for how long, revocable when. Governance is a step in the pipeline, not a page in a contract.
- 04AggregateIndividual records become counts, rates and trends. Nothing that identifies a person survives this step.
- 05AnalyzeAvailability, price movement, stock-out risk, screening coverage — questions a single organization cannot answer from its own data.
- 06ShareBack to contributors first, to a defined circle second, to the public only where the contributor said so.
- Private output
- Shared output
- Open output
Three roles, and ours is the smallest.
Target
Contributors
Organizations that produce routine health data and decide how far it travels.
Target
Data users
Ministries, researchers, funders and manufacturers that need a view of a market as it operates.
Current
AZ54
The infrastructure between the two. We connect, standardize, enforce the rules the contributor set, and aggregate. We are not a party to the data.
The rules we are building it on.
These are design principles for infrastructure on the roadmap, not controls you can audit today. We would rather publish them early and be held to them.
The contributor decides
Per data type, per circle, per level of aggregation. Consent that cannot be narrowed is not consent.
Revocable by default
Stopping is a setting, not a negotiation. It applies to everything downstream that has not already been published as an aggregate.
Aggregate before anyone else sees it
Nothing leaves a contributor's boundary at the level of an individual record.
No resale
Contributed data is not a product we sell. Access for data users is negotiated per use, and contributors are told which uses exist.
Symmetry
A contributor always gets more back than they put in, or the arrangement is not worth their time.
Neutrality
The infrastructure does not favour the organization that runs it. We take no position in the markets our contributors compete in.
What we do not do.
- We do not become the owner of data our clients or contributors connect. Connecting is not transferring.
- We do not sell contributed data, in any form, to anyone.
- We claim no certification — no GDPR, HIPAA, ISO or data residency claim is made anywhere on this site.
- We do not collect patient data through this website. No form here asks for any.
Designed for a neutral data ecosystem.
If you hold routine health data, or need to read a market you cannot see, the useful conversation starts now — while the rules are still being written.