Evidence record

What we built and what we proved are different things.

This page records, with dates, what we have confirmed, what is still being measured, and what we do not claim. Every line carries a boundary so that the state of a product is never read as a clinical result or a business result.

Document type
Evidence behind our public claims
As of
2026.08.11
Author
AetherHeal

01 · Public state

What exists now and what is planned do not share a column.

Public state classifies what is on offer. Clinical OS is the layer that holds purpose-built AI engines on one patient state under the director's authority. It runs beside the chart. It does not replace the EMR. The level of evidence is a separate question, answered in the next table.

Current public state

The public state and the evidence boundary can be read together.

  • Clinical OS

    Pre-launch validation

    Scope of the maturity label as of 2026.08.19

    Until dated public evidence is attached, we describe only what it does and where responsibility ends.

  • Golden Clinical Loop

    Pre-launch validation

    No public evidence attached

    We describe only where the patient currently stands, who approves, the record of why it was done that way, and how completion is confirmed. We publish no effect figures.

  • Dockie-talkie

    Pre-launch validation

    Preparing to open the beta on 2026.09.01

    We describe only the product screens you can see and the scope we are preparing to offer.

  • Clinical Copilot

    Pre-launch validation

    Clinical Copilot v1.1.2 as of 2026.08.08

    We describe it only as assisting work that a physician has to check and correct.

  • Clinical OS Agent

    Pre-launch validation

    No public evidence attached

    We do not describe it as a separate product or as something you can request today.

  • Golden Clinical Loop

    Pre-launch validation

    Scope of the synthetic case stage, where validation runs on fixed synthetic cases

    We do not describe it as a product that is publicly available today.

  • Dermatoscan AI

    Pre-launch validation

    Reference workflow scope as of 2026.08.19

    We describe only the reference workflow a physician reviews and the current validation scope.

  • WoundScan AI

    Pre-launch validation

    Scope of the partner co-development work and its validation procedure

    We describe only the product structure partners review and the current validation scope.

  • Firstcall

    Pre-launch validation

    Pre-launch validation

    We describe it on the premise that the resident judges and reports to a senior physician.

  • Hospital AI transition

    15-minute fit call

    What is open today is the 15-minute fit call

    What is open today is only the step that checks whether the scope fits. Adoption terms are proposed after that scope is confirmed, not before.

Published price

The published price for Dockie-talkie self-serve signup is KRW 149,000 per clinic per month, VAT included.

  • Dockie-talkie

    Pre-launch validation

    Preparing to open the beta on 2026.09.01

    We describe only the product screens you can see and the scope we are preparing to offer.

Private

Private collaboration or internal scope. It does not mean general availability.

  • Private build line

    Private prototype

    No general availability

    We record it as one private build line and nothing more. It does not imply public availability.

  • Private playbook library

    Private

    No public evidence attached

    Private material. We do not list it as a public item on a third-party developer marketplace.

Future direction

A long-term direction, not part of what is on offer today.

  • Third-party developer marketplace

    Future direction

    Not part of the current release

    A future direction. It does not exist yet and it is not a commitment.

02 · Evidence by product

A product name and a level of evidence are read separately.

Each axis looks only at public evidence as of 2026.08.11. Anything not tied to a public record is marked as the weaker state.

Clinical OSPre-launch validation
Code presence

Limited evidence

The scope the evidence appendix marks as validation

Historical proof

No public evidence

No public evidence attached

Current-release proof

Limited evidence

Scope of the maturity label as of 2026.08.19

Real-world proof

No public evidence

No field evidence attached to this capability

Golden Clinical LoopPre-launch validation
Code presence

No public evidence

No public evidence attached

Historical proof

No public evidence

No public evidence attached

Current-release proof

No public evidence

No public evidence attached

Real-world proof

No public evidence

No public evidence attached

Dockie-talkiePre-launch validation
Code presence

Limited evidence

The product page and the state of beta preparation

Dockie-talkie product page
Historical proof

No public evidence

No public evidence attached

Current-release proof

Limited evidence

Preparing to open the beta on 2026.09.01

Dockie-talkie product page
Real-world proof

No public evidence

No public evidence attached

Clinical CopilotPre-launch validation
Code presence

Documented

The prepared state of Clinical Copilot v1.1.2

Clinical Copilot product page
Historical proof

No public evidence

No public evidence attached

Current-release proof

Documented

Clinical Copilot v1.1.2 as of 2026.08.08

Real-world proof

No public evidence

No evidence of clinical results

Clinical OS AgentPre-launch validation
Code presence

No public evidence

No public evidence attached

Historical proof

No public evidence

No public evidence attached

Current-release proof

No public evidence

No public evidence attached

Real-world proof

No public evidence

No public evidence attached

Golden Clinical LoopPre-launch validation
Code presence

Limited evidence

Validation marked as running on fixed synthetic cases

Historical proof

No public evidence

No public evidence attached

Current-release proof

Limited evidence

Scope of the synthetic case stage, where validation runs on fixed synthetic cases

Real-world proof

No public evidence

No public evidence attached

Dermatoscan AIPre-launch validation
Code presence

Limited evidence

Marked as a reference workflow for physicians only

Historical proof

No public evidence

No public evidence attached

Current-release proof

Limited evidence

Reference workflow scope as of 2026.08.19

Dermatoscan AI product page
Real-world proof

No public evidence

No evidence of outside results

WoundScan AIPre-launch validation
Code presence

Limited evidence

Scope marked as a P0 scaffold, meaning the initial skeleton and its validation procedure

Historical proof

No public evidence

No public evidence attached

Current-release proof

Limited evidence

Scope of the partner co-development work and its validation procedure

WoundScan product page
Real-world proof

No public evidence

No evidence of outside results

FirstcallPre-launch validation
Code presence

Limited evidence

Product screens of the reference app for residents

Firstcall product page
Historical proof

No public evidence

No public evidence attached

Current-release proof

Limited evidence

Pre-launch validation

Firstcall product page
Real-world proof

No public evidence

Not evidence of adoption by clinics

Private build linePrivate prototype
Code presence

No public evidence

Only the private prototype label is public

Historical proof

No public evidence

No public evidence attached

Current-release proof

No public evidence

No general availability

Real-world proof

No public evidence

No public evidence attached

Hospital AI transition15-minute fit call
Code presence

Not applicable

A hospital transition is read separately from whether code exists

Historical proof

No public evidence

No public evidence attached

Current-release proof

No public evidence

What is open today is the 15-minute fit call

Real-world proof

No public evidence

No public evidence attached

Private playbook libraryPrivate
Code presence

No public evidence

Private material

Historical proof

No public evidence

No public evidence attached

Current-release proof

No public evidence

No public evidence attached

Real-world proof

No public evidence

No public evidence attached

Third-party developer marketplaceFuture direction
Code presence

Not applicable

Future direction

Historical proof

No public evidence

No public evidence attached

Current-release proof

Not applicable

Not part of the current release

Real-world proof

No public evidence

No public evidence attached

03 · Customer evidence tiers

Interest, a contract, and evidence from the field are not one tier.

The eight tiers below run from the strongest evidence down to the weakest signal. A tier with no public entry registered against it is left empty.

  1. 08

    Paid pilot in live use

    No public entry registered

  2. 07

    Paid controlled pilot with a set start date

    No public entry registered

  3. 06

    Signed fixed-price build sprint

    No public entry registered

  4. 05

    Paid adoption review

    No public entry registered

  5. 04

    Signed design-partner scope with a named sponsor

    No public entry registered

  6. 03

    Letter of intent

    No public entry registered

  7. 02

    Verbal interest

    No public entry registered

  8. 01

    Compliment

    No public entry registered

04 · Dated evidence

What we confirmed and what is still out of scope stay together.

The dates and the wording of the existing public record are kept as they are. No entry stands in as evidence for a different fact.

  1. 01

    Tongyeong Seoul Hospital selected as an essential-care testbed

    Tongyeong Seoul Hospital has been selected as an essential-care testbed and preparation is under way.

    This does not mean product use or results have been confirmed. We record the selection and the fact that preparation is under way, and nothing beyond that.

    Public company recordEvidence owner: Founder
    Subject
    Tongyeong Seoul Hospital
    Confirmed
    Selected as an essential-care testbed, now in preparation
    Not yet
    Confirmed product use or results
  2. 02

    Clinical Copilot v1.1.2

    Clinical Copilot v1.1.2 is prepared to the same level as the state published on its product page.

    It is a working screen that moves only when a physician confirms. It carries no regulatory status and no clinical results.

    Clinical Copilot product pageWhitepaper v2.0Evidence owner: Founder
    Subject
    Clinical Copilot v1.1.2
    Confirmed
    The readiness of a working screen that moves only on physician confirmation
    Not yet
    Regulatory status or clinical results
  3. 03

    About 2,000 automated tests

    We run about 2,000 automated tests, including regressions on the safety rules.

    A test count shows the regression coverage of code and rules. It shows neither clinical validity nor results in the field.

    Internal CI record, not externally verifiedEvidence owner: Founder
    Subject
    About 2,000 automated tests
    Confirmed
    Automated test coverage including safety-rule regressions
    Not yet
    Clinical validity or results in the field
  4. 04

    NVIDIA Inception member

    AetherHeal is a member of the NVIDIA Inception program.

    We record membership status only. It is not an endorsement of the product or the company.

    NVIDIA Inception membership approval notice (2026-07-10), copy not publicEvidence owner: Founder
    Subject
    NVIDIA Inception
    Confirmed
    Program membership
    Not yet
    Any endorsement of product or company quality
  5. 05

    Preparing the Dockie-talkie beta opening

    We are preparing to open the Dockie-talkie beta on 2026.09.01.

    This is the readiness state published on the product page. Scope and sequencing can still change while we prepare.

    Dockie-talkie product pageWhitepaper v2.0Evidence owner: Founder
    Subject
    Dockie-talkie
    Confirmed
    Preparation for a beta opening on that date
    Not yet
    A fixed scope and sequence
  6. 06

    Whitepaper v2.0 published

    We published Whitepaper v2.0, separating the evergreen paper from a dated evidence appendix.

    We do not flatten products that are at different stages into one level. Facts that change with the date are written in the evidence appendix, not in the paper.

    Whitepaper v2.0Evidence owner: Founder
    Subject
    Whitepaper v2.0
    Confirmed
    The split between the evergreen paper and the dated evidence appendix
    Not yet
    Reading every product as being at the same stage
  7. 07

    Building and measuring inside our own practice

    We build, test, and measure inside the aesthetic and dermatology practice where our founder still sees patients every week.

    This is not a count of outside institutions that adopted anything. It is the access we have to build and test inside our own practice.

    Founder-confirmed, not externally verifiedCorrected 2026.08.22: the earlier wording counted two clinics; the count has been removedEvidence owner: Founder
    Subject
    Our own aesthetic and dermatology practice
    Confirmed
    Access to build and measure inside our own practice
    Not yet
    A count of outside adopters, or clinical results

05 · Repeated-test evidence

What we test repeatedly in code and safety rules is kept apart from results in the field.

A reliability record shows what gets tested again and again. On its own it fills none of the other evidence axes.

About 2,000 automated tests

We run about 2,000 automated tests, including regressions on the safety rules.

A test count shows the regression coverage of code and rules. It shows neither clinical validity nor results in the field.

06 · Not yet proven

Being measured does not turn into being proven.

Figures for adoption outcomes and clinical results stay unpublished until the evidence scope is confirmed.

Effect of an AI transition

Measuring

We are measuring how far the workflow changes and what the physician actually does. We do not publish figures for adoption outcomes yet.

Effect on average spend per patient

Measuring

We are settling the measurement definition and the comparison window. We do not publish effect figures yet.

Clinical outcomes

Not published

We do not publish clinical outcome figures until the evidence scope is confirmed.

Any number missing from this page is a number we have not proven yet.

07 · What we do not claim

We do not write sentences our evidence cannot carry.

This section summarises the boundary on what we say in public. The detailed principles on physician authority and clinical wording live in the clinical safety document.

Judgment in place of the physician
We do not claim that the product makes a diagnosis or a treatment decision in the physician's place.
Settled performance
We do not guarantee accuracy, and we do not present performance as settled.
Adoption elsewhere
We do not present a count of outside institutions as a published result.
Product revenue
We do not present product revenue as a published fact.
Regulatory status
We do not claim to hold a regulatory status that has not been confirmed.

The detailed principles are in the clinical safety document.

08 · Update rule

We update the wording after the evidence changes.

We update this record when a payment or a signature is confirmed. We also add a line whenever the current-release evidence changes.

  1. 01

    Record the date and the scope that was confirmed.

  2. 02

    Leave the scope that is still unconfirmed in the same entry.

  3. 03

    Confirm the evidence owner and whether the case may be published.

  4. 04

    If the state got weaker, drop straight to the weaker wording.

Questions about the evidence scope or the as-of date go to drjeeju@aetherheal.com.