Patient context that carries between visits.
Faurenis Patient Memory helps dental teams maintain longitudinal context — preferences, risk signals, treatment history, open questions, and follow-up items — without forcing clinicians to reconstruct the story every time.
Memory timeline
Four memory types, one continuous thread.
- On intakeRisk
Penicillin sensitivity flagged — confirmed at first visit.
- Mar 2026History
Composite #36 placed; monitoring at recall.
- Apr 2026Preference
Prefers morning appointments; sensitive to noise.
- May 2026Follow-up
Follow up on mouthguard fit at next visit.
- Clinician-editable
- Audit-ready
- Clinic-scoped
- Consent-aware
The workflow problem
The story restarts every visit.
Important patient context lives across old notes, scanned documents, and team memory. Each new visit is partly a search exercise.
- 01
Context lives in too many surfaces.
Notes, scans, perio history, and informal team memory all hold pieces of a patient’s story.
- 02
Patients repeat themselves.
Preferences, allergies, prior conversations — patients are asked to re-state them on every visit.
- 03
Follow-up commitments slip.
"We’ll check that at next visit" rarely makes it into a structured surface the next clinician can see.
- 04
New team members start from scratch.
A locum, a new hygienist, a covering specialist — each one rebuilds the picture from raw notes.
How Faurenis solves it
Four memory types. One review surface.
Faurenis treats patient memory as a typed, reviewable artefact — distinct from raw notes. The clinician decides what enters memory, what gets edited, and what should not.
Longitudinal patient summary
A continuously-updated view that survives across visits and across team members.
Risk and preference memory
Allergies, sensitivities, comfort preferences — named once, surfaced when relevant.
Treatment history continuity
Prior procedures, current monitoring, and outstanding items linked to the relevant teeth and surfaces.
Visit-to-visit carryover
Open questions and follow-up commitments resurface in the next visit’s opening view.
Missing data detection
Faurenis quietly flags when an expected memory item (e.g. allergy review) hasn’t been updated in a meaningful timeframe.
Follow-up context
Memory feeds the patient communication surface so recall messages know what to remind the patient about.
How it works
Memory grows on review, not on assumption.
Nothing enters patient memory without a clinician’s explicit pass. Memory is always editable, always auditable, always clinic-scoped.
- 01
Faurenis captures approved context
During an active visit or review, Faurenis proposes memory items grounded in clinician-approved notes.
- 02
Items are typed and structured
Each proposed item is typed (risk, history, preference, follow-up) and linked to its source note.
- 03
Clinician reviews and edits memory
Clinician-editableThe clinician edits, accepts, or rejects each item before it joins the structured memory layer.
- 04
Future visits surface relevant memory
Opening a future visit brings the relevant memory subset into view — no manual lookup.
- 05
Memory feeds documentation and communication
The same memory surface is read by Faurenis Copilot, Ambient Scribe, and the patient communication workflows.
Why it compounds
Continuity becomes a measurable property of the clinic.
Illustrative shape of how memory accumulates across visits and reduces context-reconstruction time per visit.
Example workflow data
Context-reconstruction time across visits.
Stylised view of how a clinic’s opening-visit context lookup time evolves over a six-visit horizon, with and without structured memory.
Safety and governance
Memory is patient data. Treated accordingly.
Memory is one of the most sensitive workflows in the product. The controls below describe how Faurenis handles it.
Clinic-scoped memory
Memory never leaves the clinic’s data boundary. No cross-tenant retrieval, ever.
Clinician-editable, always
Every memory item can be edited or removed by the responsible clinician.
Separation of raw notes and memory
Raw notes remain the source of truth. Memory is a typed, derived layer — not a replacement.
Audit log
Every memory change is logged — who, when, and what the prior state was.
Sensitive data handling
Sensitive categories (medications, sensitivities, conditions) are handled with extra care in the review surface.
Patient data rights
Export, correction, and deletion workflows treat memory as part of the patient’s data footprint.
Built around the team
Continuity for whoever opens the visit.
Memory makes the second clinician as fluent as the first. The roles below describe where it shows up.
For dentists
Open a visit knowing the prior conversation, the prior decision, and the prior commitment.
For hygienists
Recall visits start with the right context already in view — preferences, sensitivities, follow-ups.
For specialists
A locum or covering specialist picks up the patient’s thread without trawling the notes folder.
For practice managers
Memory completeness becomes a managed signal across the team — not informal recall.
For compliance and admin
A clear, auditable picture of what the clinic has structured into memory about each patient.
Continue exploring
Designed to work together.
Build clinical continuity
Memory is the surface every other surface gets better from.
Bring a returning-patient scenario. We will walk through how memory accumulates, how it is reviewed, and how it shows up in the next visit.
Pilots run for 3 weeks. Designed for dental teams. AI-assisted, clinician-controlled.
Memory items shown here are illustrative. In Faurenis, every memory item is clinician-reviewed, clinic-scoped, and editable at any time.