dr connecttrust← Back to the trust page
OPEN · ARCHITECTURE OVERVIEW

How the service is built

Categories, not components. The detailed architecture is in the security pack, available on request.

Your clinic
Clinicians, the desktop app, your record system and your ambient scribe.
⇄ encrypted
DR CONNECT · YOUR REGIONAL DEPLOYMENT
Edge
Web application firewall in front of everything: standard rule set, bot and rate limits. Encrypted connections end inside your region.
Application hosting
Managed platform, no public address, modern TLS. Clinical content in memory only.
Identity
Organisation sign-in, role-scoped access, licence checks.
Secrets
Held in a vault. Services use managed identity, not passwords.
Data stores
Private network only. Sign-in, licence and opaque references; stored credentials encrypted with a key per organisation. No clinical content at rest.
Monitoring
Health checks and alerts, including the edge. Technical events only.
Status page
Hosted apart from every regional deployment, so it keeps answering if a region does not. It checks each region from outside every minute and holds public status history and the e-mail addresses of people who subscribe. No customer or patient data.
IdentityIn transitEdge firewallPrivate networkSecretsCredentials encryptedAt restMonitoring