How sharing works in Rhazes
How Rhazes sharing works: view-only access to a chat session and its patient, sent by email, and where everything shared lives.
Updated
Three different things travel between clinicians
It is worth separating them, because they behave differently and people often expect one to work like another.
- A chat session, and the patient attached to it. Sent to a named colleague by email, view only. That is what this collection covers.
- Documents. Shared through a space, where a whole team can read the same guidelines. See What a Rhazes space is.
- Templates and workflows. Published to the community, where anyone can take a copy. A copy is theirs, not a shared original. See Sharing a template with the community and Sharing and installing workflows.
The model for chats and patients
Three rules cover almost everything:
- Sharing is view only. The person you share with can read, and that is all. Nothing they do changes your session or your patient record.
- The patient travels with the session. Sharing a chat that is linked to a patient also gives read access to that patient record. See What the recipient can see and do.
- Access goes one hop. Somebody you shared with cannot share it on to a third person.
Why view only
Because a clinical record needs one owner. Two clinicians editing the same note is how a record ends up with a version nobody can account for.
Read-only sharing gets you the useful part, which is a colleague seeing exactly what you saw, without the part that makes the record ambiguous. If they want to work on it themselves, they can start their own session against the patient, and their reasoning lives in their session under their name.
Where it all lives
The Shared page has three tabs:
- Shared with you. Sessions colleagues have sent you.
- Shared by you. Everything you have sent out, with who has accepted and who has not.
- Patients shared with you. Patient records you can read but not change.