Governed medical AI.Secure, auditable, responsible.
Human approval gates. Role-based access. Append-only audit trail.
KODA KENKŌ is built to earn the trust of hospitals, universities, municipalities, doctors, lawyers, and public-health organisations. Governance is not a feature added after the fact — it is the substrate the platform runs on.
Human approval gates
AI agents prepare.
Professionals decide.
No clinical artefact is finalised without a human reviewer. Every workflow in the platform — SOAP draft, prescription preparation, referral letter, intake summary, claims preparation, telehealth escalation, home-care note — moves through a structured approval gate before it enters the operational record.
The reviewer is recorded. The timestamp is recorded. The content before and after the review is recorded. The approval is a load-bearing part of the workflow, not a checkbox.
Roles, audit, traceability
Different access.
Same record. Full trail.
Clinician, nurse, pharmacist, medical clerk, administrator, auditor — each role sees the operational surface they need and only the operational surface they need.
- Role-based accessGranular permissions per role. Audit-only roles for compliance and quality teams. Read-only roles for medical educators and researchers.
- Append-only audit logsEvery action, every approval, every change — recorded immutably. Logs export to JAHIS-aligned formats for institutional audit and regulatory review.
- Workflow traceabilityEnd-to-end traceability from raw input → AI draft → reviewer → approval → final artefact. Every link in the chain inspectable.
- Data controlThe institution retains data ownership. Export at any time in standard formats. Delete at any time within retention-policy constraints.
Deployment & residency
Local. Private. Country-specific.
Wherever the institution’s data needs to live.
Healthcare data carries jurisdictional and institutional constraints that consumer-grade AI deployments cannot meet. KODA KENKŌ deploys to the topology each institution requires — central cloud, on-premise, edge nodes, or hybrid — and the deployment topology is itself part of the governance surface.
Local / private deployment
Full platform inside the institution’s perimeter. Same modules, same governance, same audit surface. Designed for hospitals and public-health networks where data cannot leave the network.
Country-specific deployment rules
Deployment respects jurisdictional data-residency requirements — Japan (APPI, MHLW), Brazil (LGPD), EU (GDPR), and other markets — applied at the deployment topology level, not at the application layer.
Edge & offline operation
Local-first workflows survive intermittent connectivity. Secure synchronisation reconciles edge state with the central platform under full audit when connectivity returns.
Professional responsibility
What KODA KENKŌ is.
And what it is not.
KODA KENKŌ is a structured operational layer that helps medical professionals document, coordinate, and deliver care. It is not a clinical decision-maker. The boundaries of medical responsibility belong to the licensed professional and the institution that employs them — never to the platform.
What it does
Drafts, summarises, retrieves, organises, and routes clinical and administrative artefacts to the professional who approves them. Records the approval. Preserves the trail. Operates under institutional governance.
What it does not do
Does not diagnose, prescribe, dispense, approve, or finalise medical decisions. Does not replace the clinician, the nurse, the pharmacist, the medical clerk, or the administrator. Does not act outside the human review chain.
Institutional governance model
The institution sets the governance policy — roles, approval thresholds, retention windows, audit cadence, regulatory disclosure surface — and the platform executes within it. Configuration is institutional, not vendor-controlled.
Built for institutional review.
Open to your compliance team.
Speak directly with KodaSōken engineering and the governance team. Bring your compliance, legal, and information-security questions — we’ll answer them on the platform, not in a deck.