Agentic FabriqRestrict agents to patients associated with the active encounter, assignment, or approved workflow.
The patient relationship, not employment, grants access — the agent reaches the chart in front of it and no others.
SOLUTIONS / Healthcare
Govern AI agents around patient care and sensitive health data
Limit agents to the right patient, purpose, care team, and clinical action.
01 / IDENTITY02 / POLICY03 / AUDIT
01 / THE CONTEXTAdministrative work,
Administrative work,
with no path into the chart.
Healthcare agents may assist with scheduling, clinical documentation, patient communication, coding, prior authorization, and care coordination. Access cannot be based only on whether someone works for the organization—it has to follow the role and the patient relationship of the person the agent is acting for.
ENCOUNTER NOTE · EXAMPLEACTING FOR · THE TREATING CLINICIAN
- Patient
- R. Okonkwo · MRN ····4417 active encounter
- Assessment
- Drafted by documentation-agent
- Behavioural health
- outside this workflow
- Substance use
- outside this workflow
- Signature
- Reserved for the treating clinician
The chart in the next room belongs to someone else’s patient. This request never reaches it.
02 / IN PRACTICE
Autonomy, with accountability.
ONE CLINIC MORNING · THE SCHEDULING VIEWIllustrative · documentation-agent, acting for the treating clinician
Google CalendarThis clinician’s panelTheir own patients · their own roleEvery other panel in the clinicNo route in from this request
09:00
R.O. · MRN ····4417Follow-up confirmed, patient remindedAllowed. Times, rooms and contact details — the clinical record is not fetched for a scheduling task at all.
Twilio
Twilionot this clinician’s patients
09:30
T.N. · MRN ····8802Moved to 11:00, interpreter rebookedAllowed. The agent works the clinician’s own list, under the clinician’s own permissions, and every change is recorded.
not this clinician’s patients
10:00
R.O. · MRN ····4417Encounter note drafted from the visitHeld. Drafting is the agent’s work; signing is the clinician’s. The note is unsigned until a person puts their name on it.SIGNED BY THE TREATING CLINICIAN
K.M. · another clinician’s patientChart opened from this workflowBlocked. A different clinician’s panel, no treatment relationship here — the request stops before the chart is read.
Example appointments. The panels, purposes of use and signing rules are the ones you set.
03 / WHAT CHANGES
Control, in the details.
Differentiate treatment, payment, operations, research, and administrative access.
Each is its own grant held by different staff and different agents, so a billing agent and a documentation agent reach different parts of the same record.
Limit which portions of a record an agent can retrieve or disclose.
Segment-level scoping keeps sensitive portions of the chart out of workflows that have no need for them.
Keep orders, diagnoses, prescriptions, and patient-facing advice out of the grant.
None of them is an action an agent holds, so anything clinical that reaches a patient or a chart is a licensed clinician’s own act.
Prevent an administrative agent from inheriting clinical access.
Scheduling and billing agents work from demographic and coverage data without a path into clinical records.
Record which person, agent, and source data contributed to an action.
Every action carries an accounting of who and what was involved — disclosure-ready by construction.
THREE LAYERS. ONE DECISION.
The boundary travels with the work.
Explore the context attached to every request.
What is this agent allowed to do?
documentation-agent has a defined purpose and a bounded set of tools.
Whose authority travels with it?
The request acts for treating clinician, using that person’s permissions.
Where does the action land?
The policy applies to the requested action within Active encounter, before the tool executes.
04 / WAYS TO PUT IT TO WORK
Built for your real workflows.
01Clinical documentation
Documentation agents draft from the active encounter, and notes enter the chart under the clinician’s review and signature.
Identify→Authorize→Record
02Patient intake
Intake agents collect and verify one patient’s information at a time, limited to that registration.
Identify→Authorize→Record
03Scheduling
Scheduling runs on demographics and availability, with no clinical record access attached.
Identify→Authorize→Record
04Revenue cycle
Billing and coding agents read the minimum necessary for the claim, with payment-purpose access recorded as such.
Identify→Authorize→Record
05Prior authorization
Authorization agents assemble the request from the patient’s own records; submitting to the payer is not an action they hold, so staff send it.
Identify→Authorize→Record
06Care coordination
Coordination agents work across the care team for their assigned patients, within each member’s role-based scope.
Identify→Authorize→Record
07Research data access
Research use runs under its own purpose and its own grant, separated from treatment and operations access.
Identify→Authorize→Record
QUESTIONS
A closer look.
Do we need to change our EHR or scheduling systems?+
No. Fabriq drops in between agents and the clinical and administrative systems you already run. The EHR stays the system of record; every agent request against it is capped at the acting user’s own role and the grant the agent holds.
Do administrative agents see clinical data?+
No. Administrative and clinical access are separate scopes; a scheduling or billing agent works from demographic and coverage data and has no path into clinical records, even when both connect to the same systems.
How fast can access be revoked?+
Immediately — sessions die on revocation rather than at token expiry, and a disabled agent’s next call fails closed.
Can access follow each user’s role and patient relationship?+
Yes — that is exactly how it resolves. The same documentation agent reads differently for a treating clinician, a scheduler, and a biller, because reach is resolved per person and per purpose, down to segments of the record.
What does the access record look like?+
Every agent action carries the person who asked, the agent that acted, what was touched, and the verdict — one trail you can query when access questions come up.
Where do system credentials live?+
In Fabriq’s vault, injected per call — no shared passwords in bot configs, automatic refresh, and instant cutoff when a connection is removed.