Medical clinic

What the platform does in a clinic and where the medical line runs

What this actually is

Machinery of its own — patient enquiries, a service catalogue, appointment slots and clinic rules — is built in this release for exactly one industry: dentistry. If you run a dental practice, look at the template page instead.

For a clinic of any other profile these are general modules configured for intake and booking. There is no medical part in them, and that is not a gap in configuration: the product stores no diagnoses, prescriptions, test results or images — there is not a single column for them in the database.

Which modules are switched on

The set switched on for a clinic:

• Support: patient requests with a queue, a deadline and handover to a person.
• Knowledge base: confirmed answers about services, preparing for a visit, documents and payment.
• Internal operations: requests, tasks and approvals inside the clinic.
• Analytics: monthly series with a named source for every number.

Which AI employees work here

The lines of work that have something to do in a clinic:

• Support — the subject of a request and a drafted reply from the confirmed base.
• Knowledge — outdated answers and answers that contradict each other.
• Operations — requests handled by the rules, and deadlines.
• Quality — reviewing conversations against a list of criteria.

Where the medical line runs

The platform gives no medical advice and takes no part in treatment. It works with the administrative part: who got in touch, about what, what was answered and when.

The free text of a request is read by a rule that marks what is written as possibly clinical. Marked text is not passed into a draft and does not reach an export until a person has looked at it. That is a rule, not a medical classification, and it is named exactly that way.

Patient contacts are stored but shown masked to every role without exception, and the journal records the fact «a telephone number exists», not the number itself.

What is not in this build

The lines below are about how the product is built, not about a backlog.

• Diagnoses, history, treatment plans, prescriptions, images and test results — there are no columns for them.
• Confirmation of conformity with medical or any other legislation: the platform has no such status and has not been audited.
• Sending messages to patients: the platform writes to nobody on its own.
• Integration with a medical information system: there is no connector.

What is the same in every industry

Company isolation enforced by the database, a closed register of permissions, an immutable journal, and a second person signing off where the action calls for it. That is how the platform is built, and it does not depend on which modules are switched on.

In every industry an AI employee produces a draft. Sending a message, paying, signing and deciding about a person are things the platform does not do — in no mode and under no role.

Basis: docs/MODULE_TRUTH_TABLE.md §2, docs/PRIVACY_BOUNDARIES.md. This page describes what exists in this build, not what is planned.