At the source
The data is structured the moment a pharmacist scans a product. Not retroactively, not manually, not on a paper that gets lost between the dispensation and the claim.
A node of Great Sage Labs
Reimbursementbetween pharmacies and insurers,finally automated.
We're building the data layer that connects every dispensation in a pharmacy to the insurer who pays for it — structured, verified, real-time. The pharmacy module is live today. The insurer integration is what comes next.
Casablanca-based · Built by Great Sage Labs · French, Arabic, English
i.
1 node
Live in production today (pharmacies)
ii.
2 sides
We're building both ends of the bridge
iii.
0 paper
Reconciliation runs on structured data, not on trust
iv.
15 pharmacies
Pilots ready for beta testing
What we're building
The bridge that doesn't exist yet.
Today in Morocco, every pharmacy dispensation generates data. None of it reaches the insurer who pays for it in a structured, verified, real-time form. The reconciliation that follows runs on paper, on weeks of delay, and on trust where there should be proof.
We're building the layer that changes that. A data infrastructure where every dispensation, the moment it happens, becomes a structured claim ready for the insurer to verify and reimburse. No retroactive paper trail. No manual encoding. No silent fraud.
We're starting with the pharmacy side because it's the side where the data is born. Insurer integration is in active design — and it's why we're talking to operators now, before the architecture is set in stone.
The architecture
Structured at the source. Verified by design.
Every dispensation captured by Alchemy Lab is structured to be reimbursable from the moment it's recorded. The data model is the architecture, not an afterthought.
Verified, end-to-end
Every transaction carries its full audit trail: the pharmacy, the dispensation, the timestamp, the product. Designed to satisfy a third-party verification process from day one.
Built for what comes next
The data model is being designed today with insurer integration in mind. Patient identifiers, prescription metadata, and claim-ready structures are the next layer — and we're shaping them with the operators who will receive them.
The first node, live today
Pharmacies are how we start.
We didn't start by talking to insurers. We started by being inside pharmacies — because that's where the data is born, and where the operational reality is hardest. The pharmacy module of Alchemy Lab is a working product, in production, used by real pharmacists in Morocco.
Pharmacy module · Reimbursement intelligenceLive
What it actually looks like.
The pharmacy console — every dispensation structured the moment it leaves the counter, every reimbursement traceable, no paper trail in between.
alchemy.greatsagelabs.com / claims
Reimbursement overview
· Live syncPending
In queue
Validated
Cleared
Recovered
Synced
Reimbursement flowLive
Augmentin 1g · awaiting validationPending
Doliprane 500 · ready to submitReady
Predictive expiration alerts
Six-month horizon on every product about to die unsold. Sales velocity x batch expiry, automated.
Invisible loss intelligence
Expirations, breakage, theft, mis-counts. Quantified in dirhams every month. You finally see what was bleeding you.
Plugs into your existing system
Already running pharmacy software? We work alongside it. Native connectors are on the roadmap; in the meantime, our import wizard handles up to 50,000 products in seconds.
Why this, why us, why now
The architecture decisions get made once.
Morocco's healthcare system is at the threshold of a digital transformation. Universal health coverage is expanding. Reimbursement processes are under pressure to formalize. The infrastructure to support that doesn't exist yet — and the architecture choices made in the next eighteen months will define how the system runs for the next decade.
We're Moroccan. We've built the pharmacy node first because we believed the data had to come from the source, not from a top-down system imposed on operators who'd reject it. Now we're talking to insurers who want to be at the table when the architecture gets defined — before it's defined without them.
How it works
- Ⅰ.
Capture data at the source.
- Ⅱ.
Structure it for the people who need it.
- Ⅲ.
Connect the bridge, end to end.
Designed in Morocco, for Morocco's healthcare reality.
Things people ask us
Frequently asked.
Is the insurer integration live today?
Yes — it's live, currently under testing and continuous improvement. The pharmacy module is in production, the data layer captures every dispensation in a structured form, and the insurer integration is operational. We're refining it alongside operators to harden it for full-scale deployment.
Why start with pharmacies if the goal is insurers?
Because that's where the data is born. A reimbursement infrastructure built on a top-down architecture imposed on pharmacists would fail at the operational layer. We start where the data lives — and build the bridge from there.
Is my data secure?
Security is foundational, not a feature. Alchemy Lab is built by a team that includes a cybersecurity specialist. Every release is penetration-tested before launch.
Can I use Alchemy Lab today as a pharmacist?
Yes. The pharmacy module is in production. Access is currently invitation-based — talk to us and we'll get back to you within a few business days.
Are you working with any specific insurance operator?
We're at the conversation stage with multiple operators. We don't name partners we haven't formally signed with. If you operate in healthcare insurance and want to be at the table when this architecture gets defined, talk to us.
How does this fit with Great Sage Labs?
Alchemy Lab is the first node of the infrastructure Great Sage Labs is building for Morocco's healthcare ecosystem. The pharmacy is one node. More are coming.