Skip to content

Subprocessors

Every EDFlow sub-processor with its purpose, whether health information can reach it, the data categories, its location and when it applies, from the single list shared with the privacy page and the security review pack.

This table is generated from the single sub-processor list used by the privacy page, the PIA inputs and the security review pack, so they always agree.

Sub-processorPurposeHealth information?DataLocationWhen it applies
Amazon Web Services (self-hosted Convex, RDS, KMS)Database and backend for hospital tenantsYesVisit data needed to run the service (minimum necessary)Canada (ca-central-1; ca-west-1 for disaster recovery)Hospital production deployments
Convex, Inc.Managed backend for the showcase and developmentNoSynthetic data onlyUnited StatesNon-production deployments only
VercelWeb delivery and server functionsNoNo PHI by design; authentication tokens in transitFunctions in Montréal (yul1); global CDN for static filesEvery deployment
Expo Push (with Apple APNs and Google FCM)Push notificationsNoDevice push tokens; generic notification textUnited StatesWhen push notifications are on for the site
TwilioSMS (share links, updates, verification codes)NoPhone numbers; generic message text with no hospital or patient nameUnited StatesWhen SMS is on for the site
ResendEmail (staff invitations, password resets, summary links)NoEmail addresses; generic message textUnited StatesWhen email is configured
Microsoft Entra IDStaff single sign-onNoStaff identity onlyThe hospital's own tenantWhen the hospital enables SSO
Vercel AI Gateway (Anthropic, Amazon Bedrock, Google Vertex AI)AI features, zero data retentionNoScrubbed prompts; no identifiersUnited States (zero data retention)Only for sites that approved AI phase 2 (US processing, zero data retention)
OpenAI (speech transcription)Web voice input in the showcaseNoAudio from synthetic demonstrationsUnited StatesWeb voice only; off for hospital tenants until approved

Notes

  • Only the database host receives health information by design. Push, SMS and email carry generic text and opaque links; SMS providers necessarily receive the phone number of a patient or family member who opts in.
  • AI providers receive patient-derived data only for sites whose privacy office has approved AI phase 2, under zero data retention and with no training on the data. Web voice transcription stays off for hospital tenants until its conditions are met.
  • Optional and env-gated: push, SMS, email, SSO and AI can each be turned off per site. Without them, the service falls back to in-app delivery.
  • Showcase-only processors never see hospital data.

Change notice

New sub-processors, or a change in what one receives, are announced to each custodian in advance, with the updated PIA inputs. Flow-down terms (confidentiality, breach notice, residency where applicable) apply to every sub-processor that can receive personal information.

Last updated on

Was this page helpful?

On this page