// 01
The client
A pioneering Australian healthtech startup, building one of the early blockchain-powered prescription platforms in the 2016–2017 era — back when both digital prescriptions and blockchain in healthcare were genuinely new territory. The idea was simple to state and hard to build: give patients ownership and control of their own prescription data, instead of leaving it scattered across doctors and pharmacies who held it about them but not for them.
// 02
The problem it solved
In most healthcare systems, your prescription data isn't really yours. It lives in your doctor's system, your pharmacy's system, the hospital's system — fragmented, and controlled by everyone except you. When you see a new doctor, reconstructing your full medication history is slow and error-prone. The patient — the one person present at every appointment — is the one person without the complete picture.
This platform flipped that. The doctor writes a digital prescription; it syncs to the patient's app. The patient decides whether to share it with a pharmacy — which either delivers it or readies it for pickup, then marks it served so it can't be over-ordered beyond the prescribed limit. Visit a new doctor, and the patient chooses exactly what history to share. The patient sits at the center, controlling their own data — which, in healthcare, is still unusual.
// 03
The build
This was a genuinely complex product to ship: three connected applications, a regulated domain, and an early-days blockchain integration — all of which had to work together.
Three apps, one system. Our team built the patient mobile app, the doctor's app, and the web platform for pharmacies — each with a different user, a different workflow, and a shared source of truth underneath.
A regulated, security-first architecture. Healthcare data is, as the founder put it, a honeypot for hackers. The platform was built HIPAA-compliant, with prescription data encrypted and the blockchain layer providing a tamper-evident record — so a prescription couldn't be quietly duplicated or forged, and a breach couldn't expose more than a single, undecryptable record.
Early-days blockchain. This was built when "blockchain" was still bleeding-edge for most industries, let alone healthcare. Our team handled the application architecture and the staging-environment blockchain and compliance integration; specialist consultants took the blockchain and HIPAA setup the rest of the way for production.
Worth noting honestly: like many blockchain-era products, the platform's real value turned out to be the patient-controlled data model more than the blockchain itself — a lesson the broader industry learned around the same time.
// 04
My role
I led the delivery team that built the platform — a team of eight: developers, design, and QA in India, plus one peer in Australia who owned the direct client relationship and technical decisions. My focus was making the build happen: turning a complex, multi-app, regulated product vision into shipped software, coordinating a distributed team across two countries, and keeping three interconnected applications moving toward one coherent system.
It's a different slice of the work than architecting a system solo — this was leading a hard build to completion, which at scale is its own discipline.
// 05
The outcome
- →
A pioneering product, shipped — three connected apps for patients, doctors, and pharmacies, in a regulated domain, during the earliest days of blockchain in healthcare.
- →
Launched and piloted — the platform went live, was demonstrated at industry events in the US, and earned recognition in the healthtech and blockchain communities.
- →
A genuinely patient-first data model — at a time when "patients owning their own health data" was still more aspiration than reality.