What the recipient can see and do
Exactly what a colleague gets when you share a Rhazes session: the conversation, its files, the linked patient, and where access stops.
Updated
What they can see
- The whole conversation, including everything Rhazes produced in it.
- The files attached to that session.
- The linked patient record, if the chat has one. Its clinical information and its files, read only.
What they can do with a shared patient
More than you might expect, and all of it read only or their own:
- Read the clinical information and open the files.
- See the sessions you have shared with them for that patient, rather than hunting through their session list.
- Start their own chat session against that patient. Their conversation is theirs, under their name, and yours is untouched.
That last one is the useful part of a handover. The colleague taking over does not inherit your session; they get the context and start their own reasoning.
What they cannot do
- Change your session. Not adding a message, not editing one, not deleting it.
- Change the patient record. Not editing the clinical information, not adding files, not deleting it.
- Share it on. Access stops with them.
Everything about the record stays with the clinician who owns it.
What this means clinically
A shared session is a view of your reasoning at a point in time. It is not a shared workspace, and it is not a handover document.
So share it the way you would talk a colleague through a case: as the material, with the decision still theirs. Anything they act on is their own clinical decision, made on their own accountability, exactly as it would be if you had described the case to them in person.
Where it appears for them
Under Shared with you on the Shared page, and patients under Patients shared with you. See When a colleague shares with you and Patients shared with you.