Products and platform
Find a product for traveler interpreting, clinical notes or patient inquiries, then explore how they connect.
Open a product to see its workflow and current scope.
Prepare for a medical visit in Korea
Prepare inquiries, consultations and on-call work
Agent Whenever
A workflow under verification: prepare replies and intake on the institution’s messaging channel, then hand off to staff.
Pre-launch validation
DockieTalkie Clinical Copilot
A working screen for physicians to review conversation evidence alongside a draft note.
Pre-launch validation
Firstcall
Organize facts and missing information from a call into a draft handoff for the resident to review.
Pre-launch validation
Define how clinical images should be compared
Dermatoscan AI
Review the image comparison workflow with patient, site and capture time kept together.
Pre-launch validation
WoundScan AI
Study measurements and comparisons over time using the boundary and scale set by a clinician.
Pre-launch validation
Clinical OS · Golden Clinical Loop
The architecture behind the products: Clinical OS connects patient state and responsibility; the Golden Clinical Loop defines how work moves through review to completion. Explore that structure below.
01 / SHARED ORBIT
Purpose-built tools find their place around the context of one person’s care.
06 / Workflow example
AI prepares the repetitive work, and nothing moves on until the responsible staff member has checked it. Completion is confirmed by the booking record actually changing and the notification actually being delivered.
ΔC · DeltaCΔC (DeltaC) is a metering concept we are developing to count completed healthcare cognitive work that carries the required checks, approvals and evidence. Details are in the whitepaper.
Illustrative workflow · synthetic data · no real actions
Example task EXAMPLE-01
Paused at the staff review gate
Change an appointment time
Why review is needed
A time change affects the clinic schedule. Staff must check the source record and approve this administrative change.
Next action
Review the source and choose “Approve this example” to continue.
Responsible person
Authorized clinic staff
The example closes only after both the booking record and notification delivery are verified.
What closes this task?
The approved time appears in the booking record AND the required notification has confirmed delivery.
Appointment attendance is not established. No clinical outcome is shown.
Buttons change this local illustration only. No real booking, message, or record is created or saved.
02 / THE SHARED LAYER
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.
The existing hospital chart remains the system of record.Pre-launch validation
Select a layer to trace its role. Exploration does not approve an action or connect a system.
AI proposes. Staff verify operational details. Physicians retain clinical authority.
Read the architecture ↗03 · An engine per job
Each product focuses on one job, with its current stage shown alongside it.
Patient messaging access
Pre-launch validation
Prepares English guidance and staff handoff on messaging channels authorized by the healthcare institution. No customer account or real patient message is currently connected.
Free traveler service
Free for travelers · community coming soon
Free interpreting and medical tourism information for travelers, with a community and clinic/pharmacy advertising model in preparation.
In-visit review
Pre-launch validation
Puts the questions to ask, the evidence behind them, and a record draft on the physician's review screen.
Next-step proposals
Pre-launch validation
Proposes the next task inside the authority and the order of confirmation the clinical team has set.
Follow-through
Pre-launch validation
Attaches an owner, a due date, and the evidence of closure to one patient's open work.
Cosmetic pigment-image comparison
Pre-launch validation
Places cosmetic pigment-treatment images on the physician's review screen together with the patient, the site, and when it was taken.
Wound progression research
Pre-launch validation
We are working with partners on a product structure that shows wound photos and their measurements side by side over time.
04 · Golden Clinical Loop
Pre-launch validation
The Golden Clinical Loop is one turn of work: the AI proposes, the physician confirms, an approved tool acts, and evidence of closure is written down. Every stage sits on the same patient and under the same physician authority.
Read where the patient and the work currently stand.
Lay out what has to be checked and what is still blank.
Suggest the next step, inside the scope that was set.
The clinical team checks the evidence and the authority.
Only approved tools and named owners act.
Check the result against what booking, the EMR, and the CRM return.
Write down the owner, the due date, and what has not finished.
Reviewed corrections and operating changes go into the next version.
07 · How we work with hospital systems
We turn a clinic's repetitive work into standardized units of execution. For each task, who approved it, whether it actually ran, and how it was verified are recorded the same way. Systems and roles differ between institutions, and the structure is designed to stay the same across them; clinical judgment, treatment decisions and final responsibility remain with the physician.
The final state of each record is decided by that system. We define what is read and written first, and record who approved and what the system returned.
We start read-only, checking patient state and permissions. Write scope opens only after review.
A sentence in which a model says it finished does not count as finished. Completion is recorded only from the system's response.
Which AI may read or write what is defined in advance, and only versions that passed human review actually run.
09 · Product screens
What a product carries in the clinic, and how ready it is, differs product by product. We show the real screens and the dated public scope, and nothing past it.
Pre-launch validation
Patient messaging channel connection preparation
Free for travelers · community coming soon
Free interpreting · medical tourism information · community planned
Pre-launch validation
Physician review screen
Pre-launch validation
Cosmetic pigment-treatment reference
Pre-launch validation
Wound imaging research workflow
Training hospitals
Pre-launch validation
A tool for interns and residents to organize on-call cases
A resident structures an on-call case and prepares the report for a senior physician. The tool organizes; the resident judges and reports.
See Firstcall10 · Two starting points
A hospital job starts from on-site authority and the systems of record. An engine starts from which tools it may call and how far it would connect into Clinical OS.
Third-party developer marketplace · Future direction
A future direction. It does not exist yet and it is not a commitment.
No public self-serve path
11 · The boundary of public evidence
As of 2026.08.11
This page describes how the product is put together today and where responsibility ends. It does not establish operating results at outside hospitals or clinical outcomes. Availability is stated separately for each product.
Registered structure
Private prototype, one private build line, and a recorded boundary for what each part is allowed to do
Public evidence
Only the private-prototype label is public.
What we do not claim
Outside adoption, performance figures, clinical outcomes, or a publicly available build console
