What Rhazes reads from your EHR
The exact FHIR resources Rhazes requests, why access is read-only, and how it inherits each clinician's own EHR permissions.
Updated
Read-only, and no exceptions
Every permission Rhazes requests from your EHR is a read permission. There is no write scope, so Rhazes cannot create, amend or delete anything in the source system.
Nothing a clinician does in Rhazes can change your record of truth. Documents Rhazes generates are produced in Rhazes and go back into your systems by whatever route your organisation already uses, with a human deciding.
What it asks for
The clinical resources, in FHIR terms and in plain terms:
| FHIR resource | What it is |
|---|---|
| Condition | The problem list and diagnoses |
| Observation | Results and observations, including vital signs |
| MedicationAdministration | Medication given |
| MedicationDispense | Medication dispensed |
| AllergyIntolerance | Allergies and intolerances |
| Procedure | Procedures performed |
| Immunization | Vaccination history |
| Encounter | Visits and admissions |
| NutritionOrder | Nutrition orders |
| FamilyMemberHistory | Family history |
| QuestionnaireResponse | Completed questionnaires and assessments |
| DocumentReference and Binary | Clinical documents and their content |
Plus Patient and Practitioner, to identify the patient and the clinician signing in.
Permissions are the clinician's own
Rhazes reads as the signed-in clinician, using their EHR identity. It has no independent access and no service account with a wider view.
So the answer to "what can Rhazes see about this patient" is always "exactly what this clinician can see, and nothing else". If your EHR restricts a record, Rhazes is restricted from it by the same rule, enforced by your system rather than by ours.
Scoping it further
The list above is what the integration is capable of requesting. Your organisation decides which of those are actually granted, and a narrower set is a perfectly reasonable place to start.
A first phase of conditions, observations, medications and allergies covers most of what a clinician needs for documentation, and leaves questionnaires and documents for a later conversation once people trust it.
Because this is your own deployment, that scope is set once for your instance rather than negotiated per clinician.
Inside a workflow
A workflow reading the patient record can be pointed at specific resource types rather than everything, so an automated sequence only sees the parts of the record it needs. See Choosing what a workflow can draw on.
Formal documentation
For compliance and data handling documentation to take to your information governance team, see the compliance information on our website or email support@rhazes.ai.