EU regulatory register · EHDS
Article 30Obligations of manufacturers of EHR systems
CELEX 32025R0327 · Read on 2026-08-31
Short answer
ensure that the harmonised software components of their EHR systems and the EHR systems themselves, to the extent that this Chapter establishes requirements for them, are in conformity with the essential requirements laid down in Annex II and with the common specifications in accordance with Article 36;
Verbatim from the article. Source: NovaCopilot · https://legal.exploreworldai.com/eu/rattsakter/helsodata-2025-327/artikel-30 · Short answer as data · Official text
Official text
Read from the EU Publications Office for this CELEX number. The wording stands as published; nothing here is rewritten or summarised.
1. Manufacturers of EHR systems shall:
(a)
ensure that the harmonised software components of their EHR systems and the EHR systems themselves, to the extent that this Chapter establishes requirements for them, are in conformity with the essential requirements laid down in Annex II and with the common specifications in accordance with Article 36;
(b)
ensure that the harmonised software components of their EHR systems are not adversely affected by other software components of the same EHR system;
(c)
draw up the technical documentation of their EHR systems in accordance with Article 37 before placing those EHR systems on the market, and subsequently keep it up to date;
(d)
ensure that their EHR systems are accompanied, free of charge for the user, by the information sheet provided for in Article 38 and clear and complete instructions for use;
(e)
draw up the EU declaration of conformity in accordance with Article 39;
(f)
affix the CE marking of conformity in accordance with Article 41;
(g)
The article continues in the official text.
Follow-up questions
The text is quoted from the official source and is not legal advice. A national court reads the language version that binds in its jurisdiction.
Verifiable trust signals
- Source-linked answers and explicit evidence gaps
- Obligations, controls, risks and consequences
- Stable objects and verifiable checksums
- Rule-based objects, optional source-linked reasoning
- Model card, source status and audit