Care that starts when it is needed
A structure that runs from the moment a patient asks a question until prepared information reaches the consultation room.
AetherHeal's philosophy · goals and principles
A judgment made in the consultation room
should carry through to the next task outside it.
Our founder, a practicing physician, sees that gap in the consultation room. A patient's question disappears at the booking step. A physician's plan breaks off once the visit ends. AetherHeal is building the structure that connects the two.
Our goal is to return the effort clinics spend on booking, relaying and waiting to the care itself.
- The founder's view
- A physician founder who still sees patients
- The unit we build
- One patient flow that closes all the way
- The unit of evidence
- Source, date and physician action
- Final authority
- The physician who sets the clinical judgment and the treatment plan
Specialization and connection
Specialize the work. Connect the care.
“The division of labour is limited by the extent of the market.”
Adam Smith, The Wealth of Nations (1776), Book I, Chapter III, chapter-heading excerpt; capitalization normalized. Read the source
AetherHeal's reading
When a task can be reused across settings, there is reason to invest more deeply in specialization and evaluation. Each institution then checks that the specialized capability works inside its real care flow.
For job-specific expertise to become one continuous care journey, the connections between them must be designed too.
One scoped task
Setting A
Institutional validation and authority check
Setting B
Institutional validation and authority check
Setting C
Institutional validation and authority check
A · A physician founder who still practices
AThe person building it
is in the consultation room.
AetherHeal's founder, Dr. Jee Hoon Ju, is a physician. He sees patients himself and watches where a patient's words, images, visit notes and the next task break apart.
Moving clinical standards into software takes more than the record written after the visit. Who checks, where it stops, and what must be left behind for the next person to take over all belong in one flow.
Purpose-built AI engines for each job in care, and a Clinical OS that keeps them on one patient state under one line of physician authority.
B · How we work
BBefore building fast,
we set the order we keep.
The same principles apply to the product, to research and to what we say publicly. Authority comes before execution, evidence before claims, completion before engagement metrics.
- Authority
Authority comes before automation.
We separate what a tool may propose from what it may execute. Clinical judgment and treatment decisions, corrections, exceptions and final clinical responsibility remain with the physician.
- Evidence
Evidence comes before claims.
We separate what we built from what we have proved. Product status, field evidence and public wording stay within what dates and sources support.
- Completion
Completion comes before engagement.
Rather than clicks or replies, we look at whether one patient's task ended responsibly. A task is done only when an owner, a due date and closing evidence remain.
C · The care we are reaching for
CExtending the reach
of accountable care.
Care in which context and responsibility connect at the moment they are needed.
Clinical context across language and distance
A structure in which clinicians can confirm the context they need, whatever the patient's location or language.
Responsibility that continues outside the consultation room
A work structure in which owner, due date and closing evidence continue after the visit ends.
D · Responsibility built into the product
DThe person who checks and the evidence
live inside the product together.
Staff take over tasks; clinicians make clinical judgments. Building the information and the review order they need into the product is our design principle.
Confirmation by an authorized person
Administrative tasks are confirmed by authorized staff; proposals that need clinical judgment are confirmed by clinicians against evidence and authority.
The physician's clinical decision
The AI prepares a draft for the physician to review. The physician sets the clinical judgment and the treatment plan, makes the corrections, handles the exceptions, and carries final clinical responsibility.
Evidence with a confirmed scope
Adoption counts, product results and clinical outcomes are published with a date only after their evidence scope is confirmed.
What the chart does, and the execution layer
The chart records what finished. We handle what has not finished yet.
Principles and evidence
Principles show in the order
evidence is laid down.
Dated public evidence and the architecture's boundaries of responsibility are in separate documents.