When the output is not what you expected
Why a Rhazes note or answer comes out in the wrong style, misses sections, or draws on the wrong sources, and what to change.
Updated
Start with what kind of wrong it is
Each of these has a different fix, and trying the wrong one wastes time.
It reads like it was written for another specialty
Your profile drives this. Speciality and grade decide how much reasoning Rhazes spells out; country and language drive drug naming, spelling and which guidance it reaches for.
If Rhazes consistently writes at the wrong level or uses the wrong conventions, the profile is almost always the reason. See Completing your clinician profile.
The note is missing sections, or ignores my format
That is the template. A heading with no explanation leaves Rhazes to guess what belongs under it, and anything that must always appear needs to be stated in the template rather than remembered each time.
Generate example output from the template to see what it actually produces. See Creating your own template and Refining and previewing a template.
It answered from the web instead of our guidelines
Check a space is linked to the chat. If one is and it still happened, Rhazes says so explicitly above the answer, and that notice tells you the space contributed nothing. See When your space has nothing to say.
It is too long, or too short
There is a response length setting. See Setting the response length.
The facts are wrong
If it came from a consultation, check the transcript first. A mistake there carries into everything generated from it. See When a transcript is wrong or missing.
Otherwise open the citations and read what the answer was built on. See Citations and sources.
It refused to do what I asked
That is usually deliberate rather than a fault. See When Rhazes declines a request.
If it was unsafe, please report it
Report from the response itself so the exact conversation comes with it. See Reporting an unsafe output or a security concern.