Skip to content

Product

How MedicalBot is designed to work

A single operating model — Ask, Assess, Route — governs every MedicalBot workflow, from the public demo to a future secure clinical environment.

Operating model

Ask. Assess. Route.

  1. 01 · Ask

    Capture the request

    A workflow interaction comes in — a message, call, form, or scheduled trigger. The system captures only the fields a configured workflow actually needs.

  2. 02 · Assess

    Apply configured controls

    The request is evaluated against organisation-defined knowledge, workflow rules, policy constraints, and escalation conditions set before go-live — not open-ended model judgment.

  3. 03 · Route

    Act, ask, or hand off

    The workflow returns an approved information response, requests clarification, starts an approved automation, schedules a next step, or routes the interaction to a human.

Where it runs

Three environments, one model

The same Ask, Assess, Route pattern applies across three clearly separated planes. This repository implements the first two.

Public demonstration

This website and the /demo previews illustrate the Ask → Assess → Route pattern with sample data. No PHI is collected here, and nothing here is a live clinical system.

Configured organisational workflow

Once an organisation defines scope, policies, and escalation rules, the same pattern runs against real operational workflows — still without PHI unless a secure environment is in place.

Future secure clinical environment

PHI processing, enforceable audit, and EHR/FHIR writeback belong to a dedicated secure application plane, tracked separately from this public site and implemented only under customer agreements.

Do not submit protected health information (PHI) on this website.

Architecture preview

See the pattern in action

Interact with labeled demos that illustrate console patterns without implying a live clinical system.

Visit the architecture preview for interactive product education, or the product demo chat to try a scoped conversation.

FAQ

Common questions about the operating model

No. It is an operating model for governed workflow automation — communication, scheduling, documentation support, and operational routing. It does not diagnose disease or prescribe treatment.

See MedicalBot in a guided demo

Book a product walkthrough with our team. We discuss architecture, governance patterns, and fit for your organization — without collecting PHI.

Do not submit protected health information (PHI) on this website.