"Your medical AI assistant."
Tandem is an AI-powered medical assistant for doctors, therapists, nurses, and healthcare facilities.
The tool supports the preparation, documentation, and follow-up of treatment appointments, creates medical notes and documents in seconds, suggests suitable diagnosis and procedure codes, and allows editing via voice input. According to the website, Tandem supports over 50 specialties and integrations with more than 100 medical systems.
Tandem Health
Your medical AI assistant
Location: Sweden ⓘ Tandem Health AB: Malmskillnadsgatan 44A, 111 57 Stockholm, Sweden. German legal notice / local company: Tandem Health Global GmbH, P6, 26, 68161 Mannheim.
Enterprise – everything in Pro plus custom integrations, onboarding/training/rollout, prioritized support, enterprise authentication, and detailed usage reports. Other Enterprise For larger practices and care organizations; includes everything in Pro plus custom EHR integrations, full onboarding, training & rollout, priority support, enterprise authentication, and detailed usage reports.
Custom Integrations Custom integrations into medical record systems if a system is not yet supported.
Target audience
Tandem is primarily aimed at professional users in healthcare: physicians, therapists, nursing staff, solo practices, MVZs, clinics, and larger care organizations. The tool is particularly well suited for teams that want to speed up clinical documentation, coding, and transfer into existing medical systems without covering a consumer use case. Regulated organizations in Europe with a strong focus on data protection are also clearly part of the core target audience.
Outstanding features
Among the most notable features are the automatic creation of medical notes and other documents from consultations, suggestions for diagnosis and procedure codes, editing via voice input, and 1-click transfer into more than 100 medical systems. In addition, there are current product developments such as “Personalised Memories,” meaning a more personalized writing style of the system, as well as the expansion of administrative team workflows through “Tandem Secretary.” Functionally, this is more than a pure transcription service.
Main application areas
Tandem becomes interesting wherever medical documentation takes up a lot of time: in practices, outpatient clinics, hospitals, specialized departments, and in cross-organizational care processes. Typical scenarios include physician and treatment notes, referrals, patient letters, ward round summaries, coding support, and structured handover into practice or hospital software. Officially, Tandem is also positioned for more than 50 specialties and different care settings.
Use & notes
Use follows a SaaS model: conversations or consultations are processed, resulting in notes, documents, and codes that are reviewed by specialist staff and transferred into existing systems. From a data protection perspective, it is important that Tandem typically acts as a data processor for platform data on behalf of the respective healthcare institution, that audio is not stored according to the security page, and that patient data is processed in Europe according to the product page. Before procurement, however, the specific DPA/AVV, the list of subprocessors, transfer mechanisms, and the specific usage context should still be reviewed separately, because the general Privacy Policy does not completely rule out international transfers for certain data categories.
| Target audience | Assessment |
|---|---|
| Doctors / clinicians | Very suitable – Tandem listens to consultations, creates structured notes, documents, and codes for medical review. |
| General practices / specialist practices | Very suitable – for less documentation effort, faster creation of physician letters/notes, and EHR transfer. |
| Hospitals / care organizations | Very suitable – Enterprise offers integrations, rollout, training, reporting, and authentication. |
| European healthcare providers | Very suitable – Tandem is geared toward European healthcare regulation, EU data residency, and local patient data protection laws. |
| Private individuals / patients directly | Not suitable – Tandem is a clinical documentation tool for medical professionals, not a patient symptom checker. |
| Privacy-sensitive organizations | Well suited, but subject to review – Health data is particularly sensitive; positives include EU data residency, no training on patient data, DPA, and certifications. |
Hosting & Data
1) On-prem / local hosting
Meaning: The company operates the solution on its own hardware or within its own infrastructure. In the strictest sense, not only the application runs locally, but ideally the model as well.
2) Private cloud / data center
Meaning: The solution runs in a dedicated or more clearly separated cloud environment, often with a hosting provider or hyperscaler, but in a German data center or in a particularly controlled environment.
3) EU SaaS / managed
Meaning: The provider operates the solution itself as a service. The company uses the tool as a ready-made cloud service, ideally with EU data residency.
4) Hybrid
Meaning: One part of the processing remains internal / local / in a private cloud, while another part runs in an external cloud or EU SaaS.
5) AVV / DPA
Meaning: This is the data processing agreement or Data Processing Addendum. It governs that the provider processes personal data on behalf of the customer and is bound by the customer's instructions.
6) No training
Meaning: The provider does not use your prompts, uploads, attachments, chat histories, or outputs for training or improving the general model — ideally excluded by contract.
7) Open-source / transparency path
Meaning: There is a path toward greater technical transparency and sovereignty, for example through:
- open models
- documented components
- self-hostable parts
- traceable architecture
- export / switching options
| On-prem / local hosting | ❓ |
| Private cloud / data center | ⚠️ |
| EU SaaS / Managed | ✅ |
| Hybrid | ❓ |
| DPA / AVV | ⚠️ |
| No training on customer data | ✅ |
| Open source / transparency path | ❓ |
On-Prem / local hosting: unclear
An on-premise, local, or self-hostable deployment was not specified on the website.
Private Cloud / data center: partial
European data centers and 'enterprise-grade security agreements' are mentioned. This indicates a controlled hosting environment, but a dedicated private cloud or customer-specific data center option is not clearly described on the website.
EU SaaS / Managed: covered
The website describes Tandem as an online-delivered service and explicitly states that patient data is processed and stored in European data centers or remains within the EU.
Hybrid: indirect / not available
A hybrid operating model with partly local/internal and partly external processing was not specified on the website.
DPA / DPA: partial
The privacy policy explicitly mentions a 'Data Processing Agreement (DPA)' or equivalent contractual terms and describes processing according to documented customer instructions. However, the DPA itself was not publicly accessible on the website.
No training: covered
The website explicitly states that Tandem does not train AI models using patient or personal data and that the data is never used to train AI.
Open source / transparency path: indirect / not available
Open-source components, open models, self-hostable parts, or any other documented transparency path were not specified on the website.
Data processing
According to the website, Tandem operates as a managed cloud service. Patient data is processed and stored exclusively in Europe or within the EU. Audio is processed in real time and deleted after transcription. Tandem describes itself as a data processor for platform data on behalf of the respective healthcare institution and refers to a DPA for this. Specific subprocessors, specific data center countries, and technical details on hosting architecture or data flows are not specified on the website.
Conclusion
For users in Europe, Tandem appears in its best-documented form to be an EU-oriented SaaS service with good data protection and compliance signals. However, central details are missing from the publicly accessible website for a truly reliable final EU/EEA assessment, especially regarding subprocessors, specific server locations, and the specifically reviewable DPA. Therefore, overall 'conditional' rather than 'yes'.
Sources
| On-prem / local hosting | ❓ |
| Private cloud / data center | ⚠️ |
| EU SaaS / Managed | ✅ |
| Hybrid | ❓ |
| DPA / AVV | ⚠️ |
| No training on customer data | ✅ |
| Open source / transparency path | ❓ |
On-Prem / local hosting: unclear
An on-premise, local, or self-hostable deployment was not specified on the website.
Private Cloud / data center: partial
European data centers and 'enterprise-grade security agreements' are mentioned. This indicates a controlled hosting environment, but a dedicated private cloud or customer-specific data center option is not clearly described on the website.
EU SaaS / Managed: covered
The website describes Tandem as an online-delivered service and explicitly states that patient data is processed and stored in European data centers or remains within the EU.
Hybrid: indirect / not available
A hybrid operating model with partly local/internal and partly external processing was not specified on the website.
DPA / DPA: partial
The privacy policy explicitly mentions a 'Data Processing Agreement (DPA)' or equivalent contractual terms and describes processing according to documented customer instructions. However, the DPA itself was not publicly accessible on the website.
No training: covered
The website explicitly states that Tandem does not train AI models using patient or personal data and that the data is never used to train AI.
Open source / transparency path: indirect / not available
Open-source components, open models, self-hostable parts, or any other documented transparency path were not specified on the website.
Data processing
According to the website, Tandem operates as a managed cloud service. Patient data is processed and stored exclusively in Europe or within the EU. Audio is processed in real time and deleted after transcription. Tandem describes itself as a data processor for platform data on behalf of the respective healthcare institution and refers to a DPA for this. Specific subprocessors, specific data center countries, and technical details on hosting architecture or data flows are not specified on the website.
Conclusion
For users in Europe, Tandem appears in its best-documented form to be an EU-oriented SaaS service with good data protection and compliance signals. However, central details are missing from the publicly accessible website for a truly reliable final EU/EEA assessment, especially regarding subprocessors, specific server locations, and the specifically reviewable DPA. Therefore, overall 'conditional' rather than 'yes'.
Sources
Strengths & weaknesses at a glance
| Strengths | Weaknesses |
|---|---|
| • Clear specialization in medical documentation and clinical workflows. | • Practically not meaningful for non-medical users, as the product is clearly tailored to clinical contexts. |
| • Over 100 integrations with medical systems. | • According to the pricing page, the free version is only usable to a limited extent in several advanced features. |
| • Support for 50+ specialties. | • Enterprise features such as custom integrations, enterprise authentication, and customizable data retention are not included in the entry-level plan. |
| • EU processing and storage of patient data. | • The privacy policy permits transfers of certain personal data outside the EEA under protective safeguards; a fully publicly accessible detailed overview of all processors/subprocessors could not be fully verified in the browser. |
| • No audio storage after transcription. | |
| • No use of patient or personal data for AI training. | |
| • Strong formal security/quality signals: ISO 27001, ISO 13485, CE/UKCA, NHS/country-specific compliance notices. |
Reviews
0 reviews in total
There are no confirmed reviews for this tool yet.
Submit review
Your review will only become visible after email confirmation. This protects the portal against abuse.
Report review
Please select the reason why this review should be checked.
GDPR-compliant usage possible?
The website contains several strong indications for GDPR-compliant use in the EU/EEA region: Tandem describes itself as a processor for customer data, refers to a data processing agreement, states that the processing and storage of patient data take place exclusively in European data centers, and explains that patient data are not used to train AI models. However, the publicly accessible website does not provide specific server countries/data center providers, a publicly viewable list of subprocessors, or a publicly accessible DPA text. As a result, use from an EU/EEA perspective appears plausibly well safeguarded, but is not documented with complete transparency.
Positive
Positive aspects include the explicit statements that all patient data are processed and stored in Europe, that no audio recordings are stored, that patient data are not used for AI training, and that Tandem is certified according to ISO 27001 and ISO 13485. In addition, the privacy policy describes its role as a processor and refers to a DPA.
Negative
A negative aspect is that the website does not provide any specific public information on individual server locations or countries, no publicly available list of subprocessors, and no directly viewable DPA content. Likewise, no on-premise, self-hosting, or clearly documented private cloud option was indicated on the website.
Server location
The website states that patient data are processed and stored exclusively in European data centers, or that all data remain within the EU. A specific country, specific data center, or specific hosting provider is not stated on the website.
