12
min read
Data portability: public vs private healthcare under EU law
Understand how GDPR, EHDS, and national health law create different data portability obligations for public and private healthcare providers across Europe

Data portability obligations apply to all EU healthcare providers. But which rules apply depends on whether the provider is public or private, because the lawful basis for processing determines which rights patients can actually enforce.
Three regulatory layers govern patient data portability
Healthcare organisations operating across Europe face a legal obligation on patient data portability, not merely a technical aspiration. Understanding data security & privacy obligations is a prerequisite for this analysis.
The first layer is the General Data Protection Regulation (GDPR), which sets the baseline right to data portability under Article 20, with a critical limitation that significantly narrows its application in public healthcare. The second is the European Health Data Space (EHDS) Regulation, Regulation (EU) 2025/327, which entered into force on 26 March 2025 and represents the most significant structural change to health data governance in EU history. The third is national implementing legislation, which governs how public health systems manage record access and transfer through sector-specific health law rather than data protection law.
These layers don't operate independently. GDPR remains the primary data protection framework. EHDS introduces sector-specific obligations that sit alongside it. As Taylor Wessing's analysis of the EHDS-GDPR relationship notes, EHDS builds a sectoral framework on top of GDPR rather than replacing it. Implementation runs in phases: general provisions apply from March 2027, primary and secondary use rules from March 2029. Any compliance assessment that relies on GDPR alone will produce an incomplete picture of what providers are actually required to do.
Why the public/private distinction determines which portability rights apply
GDPR Article 20 gives individuals the right to receive their personal data in a structured, commonly used, machine-readable format and to transmit it to another data controller. This right applies only where processing is based on consent (Article 6(1)(a) or Article 9(2)(a)) or on a contract (Article 6(1)(b)). Where processing is grounded in a legal obligation or the performance of a public task, Articles 6(1)(c) and 6(1)(e) respectively, Article 20 doesn't apply.
Most public healthcare providers process patient data under a statutory mandate. A national health service treating a patient does so not on the basis of a contract, nor typically on the basis of consent: it's fulfilling a legally defined public function. This means the GDPR portability right doesn't directly apply to the majority of public health system data processing in the EU. Patients who want to transfer records from a public hospital have to rely on national health law provisions instead, which vary considerably across Member States.
Private healthcare providers that process patient data on the basis of consent or contract are directly subject to GDPR Article 20. Patients can request their data in a machine-readable format, ask for direct transmission to another controller where technically feasible, and expect a response within one month, extendable by two months for complex requests provided the provider notifies the patient within the first month. What counts as portable "personal data" in a clinical context is broader than many providers assume: it includes data actively provided by the patient and data generated through the service relationship, but not data derived or inferred by the provider. That distinction becomes relevant when assessing whether AI-generated clinical codes or risk scores fall within scope.
Mixed-model providers, such as private clinics contracted to deliver services within a public health system, or public hospitals with private patient wings, face the most complex analysis. Arnold & Porter's advisory on the EHDS notes that the EHDS definition of "health data holder" applies to any legal person with the right or obligation to process personal health data, regardless of whether they're nominally public or private. Natural persons and microenterprises, defined as organisations with fewer than 10 employees and an annual turnover or balance sheet total not exceeding €2 million, are excluded from health data holder obligations by default, though Member States may extend those obligations to them. Providers operating across public and private modalities without a clear mapping of which activities rely on which lawful basis are exposed to compliance risk under both GDPR and EHDS.
How public providers handle record access today, and what changes under EHDS
Public healthcare providers implement patient record access and transfer rights through sector-specific legislation, with health ministries rather than data protection authorities administering the relevant obligations. The supervisory body, the enforcement mechanism, and the applicable timeline may all differ from those that apply to a private provider under GDPR.
These frameworks differ substantially by jurisdiction. Nordic models have relatively mature national infrastructure: Finland's Kanta system gives patients a centralised digital access point for records held across public providers. Germany introduced a statutory right to receive copies of records under the Patient Rights Act (Patientenrechtegesetz), requiring providers to respond without undue delay, alongside the Telematikinfrastruktur (TI) as a national interoperability backbone. France has implemented the Mon Espace Santé platform under national digital health legislation. Southern European public systems, Spain, Italy, and Portugal, have statutory access rights but face greater variation at the regional level, with implementation quality closely tied to regional health authority capacity.
The EHDS changes this materially. Its central aim is to establish a consistent framework for health data access and portability that applies across both public and private providers, closing the gap created by GDPR's lawful basis dependency. The EHDS introduces a strengthened primary use portability right under Article 7 that removes the lawful-basis restriction, covering data processed under any legal basis under Article 9 GDPR, not just consent or contract. This means patients will be able to seek portability of their health data from public healthcare providers that previously fell outside GDPR Article 20's scope, once the relevant provisions come into force in March 2029. As Skadden's legal briefing on the EHDS confirms, all EU-established healthcare providers, including hospitals, clinics, and private practices, are subject to the same EHDS compliance obligations for data sharing, interoperability, and patient access, with non-compliance carrying fines equivalent to those under GDPR.
The EHDS also introduces the MyHealth@EU infrastructure for cross-border access to patient health data across participating Member States, standardised data formats with HL7 FHIR (a widely used standard for exchanging healthcare information electronically) emerging as the interoperability baseline, and Health Data Access Bodies (HDABs) governing secondary use of health data by researchers, industry, and public bodies under a permit system rather than individual consent.
One tension worth flagging: a peer-reviewed analysis in Computer Law & Security Review identifies a conflict between Recital 12, which calls for portability to apply to any private or public data controller, and the operative text, which frames obligations around healthcare providers specifically. The precise scope of who qualifies as a health data holder in edge cases, covering wellness apps, occupational health providers, and telemedicine platforms, remains subject to interpretation. This provision is the one most likely to generate early enforcement disputes as national supervisory bodies begin applying the regulation.
Format and timeline requirements by provider type
GDPR requires portable data in a machine-readable format such as JSON, XML, or CSV, but doesn't mandate a specific technical standard, which produces significant variation in practice. The EHDS addresses this directly. The regulation requires health data holders to maintain structured, interoperable data in formats compatible with the EHDS technical framework (the European Electronic Health Record Exchange Format, EEHRxF); the exact technical specification, likely to draw on HL7 FHIR, is still being finalised through implementing acts due by March 2027.
Context | Applicable framework | Timeline |
|---|---|---|
Private provider (consent/contract basis) | GDPR Article 20 | One month; extendable by two months |
Public provider (public task basis) | National health law | Varies by Member State |
Germany (private and public) | Patient Rights Act | Without undue delay |
France | National digital health legislation | Varies by record type |
Post-EHDS (all providers) | EHDS primary use provisions | To be specified in implementing acts |
Cross-border portability: where fragmentation is most acute
A patient moving from France to the Netherlands, or a cross-border worker receiving care in a different Member State, currently has no reliable way to ensure their health records follow them. National medical record systems use different data models, different coding systems, and different access protocols.
The EHDS addresses this through MyHealth@EU, which requires Member States to participate in cross-border health data exchange through national contact points, building on the existing eHealth Digital Service Infrastructure (eHDSI) framework but significantly expanding its scope and legal mandate. Research on EHDS Health Data Access Body implementation identifies persistent challenges: inconsistent digital health system maturity across Member States, varying data quality standards, and the absence of harmonised governance frameworks for HDABs. For providers in border regions or serving internationally mobile patient populations, patient-held records remain the practical bridge solution until the EHDS infrastructure is operational.
Priority compliance gaps to close before EHDS deadlines
For IT and compliance teams building roadmaps ahead of EHDS phased deadlines, the highest-priority gaps are worth working through in turn.
Many providers, particularly in public systems, still generate clinical documentation as scanned PDFs or in proprietary legacy formats. Meeting EHDS format requirements will mean either replacing those systems or introducing middleware that can convert legacy outputs into HL7 FHIR-compliant exports. Closely related is the absence of patient-facing data access portals: the EHDS primary use framework treats digital access as the default, so providers that haven't yet deployed self-service patient portals will need to build or procure this capability.
Private providers relying on consent as a lawful basis need to be able to show that consent was freely given, specific, informed, and unambiguous, and to link consent records to specific data categories for portability purposes. Unclear consent documentation is a common gap that becomes harder to remediate retrospectively.
The most significant infrastructure gap in public health systems is legacy medical record systems that can't export structured data. A study mapping Spanish national security measures against EHDS secondary-use security requirements (Article 73) illustrates the scale of technical groundwork involved. Many existing public sector deployments lack the architecture to support this without significant remediation.
Finally, providers operating across public and private modalities need a documented processing activity mapping, updated to reflect EHDS health data holder obligations, as a foundational prerequisite. Without it, the compliance analysis for mixed-model processing simply can't be completed accurately.
For medical record systems operating across public and private environments, the practical requirements converge on four capabilities: exporting structured clinical data in HL7 FHIR-compliant formats that preserve SNOMED CT codes, ICD classifications, and medication terminology; patient-facing access portals that allow individuals to view, download, and transmit records without going through administrative staff; audit logging of all data access and export events; and interoperability with national medical record system infrastructure such as Germany's TI, France's Mon Espace Santé, or Finland's Kanta where applicable. Legacy systems in public institutions present a particular challenge across all four of these areas.
The EU Data Act (Regulation (EU) 2023/2854), which became applicable on 12 September 2025, adds further data-sharing obligations for connected medical devices and digital health tools, an additional compliance layer for private providers using internet-connected clinical equipment or wearable health monitoring devices. For a broader overview of the regulatory landscape, see our guide to EU healthcare AI regulations.
One genuine limitation is worth naming. As a directly applicable Regulation, the EHDS doesn't require Member States to transpose it into national law, but implementing acts and eventual case law will still shape how some provisions are applied in practice. The evolution of the health data concept across GDPR, the Data Governance Act, and the EHDS reflects a deliberate policy direction towards greater data access and cross-sector portability. Current compliance assessments should be treated as working hypotheses rather than settled conclusions, and national EHDS implementation processes deserve close attention, since they will set the operational parameters that determine what compliance actually requires in each jurisdiction.
Frequently asked questions
▶ Does GDPR give patients the right to port their health data from any provider?
No. Article 20 applies only where processing rests on consent or contract. Public providers operating under a statutory mandate fall outside it entirely. The practical consequence is that a patient's ability to enforce portability depends on which Member State they're in and what that country's health law actually says.
▶ What is the European Health Data Space and when does it apply?
Regulation (EU) 2025/327 entered into force on 26 March 2025 and builds a sector-specific health data framework on top of GDPR. General provisions apply from March 2027, primary and secondary use rules from March 2029. All EU-established healthcare providers are in scope, public and private alike.
▶ How does the EHDS change portability rights compared to GDPR?
The key practical shift is that EHDS Article 7 removes the lawful-basis filter. From March 2029, a patient can request portability from a public hospital that previously had no GDPR Article 20 obligation at all. The right follows the data, regardless of why the provider was processing it.
▶ What format must providers use when responding to a portability request?
Under GDPR, any structured machine-readable format (JSON, XML, CSV) satisfies the requirement. The EHDS raises the bar by mandating compatibility with the European Electronic Health Record Exchange Format. The exact technical specification is being finalised through implementing acts due by March 2027, with HL7 FHIR as the expected baseline.
▶ How long does a private provider have to respond to a data portability request?
One month under GDPR, extendable by two months for complex requests if the patient is notified within the first month. One practical point the body doesn't dwell on: the clock starts from receipt of the request, so providers without a clear intake process risk missing the deadline before they've even begun gathering the data.
▶ What portability obligations apply to mixed-model providers?
The EHDS definition of "health data holder" covers any legal person with the right or obligation to process personal health data, regardless of nominal public or private status. For mixed-model providers, the immediate action is a processing activity mapping that assigns a lawful basis to each activity type. Without that, neither the GDPR nor the EHDS analysis can be completed.
▶ How does cross-border portability work for patients moving between EU Member States?
Today there is no reliable mechanism. MyHealth@EU will require Member States to connect through national contact points, but the infrastructure is not yet operational. Providers in border regions or serving mobile populations should document this gap in their patient-facing communications now, rather than waiting for the EHDS deadlines to force the issue.
▶ What are the most common compliance gaps providers should address before EHDS deadlines?
In rough priority order: legacy clinical documentation in non-exportable formats, no patient-facing access portal, consent records that can't be linked to specific data categories, medical record systems that can't produce HL7 FHIR-compliant exports, and no documented processing activity mapping. The last item is the prerequisite for everything else, so it's the right place to start.
▶ Does the EHDS apply to small private practices and microenterprises?
Microenterprises (fewer than 10 employees, annual turnover or balance sheet total at or below 2 million euros) are excluded from health data holder obligations by default. Member States can extend those obligations nationally, so the safe approach for practices near that threshold is to track their own jurisdiction's implementation rather than assume the exclusion will hold.
▶ What does the EHDS mean for medical record systems in public institutions?
Most public-sector medical record systems were built for documentation, not structured export. Achieving EHDS interoperability will require either replacing those systems or adding middleware capable of converting legacy outputs into compliant formats. Providers should factor that remediation timeline into their 2027 and 2029 planning now, since procurement and implementation cycles in public health typically run two to four years.