↑ ↓ to present

A vision · Naing Maw

Healthcare 2.0

The infrastructure for continuous care.

Scroll

The problem

Healthcare doesn't have a digital problem.
It has an infrastructure problem.

Walk through any clinic and the software is everywhere — booking, records, prescribing, monitoring. More technology per consult than at any point in history. And a patient still leaves one provider and arrives at the next as a stranger.

The failure isn't at the interface. It's in the architecture underneath — the layer that should make care continuous, and doesn't. Twenty years of "digital health" has mostly digitised the fragmentation.

What's broken, structurally

The encounter is the unit.
It should be the patient.

Healthcare 1.0 — episodic

Care is a series of episodes.

Every encounter starts near zero.

History is split across systems.

The patient carries the continuity — when they're least able to.

And the system stops waiting to be opened. It reads where the patient is and brings the next step to them. Push becomes pull. The filing cabinet becomes attention.

The architecture

Three layers. Built from the bottom up.

Most of healthcare ships only the top layer. Tap each layer.

The surface — an interface that disappearsLast to build
Most days the system says nothing, and the silence is the product working. When it speaks, it says one true, clinician-validated thing at the moment it matters — then gets out of the way. The measure of maturity is not adoption. It is disappearance.
The intelligence — prepares, never decidesReads the record
Learns the person's baseline, surfaces the anomaly, drafts the recommendation, translates the plan into language the patient can act on. Its job is to protect the one resource that doesn't scale — the clinician's attention — and spend it only on the calls that genuinely need a human.
The foundation — the longitudinal recordThe strategic layer
One continuous record per person — consults, scripts, dispensing, results, daily lived data — accumulating across years and providers. Portable by design: she sees everything, shares with granular consent, and can take all of it elsewhere. It outlives any single clinical relationship. The layer that carries the patient is the one almost nobody owns.

Truth lives at the bottom · the surface is the last thing you build

What it feels like — the patient

The app disappears.
The care stays.

The system has been quietly collecting the whole time — her cycle, her sleep, her labs, the one-line journal entries that cost her a minute. Most mornings: nothing.

One morning, her phone lights once. One validated insight, with its provenance and her clinician quietly in the loop. She glances, half-smiles, gets on with her morning.

Try the card — either action returns it to silence.

7:14
Tuesday · Cycle day 19
Morning · From your care team

Your cycle's been steady three months. Your sleep dipped this week.

Two short nights, magnesium skipped both. Nothing urgent.

Most days, it says nothing

What it feels like — the clinician

Decisions, not data.

The patient's calm is manufactured here. The system has read everything, handled what is unambiguously safe, logged all of it — and surfaced only the calls that need a human. Try approving the routine items. The safety flag won't clear without a deliberate review.

Dr S · Morning triage 3 need you · 41 handled today
Safety · review required
New bleeding reported — review now.
Deterministic flag · cannot be auto-cleared or bulk-dismissed
PCOS · 29
Insulin held in range 12 weeks — taper one supplement?
Same pathway as the lifestyle stack · low risk · evidence on tap
Perimenopause · 41
Sleep + cycle pattern worth a note — send a drafted check-in?
Drifting · last activity 23 days · message pre-drafted
Routine queue clear. The safety item still needs your eyes.
41 safe items handled & logged · shown for awareness

The consult becomes the exception — and when one is needed, it arrives prepared.

Trust by architecture

Trust isn't claimed.
It's built into the structure.

Law 01

The clinician is always in the loop

Permanent, not transitional. What improves over time is not whether a human decides — it's how well the system spends human attention.

Law 02

Safety is deterministic

A hard rail above the model. It never asks the AI to judge its own output, and certain lines never cross without a human. Written once; the model gets smarter underneath it forever.

Law 03

Commerce is walled off

The clinical layer never sees price or margin — an architectural boundary, not a policy. Most of a well-built plan earns the operator nothing. That ratio is the proof.

Law 04

Everything is attributed & audited

Who prepared it, what it was based on, who approved it, when — on an immutable log. The system's worst day is better documented than the old system's best day.

The hard questions

Answered directly.

A concept earns credibility by how it handles its best objections.

Isn't this just the national record with a better interface?+
No — structurally. The national record is a document repository: episodic summaries, provider-mediated. This is a living longitudinal model: it learns a baseline, carries the plan as live data, ingests daily signals, coordinates practitioners around one current picture. Complementary by design — the platform speaks the national standards at its boundary and contributes upward. The national record is where summaries of care go; this is where care actually runs.
What does "patient-owned" actually mean, legally?+
An architectural commitment, not a claim about legal title. Records are legally held by providers; what this system builds is the full practical substance of ownership — she sees everything, consent is granular and revocable, the complete record exports at any time, and it persists beyond any clinical relationship. The law treats the operator as custodian; the architecture treats the patient as principal. She can take all of it and leave — and the system was built so she could.
Does "the consult becomes the exception" survive regulation and funding?+
Built as a deliberate transition. The safety layer encodes the review intervals and escalation rules professional standards require, so continuous care raises the floor of oversight: between formal reviews, the system watches, where today nobody does. The economic shift — attention replacing appointments as the unit of care — is named as a design input and planned with clinical and financial leadership, not discovered as a side effect. Regulation follows demonstrated safety; the architecture is built to demonstrate it.
Isn't an always-collecting record a surveillance risk?+
The answer is structural, like the commerce wall. Data minimisation with visible provenance. The record serves one master — never sold, never advertising, commercially blind. Consent is the perimeter: opt-in, granular, previewable, revocable, defaults set to less. And honesty about what can't be promised away: minimum retention of raw streams, de-identification, encryption, export-and-delete. The felt experience must be care, not watching — and the structure must back the feeling.
A record is only a passport if someone else accepts it.+
True — the cold-start problem killed most patient-held record attempts. So the design works in stages: the record is worth holding at zero external acceptance (it powers her own care from day one); acceptance starts inside a federation of specialist clinics on one base layer; and the bridge outward is patient-mediated and standards-based. Universal acceptance is a decade-scale outcome — the architecture is valuable at every point before it.
Will clinicians — and their indemnity insurers — accept this?+
Possibly the real adoption constraint, ahead of regulation. The answers are designed to be better than the status quo: deterministic protocols authored by clinical leadership, nothing reaching a patient without a hard rule or a named clinician's sign-off, and a complete immutable chain of who prepared what, approved by whom, when. The claim to defend in front of an insurer isn't "the model is accurate." It's that the floor of oversight between visits is higher — because today, that floor doesn't exist.

How we get there

Build the foundations,
not the far-future system.

Concept to align. Primitives to progress. Never the end-state as throwaway software. Each piece earns its keep today and survives to year five.

Now

Primitives

Patient-journey state machine · federated longitudinal record · immutable audit trail · conflict engine.

Phase 1

The care plan

The first visible surface of the record — multi-practitioner, attributed, coordinated. Shipping.

Then

The passport

Identity, consent, cross-clinic continuity. A second clinic opens already knowing her.

End-state

Intelligence

Ambient, generative, continuous — under the constitution. The interface disappears.

This is not written from a whiteboard. It is being built — a live multi-brand clinical platform in Australia; a women's-health clinic as the first instance. And the measurements behind the design are real: in a sample of 113 referrals received by the clinics, the field naming the tests required was completed in ten. Free text, measured. That is why the foundation captures structure at the source.

The goal isn't a better clinic.
It's a system that understands where a person is — across the whole of their health — and meets them there.

Healthcare 2.0 · Silently · Continuously · Built to last