01About this list#
A subprocessor is a third party that processes customer data on Modulon's behalf to help us provide the service. We choose each one carefully, review its security before we sign, and bind it by contract to protect the data it handles.
Each clinic's data is kept in its own region, and handled only by the subprocessors for that region. Every subprocessor that handles patient data is bound by the same restrictions our Business Associate Agreement or Data Processing Agreement places on Modulon, including that it may not use the data to train its models.
02Current subprocessors#
United States
For clinics in the United States. Patient data is stored and processed in the United States.
| Provider | Purpose | Patient data |
|---|---|---|
| Google CloudUnited States | Hosting, databases, file storage, backups and encryption keys | Yes,under a BAA |
| OpenAIUnited States | Language and speech models for calls, messages, transcription and drafting | Yes,under a BAA |
| TwilioUnited States | Phone numbers, calls and text messages for the receptionist and patient messages | Yes,under a BAA |
| StediUnited States | Insurance eligibility checks, claims, claim status and remittance | Yes,under a BAA |
| StripeUnited States | Patient payments, paid out to each clinic's own account | Paymentdetails only |
European Union and United Kingdom
For clinics in the EEA, Switzerland and the UK. EU clinics' data is stored in Germany, and UK clinics' data in London.
| Provider | Purpose | Patient data |
|---|---|---|
| Google CloudFrankfurt and London | Hosting, databases, file storage, backups and encryption keys | Yes,under a DPA |
| OpenAIEuropean Union | Language and speech models, under European data residency | Yes,under a DPA |
| TwilioIreland | Phone numbers, calls and text messages, under European data residency | Yes,under a DPA |
| StripeIreland | Patient payments, paid out to each clinic's own account | Paymentdetails only |
Gulf
For clinics in the six Gulf states. Data for the UAE, Qatar, Saudi Arabia and Kuwait is stored in the clinic's own country; data for Bahrain and Oman is stored in the UAE.
| Provider | Purpose | Patient data |
|---|---|---|
| Microsoft AzureDubai, Doha,Riyadh, Kuwait | Hosting, databases, file storage, backups and encryption keys | Yes,under a DPA |
| Azure OpenAIDubai, Doha,Riyadh, Kuwait | Language and speech models, run in the clinic's country | Yes,under a DPA |
| Local carrierClinic's country | Calls and text messages, through a licensed operator named in the clinic's order form | Yes,under a DPA |
Every region
Services Modulon uses to run its own business, which hold no patient data.
| Provider | Purpose | Patient data |
|---|---|---|
| Google WorkspaceUnited States | Modulon's own email, documents and staff sign-in | No |
| StripeUnited States | Clinics' subscription billing | No |
03Notes on specific providers#
AI models
Our AI providers process patient data under a Business Associate Agreement or Data Processing Agreement and a zero data retention arrangement: they do not store the content we send, and do not use it to train or improve their models. Modulon sends each request only the information that task needs, to models running in the clinic's region.
Payments
Stripe receives what it needs to take a payment, such as the patient's name, contact details, card and the amount due, but no diagnoses, visit reasons or other clinical information. In the United States, HIPAA exempts payment processing of this kind, so Stripe does not sign Business Associate Agreements, and Modulon keeps clinical detail out of every payment it creates. Card details go straight to Stripe and never touch Modulon's servers.
Modulon uses Google Workspace for its own business email. Notifications that the platform emails to clinic staff carry no patient data; they say that something needs attention and link back into the platform, where staff sign in to see it.
04Systems a clinic connects#
When a clinic connects Modulon to its own systems, data moves between Modulon and those systems at the clinic's direction. Those vendors work for the clinic under the clinic's own agreements, so they are not Modulon subprocessors. Typical connections include:
| System | Examples |
|---|---|
| Medical record and practice management systems (EHR, EMR, HIS or PMS) | EZDERM, ModMed, Epic, NextGen Healthcare |
| Health information exchanges | Malaffi, NABIDH and Riayati in the UAE |
| Insurance platforms | eClaimLink and Shafafiya in the UAE, NPHIES in Saudi Arabia |
| Phone systems | RingCentral |
| Email, forms and e-fax inboxes | Google Workspace |
| Prior authorization | CoverMyMeds |
| Payment processors | A clinic's own Stripe or Authorize.net account |
Each connection is granted by a clinic administrator, is limited to the data the clinic's chosen features need, and can be disconnected at any time from the platform's settings.
05Changes to this list#
We update this page before a new subprocessor begins handling customer data, and notify the clinics in the affected region at least 30 days before a new subprocessor begins handling patient data.
A clinic that objects on reasonable data protection grounds can raise its concerns with us, and we will work with it in good faith on an alternative. If we cannot find one, the clinic may end the affected services as its Business Associate Agreement or Data Processing Agreement provides. To be notified of changes, write to hello@modulonhealth.com.
Questions about this page? Write to hello@modulonhealth.com.