Working with patients in a workflow
Read patient details and clinical records inside a Rhazes workflow, or create a new patient record from what the run found.
Updated
Reading a patient
Patient details brings in the name, date of birth and identifiers. Patient record brings in the clinical information held on them.
Between them, a workflow works on a real patient rather than on whatever happens to be pasted into a chat, which is what makes automation worth having on clinical work at all.
Using those values further down
Anything these steps produce can be referred to by later steps, so a document can carry the patient's details and a question can quote them back to you. See Passing values between steps.
Creating a patient
A Create patient step makes a record from what the workflow gathered. That is how an intake workflow ends with the patient actually on your list rather than with a summary you then have to transcribe.
It does not attach them to your chat by itself
A workflow that creates a patient does not silently link them to the chat it ran in. The result shows the new patient with a button to attach them, so that stays your decision.
That restraint is deliberate. Attaching a patient changes what Rhazes has in context for everything that follows, and it should not happen without you knowing it happened.
Check before you build on it
A workflow that creates patient records can create the wrong one, particularly when it is working from a document rather than from your EHR. Confirm the identifiers before the record is used for anything. See Adding a patient in Rhazes.