Rolling out Rhazes across a team
How to get a department working the same way in Rhazes, using shared spaces, workflows and templates rather than instructions.
Updated
Consistency comes from shared objects, not from training
You cannot get a department documenting the same way by telling them to. You get it by giving them the same template, the same workflow and the same set of guidelines, and letting the tool carry the standard.
Three things do that work:
- A shared space holding your local guidelines and policies, so everyone's answers are grounded in the same material. See What a Rhazes space is.
- Shared templates, so every discharge summary comes out in the agreed shape. See Sharing a template with the community.
- Shared workflows, so a multi-step task runs the same way whoever starts it. See Sharing and installing workflows.
A rollout that works
- Start with one team and one problem. The discharge summary, the clinic letter, the referral triage. Something everybody does and everybody dislikes.
- Build the shared objects first. A space with the local guidance, a template for the document, and one workflow. Do this before anyone else signs in, so the first thing they see is something that already fits their work.
- Pilot with two or three clinicians who will tell you the truth.
- Fix what they tell you, which is almost always the template.
- Then widen it, with the shared objects already proven.
The failure mode is the reverse: give fifty people access, tell them it is very good, and let each of them discover it alone. Most will try it twice on a busy day and stop.
Nothing is metered, so let people explore
On your own deployment there are no usage caps, so a clinician trying Rhazes on a full clinic cannot run out partway through and conclude it does not work. Say so when you introduce it, because anyone who has used a capped product will assume otherwise.
Give at least two people admin on a shared space
A departmental space maintained by one person becomes unmaintained the day that person rotates. See Rhazes space roles and permissions.
Reviewing how it is going
Clinical audit is the honest way to check whether documentation has actually improved, rather than asking people whether they like it. Audit a sample of notes from before and after against the same standards. See What clinical audit in Rhazes does.
Since audit is available to everyone on your deployment, this costs you nothing but the time to define the standards once.