FOR MEDICINE · KODA KENKŌ · TOKYO
Continuity, where
it is not optional.
Clinical infrastructure for systems that cannot forget a patient between sessions. Built for Japan.
Stateless assistants reset. Medicine cannot.
We build the continuity layer beneath the model — patient context, identity, and audit that survive every session boundary and every change of substrate.
01 — THE CLINICAL PLATFORM
KODA Kenkō.
Applied proof.
Our medical product line, built on the KoLo continuity-first agent architecture. Reception, triage, SOAP, billing, and schedule — all in Japanese.
Visit KODA Kenkō ↗02 — THE WORKFLOW
One thread, end to end.
Reception
Intake and patient context that persists across every visit — never a cold start.
Triage
First-line assessment under clinician oversight, with the reasoning kept on record.
SOAP
AI-drafted clinical notes — Subjective, Objective, Assessment, Plan — held for human approval.
Billing
Charge capture and reconciliation aligned to Japanese clinical workflow.
Schedule
Appointment and resource coordination that keeps state between sessions.
03 — THE STANDARD
What clinical continuity demands.
Patient context, persisted
A clinical agent that cannot forget a patient between sessions — continuity is the safety feature.
Human-in-the-loop
Every draft — note, triage, charge — passes through clinician approval. The agent assists; it does not decide.
Defensible audit trail
A record of every action, in the form medicine and Japanese regulators expect.
Built for Japan
Designed around MHLW, JAHIS, and APPI from the first line — not retrofitted.
04 — TWO SURFACES
Lab and clinic, deliberately separate.
KodaSōken is the research house and the runtime. KODA Kenkō is the applied clinical product. Clinicians, hospitals, and compute partners each meet the right surface.
See the architecture →A patient is never a cold start.
Medical AI infrastructure with memory that holds.
Begin a conversation →