The date everyone quotes for Europe's health data law is March 2027.

If you make a medical device or an IVD that claims it can exchange data with hospital record systems, that is not your date.

Your date is 2029 or 2031. Which one depends on the kind of data your claim covers. What arrives in 2027 is the rulebook you will be tested against.

That gap is build-and-test time. Most manufacturers will spend it waiting. They should not.

Which medical device and IVD manufacturers does EHDS Article 27 actually catch?

The European Health Data Space Regulation, Regulation (EU) 2025/327, does not pull every medical device into scope. It catches one behaviour: a claim.

Article 27(1) reads: "Manufacturers of medical devices or in vitro diagnostic medical devices, as defined in Article 2, point (1), of Regulation (EU) 2017/745 and Article 2, point (2), of Regulation (EU) 2017/746, respectively, that claim interoperability of those medical devices or in vitro diagnostic medical devices with the harmonised software components of EHR systems shall prove compliance..."

So the test is not whether you handle health data. It is whether you claim interoperability with the harmonised software components of EHR systems.

If your device or IVD says, anywhere, that it exchanges data with EHR systems, assume you are in the conversation until you have read your own labelling, instructions for use and marketing copy against that sentence.

Article 27(2) applies the same duty to providers of high-risk AI systems that sit outside the MDR and IVDR. If your software is regulated as an AI system rather than a device, the same logic follows.

What does an interoperability claim commit you to proving?

The rest of Article 27(1) names the target. Manufacturers "shall prove compliance with the essential requirements on the European interoperability software component for EHR systems and the European logging software component for EHR systems, laid down in Section 2 of Annex II to this Regulation. Article 36 of this Regulation shall apply to those medical devices and in vitro diagnostic medical devices."

Two components, each defined in Article 2(2):

→ The European interoperability software component "provides and receives personal electronic health data under a priority category for primary use" in "the European electronic health record exchange format."

→ The European logging software component "provides logging information related to access by health professionals or other individuals to priority categories of personal electronic health data," in the format defined in point 3.2 of Annex II.

Annex II states that its essential requirements "shall apply mutatis mutandis to medical devices, in vitro diagnostic medical devices, AI systems and wellness applications claiming interoperability with EHR systems."

Section 2 of Annex II, titled "Requirements for interoperability," leans heavily on the European electronic health record exchange format. One example, point 2.2: "Where an EHR system is designed to store or intermediate personal electronic health data, it shall be able to receive personal electronic health data in the European electronic health record exchange format, by means of the European interoperability software component for EHR systems."

"Mutatis mutandis" is doing real work there. Annex II was written for EHR systems. How each point translates to your device is a judgement your team will have to document. That is exactly the kind of judgement a notified body will ask you to show.

Why does 26 March 2027 not trigger Article 27 for manufacturers?

Article 105 does say: "This Regulation shall apply from 26 March 2027."

The next sentence carves Article 27 out: "However, Articles 3 to 15, Article 23(2) to (6), Articles 25, 26, 27, 47, 48 and 49 shall apply as follows."

Article 27 is on that list. It does not follow the March 2027 date. It follows a staged schedule tied to data categories.

For a manufacturer, that is the whole story of this piece. Nothing in Article 27 binds you in March 2027. Its duty to prove compliance with Annex II starts later, on one of two dates.

Is your device on the 2029 or the 2031 clock?

Article 105 sets the two dates:

→ "(a) from 26 March 2029 to priority categories of personal electronic health data referred to in Article 14(1), points (a), (b) and (c)"

→ "(b) from 26 March 2031 to priority categories of personal electronic health data referred to in Article 14(1), points (d), (e) and (f)"

Article 14(1) lists the six priority categories:

  • (a) patient summaries
  • (b) electronic prescriptions
  • (c) electronic dispensations
  • (d) medical imaging studies and related imaging reports
  • (e) medical test results, including laboratory and other diagnostic results and related reports
  • (f) discharge reports

So your clock depends on which data your interoperability claim covers. In practice:

→ An imaging device whose claim covers imaging studies and reports maps to point (d). That points to 2031.

→ An IVD whose claim covers laboratory results maps to point (e). That also points to 2031.

→ Software whose claim covers e-prescriptions, dispensations or patient summaries maps to points (a) to (c). That points to 2029.

This is a mapping exercise, not a legal classification. A single product can touch more than one category. If your claim spans both groups, plan to the earlier date for the data that triggers it.

A third rule, point (c) of Article 105, applies when the Commission amends the main characteristics of a category in Annex I by delegated act. The date then runs "from one year from the date established in a delegated act," provided it falls after the (a) or (b) date. Keep it on your watch list. It does not move your baseline.

What lands in 2027 that you should track now: the Article 36 common specifications

Here is what is genuinely due in 2027. It is a Commission duty, not yours.

Article 36(1): "By 26 March 2027, the Commission shall, by means of implementing acts, adopt common specifications in respect of the essential requirements laid down in Annex II, including a common template and a time limit for implementing those common specifications."

The same paragraph says that, where relevant, the specifications "shall take into account the specificities of medical devices and high-risk AI systems referred to in Article 27(1) and (2)."

Three points matter for a manufacturer.

They set the test. The EHDS common specifications will translate Annex II into something you can build against. Article 36(2) says they will include their scope, applicability, version, validity period, "a normative part," and "an explanatory part, including any relevant implementation guidelines."

They offer a presumption. Under Article 36(4), devices and IVDs "that are in conformity with the common specifications... shall be considered to be in conformity with the essential requirements covered by those common specifications."

They apply on your clock, not 2027. Article 105 says the implementing acts under Article 36(1) "shall apply from the dates referred to in the third paragraph of this Article depending on the categories of personal electronic health data." That means 2029 or 2031 again.

Article 36(5) adds that where specifications affect devices under Regulation (EU) 2017/745 or (EU) 2017/746, their adoption "may be preceded by a consultation with the Medical Device Coordination Group." Watch that channel.

A caveat. Our corpus holds the Regulation text, not the implementing acts. We do not know from source whether the Commission has adopted them yet, or what they will say. Treat any summary of their content you see before publication with care.

How do you fold EHDS evidence into the MDR or IVDR technical file you already run?

You already maintain technical documentation under the MDR or IVDR. Article 27 does not prescribe a separate file. It adds a second set of requirements to evidence for one specific claim.

The practical move is to keep the Annex II evidence next to the claim it supports:

→ The interoperability claim, quoted from your labelling or instructions for use.

→ The Article 14(1) data categories it touches, and the resulting 2029 or 2031 date.

→ How each relevant Annex II point applies to your device, with your "mutatis mutandis" reasoning written down.

→ Test evidence against the European electronic health record exchange format and logging requirements, once the specifications define them.

→ The version of the common specifications you tested against, since Article 36(2) gives each one a version and validity period.

Kept that way, a reviewer can follow one line from claim to category to date to evidence. That is the question you will be asked.

What can a manufacturer usefully finish before the specifications are final?

You cannot test against specifications you have not seen. You can do everything that comes before the test.

  1. Inventory every interoperability claim. Labelling, instructions for use, tender responses, sales decks. Any place your product says it talks to EHR systems.
  2. Tag each claim to Article 14(1) categories. This sets its clock. Products with no claim drop out of Article 27 scope.
  3. Name an owner for Article 36. One person tracks the implementing acts, MDCG consultation and the version that will apply.
  4. Decide where Annex II evidence lives. Pick the slot in your existing technical documentation now, so 2028 is not a restructuring project.
  5. Revisit marketing language. If a claim is loose, either commit to it with evidence or narrow it. The duty attaches to what you claim.

None of this depends on unpublished text. All of it shortens the path once the specifications land.

At Aigis, each interoperability claim is held against the Article 27 text, and its clock is derived from the Article 14(1) categories it touches. The mapping is source-grounded: every obligation traces to a verbatim quote from the Regulation. When a notified body or authority asks why a product is on the 2031 clock, the answer is a query, not a project.

See how it maps for device and IVD portfolios at agrc.ai/medical-devices.

FAQ: EHDS, medical devices, IVDs and EHR interoperability

Does EHDS Article 27 apply to medical device manufacturers from 26 March 2027? No. Article 105 lists Article 27 among the provisions that apply on a staged basis: from 26 March 2029 for the categories in Article 14(1)(a) to (c), and from 26 March 2031 for those in points (d) to (f).

Which manufacturers fall under Article 27? Manufacturers of medical devices or IVDs that "claim interoperability" with the harmonised software components of EHR systems. Article 27(2) extends the same duty to high-risk AI systems outside the MDR and IVDR.

What is due by 26 March 2027? The Commission's duty under Article 36(1) to adopt common specifications for the Annex II essential requirements, by implementing acts. That is a Commission deadline. Under Article 105, those acts then apply from the 2029 or 2031 dates, by data category.

Does meeting the common specifications prove compliance? Article 36(4) provides that devices and IVDs in conformity with the common specifications "shall be considered to be in conformity with the essential requirements covered by those common specifications." The presumption covers only the requirements those specifications address.

For broader programme context, see agrc.ai/platform and agrc.ai/risk-management.