06.16
Practice-system integrations
Executive summary
Integrations synchronise patients, appointments and records with the practice-management systems clinics already run, and expose a FHIR surface. A connector registry, mapping engine and conflict resolver sit behind an inbox, an outbox and a dead-letter queue, so a vendor outage never loses a change. Connectors exist for Dentally, Open Dental, generic FHIR and a local bridge for on-premises systems.
Overview
- PilotOperate · Practice-system integrationsLet Faurenis sit alongside an existing practice system instead of replacing it on day one.
Pipeline
- Inbound changes arrive by webhook or scheduled pull into the inbox.
- The mapping engine translates vendor records; the conflict resolver decides between concurrent edits.
- Outbound changes leave through the outbox with retries; failures go to the dead-letter queue.
- A scheduled reconcile compares both sides.
Data owned
- Connections and mappings
- Holds
- Per-clinic connector configuration
- Inbox, outbox, dead letters
- Holds
- Durable change queues
| Store | Holds |
|---|---|
| Connections and mappings | Per-clinic connector configuration |
| Inbox, outbox, dead letters | Durable change queues |
Models and engines
This module makes no model calls. Everything it computes is deterministic code.
Guardrails
- Every connector runs through the same durable queues.
- The local bridge has its own threat model.
Rollout and status
- ProductionSync engine and queuesInbox, outbox, reconcile on schedule
- PilotVendor connectorsPer clinic
Interfaces
- Consumes
- What
- Vendor webhooks and APIs
- Emits
- What
- Patients, appointments and documents into Faurenis
- Emits
- What
- Updates back to the vendor system
| Direction | What |
|---|---|
| Consumes | Vendor webhooks and APIs |
| Emits | Patients, appointments and documents into Faurenis |
| Emits | Updates back to the vendor system |
Known limits
- Per-connection webhook signature verification is implemented for the reference connector; wiring it into each production connector is open work.
SOURCE OF TRUTH
server/integrations/server/routes/data/fhir.tsdocs/integrations/docs/integrations/local-bridge-threat-model.md