Less paperwork.More medicine.

AI prepares. Professionals review. Teams move faster.

KODA KENKŌ is an AI-powered operational layer for healthcare teams. It sits above the EMR, rezekon, scheduling, and document feeds your team already runs — and produces structured, human-reviewed artefacts that enter the operational record.

KODA KENKŌ operational support layer architecture diagram

How the platform works

AI prepares.
Professionals review.
Teams move faster.

Five steps. One operational record. Every step human-reviewed and logged.

01

Collect

Voice, documents, intake forms, insurance cards, system feeds. Whatever shape the information arrives in, the platform ingests it.

02

Organise

KoLo OS routes each piece of information into the right workflow — medical clerk queue, SOAP workspace, medication reference, home-care log, telemedicine session.

03

Draft

Purpose-built AI agents prepare structured drafts: intake summaries, SOAP narratives, referral letters, claims packs, interaction flags, care notes. One agent per workflow.

04

Review

The professional — clinician, nurse, pharmacist, clerk, administrator — reviews the draft. Edits. Approves or rejects. The decision, the reviewer, and the timestamp are recorded.

05

Record

The final artefact enters the operational record. Exportable. JAHIS-aligned. FHIR-compatible. Audit-clean.

Five-step KODA KENKŌ human-reviewed audit pipeline: 1. Collect (収集), 2. Organise (整理), 3. Draft & Retrieve (下書き・参照), 4. Review (確認), 5. Approve & Escalate (承認・連携). Each step records to the immutable audit trail with timestamp, action, user, and status. 監査記録 · 履歴.

KoLo OS

Not a cloud dependency.
An operating layer built
for medical reality.

The operating foundation underneath every KODA KENKŌ product.

Continuity across model changes

AI models change every few months. Regulators issue new guidance. Vendors get acquired. KoLo OS isolates your workflow from what changes underneath. Your audit trail, your approvals, and your operational record stay continuous regardless.

Professional roles, not generic users

Doctor. Nurse. Pharmacist. Medical clerk. Administrator. Home-care provider. Public-health officer. Each role sees the workflows, permissions, and review boundaries appropriate to their responsibility.

Memory that persists

Patient context carries across intake, SOAP, medication reference, home-care visit, and telemedicine follow-up. Surfaced when needed. Not buried in folders.

Audit trail by default

Every action — collect, draft, review, approve, reject, export, sync — is logged. Who did it. When. What changed. Append-only. Immutable.

Local and edge operation

Clinics, home-care visits, rural health posts, disaster-response teams. The platform runs where the patient is. Syncs when connectivity returns. Full audit history across offline and online states.

KODA KENKŌ workflow UI on a Japanese hospital workstation, with KoLo OS foundation blocks underneath: Workflow Memory (ワークフローメモリ), Roles & Permissions (役割・権限管理), AI Routing (AIルーティング), Edge Operation (エッジ運用), Audit History (監査履歴). Real Japanese healthcare staff reviewing patient workflow.

Japanese-grade origin

Built in Japan.
Designed for Japanese clinical reality.

KODA KENKŌ is engineered from Japanese medical practice, not adapted from foreign healthcare software.

  • SOAP follows the Japanese clinical model主観的情報 · 客観的情報 · 評価 · 計画. Not retrofitted from a Western template.
  • Dictation understands Japanese clinical realityKansai, Tōhoku, Kyūshū, Hokkaido regional speech patterns. Multi-language intake — English, Portuguese, Chinese, Vietnamese, Tagalog, Nepali, and other major Asian languages — for the foreign-patient flow most clinics handle manually.
  • Medication built on Japanese HOT codesComposition, dosage forms, indications, contraindications, interactions — drawn from Japanese pharmacology references, not adapted from foreign formularies.
  • Export aligned to Japanese standardsJAHIS 標準データ交換 · MHLW guidelines · PMDA expectations · 個人情報保護法 (APPI).

Governance & security

No clinical artefact is finalised
without a human reviewer.

The review boundary is the load-bearing architecture, not a checkbox.

Clinician-in-the-loop by default

Every draft — SOAP note, referral letter, claims pack, medication flag, care plan — is reviewed and approved by a qualified professional before it enters the operational record. The platform prepares. The professional decides.

Role-based access

Clinician, nurse, pharmacist, medical clerk, administrator, auditor. Each role has bounded permissions. No role can bypass the review step for clinical artefacts.

Immutable audit trail

Every draft, every review decision, every edit, every approval — recorded. Exportable for institutional audit, regulatory inspection, or legal discovery.

Data residency configurable

On-premise. Cloud. Hybrid. Edge. You control where patient data lives and which jurisdictions it crosses.

Deployment models

One platform.
Four deployment topologies.

Match the topology to the operational reality, not the other way around.

Cloud

Managed infrastructure. Automatic updates. Zero on-site hardware. For clinics and hospitals that prefer operational expenditure.

On-premise

Deployed inside your institutional network. Full data sovereignty. For university hospitals and public-health networks with strict data-residency requirements.

Hybrid

Operational workloads on-premise. AI inference in the cloud or on dedicated edge hardware. For organisations that want data locality with AI capability.

Edge

Local-first operation. For rural clinics, home-care teams, mobile health units, and disaster-response deployments. Works offline. Syncs when connected.

Integrates with what is running

No rip-and-replace.
No parallel record.
No migration project.

KODA KENKŌ reads from and writes back to the systems your team already maintains.

  • EMR systemsORCA, Medicom-HRf, Dynamics, Fujitsu HOPE, NEC MegaOakHR. Integration via HL7 FHIR and JAHIS-aligned export.
  • Rezekon (receipt computers)Reads claims data, writes back structured claims-preparation packs. JAHIS-aligned export to existing billing software.
  • Document feedsFax, email, scanner, patient portal — triaged into the workflow queue automatically. No manual sorting.
  • Scheduling systemsReads appointments, writes back structured intake and consultation summaries to the patient’s operational record.
  • Insurance & claimsClaims-preparation artefacts exportable to existing billing and rezekon software. No parallel claims pipeline.

Start with one module

Modular like building blocks.
Start with the workflow that removes your biggest friction.

Add the next module when your team is ready. The operational record carries across.

Modular Healthcare Platform Adoption — five-step pathway: 1. Pilot One Workflow (パイロットワークフロー), 2. Validate with Staff (スタッフによる検証), 3. Add Related Module (関連モジュールの追加), 4. Connect Existing Systems (既存システムの接続), 5. Expand Across Organization (組織全体への拡大). Applied to Small Clinic, Hospital Department, Home-Care Provider, and Municipality contexts. モジュラー型ヘルスケアプラットフォームの導入。

Small clinic

Medical Clerk — intake, forms, referrals, claims prep. Save clerk hours without adding software the doctor learns.

Hospital department

SOAP — structured documentation, bilingual records, audit-clean notes across shifts and teams.

Home-care provider

Home Care & Nursing — visit notes, vitals, medication reference, clinical hand-off.

Municipality

Telemedicine Bridge — nurse-led intake, shared bilingual record, remote specialist escalation.

Pharmacy

Pharmacology — HOT-code-native drug reference, interaction checking, pharmacist-review workflow.

Large hospital

Hospital Operations — bed occupancy, equipment booking, shift coordination, clinical team view, operational dashboards.

See the platform in your environment.
One workflow, end-to-end.

20-minute walkthrough with KodaSōken engineering. We open the platform on your real operational pain point and run one workflow end-to-end. No deck. No slides. Your data, your workflow, your questions.

Platform — KODA KENKŌ