Compliance designed in, not bolted on.
Faurenis helps dental teams manage consent, audit logs, AI review, residency controls, data access, and governance workflows from the foundation of the product.
Frameworks
- GDPR · ready
- EU AI Act · pathway
- MDR · aware
- ISO 27001 · pathway
- HIPAA · pathway
Audit · today
- 14:02Consent captured · ai-analysis
- 14:08Scribe draft created · visit V-4421
- 14:11Clinician reviewed and approved
- 14:11Record updated · patient timeline
- 14:11Audit event stored
Controls
- Residency
- EU
- Access roles
- 4 active
- AI review queue
- 3
- Last export
- 2 days
- Audit-ready
- Consent-aware
- Role-scoped
- EU-residency by default
The workflow problem
Compliance shouldn’t be a Tuesday-afternoon scramble.
Most clinical AI bolts on consent, audit, and access controls after the fact. Faurenis treats them as foundations.
- 01
AI workflows need clear oversight.
Without a queue, AI-generated outputs slip through without explicit review.
- 02
Patient data requires careful access control.
Roles, scopes, and SLAs around access need to be observable, not implicit.
- 03
Audit evidence is hard to reconstruct later.
When a regulator asks, "who did what when," the answer should already exist.
- 04
Compliance can’t be an afterthought in clinical software.
Designed-in trust is the only kind that survives a real review.
How Faurenis solves it
Eight controls, woven into the product.
Each control below isn’t a settings page — it’s a property the rest of the surface enforces.
Audit logs
Every consent, draft, review, save, and export is logged with timestamp + reviewer identity.
Consent-aware workflows
No retrieval without a basis; every AI action checks current consent before proceeding.
AI review queue
AI outputs land in an explicit review surface. No silent merges into the record.
Data residency controls
EU-residency by default; configurable region scope per clinic.
Role-based access
RBAC + per-feature scopes; the principle of least privilege is the default.
Export and deletion readiness
Patient-data export + erasure workflows ready for GDPR-style requests.
Security / compliance dashboard
A live operating view of governance posture — not a quarterly PDF.
Risk and governance documentation
Per-clinic governance artefacts kept current alongside the product.
How it works
A six-step posture, lived every day.
Compliance isn’t an event. It’s the shape of the day-to-day workflow.
- 01
Configure clinic governance
Set residency, retention, consent posture, and AI review SLAs per clinic.
- 02
Set team roles and permissions
Map clinical and admin roles to feature scopes. Least privilege by default.
- 03
Capture consent and workflow events
Every relevant action lands as a structured event with a reviewer attribution.
- 04
Review AI-generated outputs
Clinician-controlledNo AI output merges into the record without an explicit review state.
- 05
Export audit evidence when needed
Per-incident, per-patient, per-window exports ready when asked.
- 06
Monitor compliance posture
A live dashboard of consent coverage, review SLAs, residency drift, and export volume.
Why it matters
Posture you can show, not posture you have to construct.
Illustrative shape of the controls posture Faurenis holds across the audit surface. Real numbers depend on clinic configuration.
Example workflow data
Controls implemented vs in-progress vs planned, per area.
Stylised view of Faurenis’s controls posture across five regulatory areas.
Safety and governance
Every control above is a property of the product, not a checkbox.
The controls below are the day-to-day surfaces that enforce the posture.
Clinician review required
AI outputs cannot merge into the record without explicit clinician approval.
Review state on every output
Draft / reviewed / approved is a first-class state model.
Audit event for every action
Consent, draft, review, save, export — each lands as a structured event.
Consent posture per patient
Granular per-purpose consent with revocation paths.
Data residency enforced
EU-by-default; region scope configurable per clinic, never inferred.
RBAC + per-feature scopes
Roles map to feature scopes; the surface refuses out-of-scope actions.
Versioned outputs
Every plan, note, and document carries version history with reviewer attribution.
Built around the team
Compliance is a posture the whole team holds.
The roles below describe where the compliance surface shows up.
For compliance and admin
Live audit posture + export-on-demand + per-patient consent visibility.
For IT and security
Residency posture + RBAC + access logs surfaced as operating signal.
For clinic owners
Compliance posture visible at the operating level — not buried in legal.
For dentists
Review-before-record is the default; the safe path is the easy path.
For practice managers
Validation queues + AI review SLAs visible alongside operating signal.
Continue exploring
Designed to work together.
Review Faurenis’s trust model
Bring your security checklist — we’ll walk it line by line.
A 30-minute conversation with Faurenis’s security and compliance team. Real artefacts, real residency posture, real audit examples.
No silent merges. No autonomous record updates. Audit-ready by design.
Audit examples shown here are illustrative. Faurenis’s actual posture per clinic is configurable and audit-ready on demand.