Questions that reach you
What arrives is never a chat history. It is a sheet with the question, the plan it touches, the context from the chart, what the patient already heard, and a reply you approve.
Mosaic is meant to reduce the number of times a patient needs you, and to compress the times that remain. The Inbox is the second half of that sentence.
What a request contains
- The question in the patient's own words.
- The point of the plan it belongs to, with the date you signed it.
- The context from the chart that bears on it, and only that.
- What Mosaic already told her, so you know what she has heard.
- A draft reply, written from the plan and the chart.
You approve, you edit, or you ask her to come in. Nothing goes to a patient before you have seen it.
A request in the Inbox: a patient reporting muscle aches on a statin, with the plan item, the CK before the start, the three things Mosaic already said, and a draft reply below.
When you see them
Requests do not push. They collect, and the Inbox shows them once in the morning and once in the afternoon, with anything a patient described as a symptom marked. The practice decides the rhythm, not the patient.
What it costs her
Reading a question is part of her treatment and costs her nothing. Where your answer becomes a service outside the statutory catalogue, the price is named before it happens and she agrees in writing first, as German law requires. Mosaic never makes that decision; it prepares the document and shows her the price.
A question can only reach you if you opened that door for that patient. With the switch off she still receives everything you share; she simply cannot write to you through the app.