Documentation navigation
How Menaela works
Menaela reasons about a request, but it does not become the clinic database. Facts and actions still come from structured context and explicit product tools.
A request starts with intent, not a button
A staff member can ask “find the next ECG slot this week” instead of opening several screens. A patient can write “anything earlier?” instead of starting a new booking flow.
Menaela first has to understand what the person is trying to do and which previous context still matters.
Then it retrieves relevant context
The assistant should not load every record in the clinic into every request. It retrieves the context needed for the current workflow: clinic configuration, provider/service facts, patient or appointment information and relevant previous conversation state.
Actions happen through explicit tools
A language model can propose what to do. It should not directly edit production tables because the text sounds confident.
Operational actions are exposed as constrained capabilities such as searching availability, retrieving a patient, booking or moving an appointment, or reading configured clinic information. The application remains responsible for validation and data integrity.
Some actions require confirmation or handoff
A useful assistant is not the one that always acts. It is the one that knows when enough context exists to act safely.
If the service is ambiguous, the patient identity is uncertain, a payer answer is not supported, or a medical judgement is required, Menaela should clarify or escalate.
