Digital Omnibus: what really changed in the AI Act’s definitions
The Digital Omnibus changes three things in Article 3 of the EU AI Act, and many overviews misquote them. Here is the check against the Official Journal.
In short
Amending Regulation (EU) 2026/1744 only recasts point 14 in Article 3 of the EU AI Act and inserts points 14a and 14b. The official German term is “Sicherheitsbauteil” (safety component), not “Sicherheitskomponente”, and the abbreviation “SMC” does not appear in the German text of the regulation. The English version does use “SMC” for small mid-cap enterprises. Article 3 contains 68 numbered definitions.
Auf Deutsch lesen: deutsche Fassung
Overviews are circulating that collect all the definitions of the EU AI Act in a single table, together with the changes made by the Digital Omnibus. The idea is good. That is exactly what you need in an audit. Only such a table has to be right word for word, because a definition is not a text that may be reproduced in paraphrase. It is the switch that decides how a system is classified. I read one of these German-language overviews against the Official Journal. The result is the reason for this article.
What the Omnibus actually changes in Article 3
The amending regulation bears the number (EU) 2026/1744. It is dated 8 July 2026, was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026. Its Article 1(4) touches the definitions, and does so sparingly. Point (a) amends point 14 and reproduces it in its full new wording. Point (b) inserts points 14a and 14b. Nothing more happens in Article 3. Anyone who reads that the Omnibus has rebuilt the definitions is reading too much into it.
This is the new point 14 in the official English version of the regulation:
“safety component” means a component of a product or of an AI system which fulfils a safety function for that product or AI system, or the failure or malfunctioning of which endangers the health and safety of persons or property; for the purposes of this definition, a component fulfils a safety function where its intended purpose is to prevent or mitigate risks to health and safety of persons or property;
The second half of the sentence is what is actually new. Previously it could be argued when a component fulfils a safety function. Now it is written down: where its intended purpose is to avert or mitigate risks. That is a restriction. A component that incidentally also increases safety, but whose purpose is a different one, no longer falls under it as a matter of course.
Where the circulating versions deviate
I laid the rows that were marked as new or amended in the overview I checked next to the official text. None of the three reproduces it.
| Official Journal, Regulation (EU) 2026/1744 | What the overview I checked said |
|---|---|
| “Sicherheitsbauteil” (safety component) | “Sicherheitskomponente” |
| “… die Gesundheit und Sicherheit von Personen oder Eigentum gefährdet” (endangers the health and safety of persons or property) | “… oder die Sicherheit von Sachwerten gefährdet” (or endangers the safety of material assets) |
| “ein Bauteil … wenn seine Zweckbestimmung darin besteht … abzuwenden oder zu mindern” (a component, where its intended purpose is to avert or mitigate) | “eine Komponente … bestimmungsgemäßer Zweck … verhindern oder zu mindern” (a different word for component, proper purpose, prevent or mitigate) |
| “Kleinst-, kleines oder mittleres Unternehmen” or “KMU” (micro, small or medium-sized enterprise, SME) | “Kleinstunternehmen, kleines und mittleres Unternehmen” (micro-enterprise, small and medium-sized enterprise) |
| “kleines Midcap-Unternehmen” (small mid-cap enterprise), defined by reference to a small enterprise with medium capitalisation | “kleines Mid-Cap-Unternehmen” or “SMC”, defined as a small mid-cap enterprise |
Why this is not quibbling over words
“Sicherheitsbauteil” is not an arbitrary synonym, it is the switching term for the high-risk classification. Article 6(1) classifies an AI system as high-risk if it is intended to be used as a safety component of a product covered by the Union harmonisation legislation in Annex I, and if that product requires a third-party conformity assessment. Anyone who has “Sicherheitskomponente” in their documentation searches the German text of the regulation for a word that does not occur there, and does not find the connection point.
With the mid-caps it is even clearer. The abbreviation “SMC” appears nowhere in the German text of the regulation, I searched for it specifically. The official German term is “kleines Midcap-Unternehmen”, without a hyphen, and it is determined by point 2 of the Annex to Recommendation (EU) 2025/1099, that is, by a small enterprise with medium capitalisation. In the circulating version, by contrast, the term defines itself: a small mid-cap enterprise is said to be a small mid-cap enterprise. With that, nobody can establish whether their company falls under it. And that is exactly what this point is about, because it decides on relief measures.
Article 3 has 68 points
The second issue concerns completeness. Article 3 of the EU AI Act contains 68 numbered definitions, plus 14a and 14b since the Omnibus. In the overview I checked, six of them were missing, and they are not the harmless ones:
- Point 37, special categories of personal data. It is the switching point for Article 4a, which Regulation (EU) 2026/1744 put in the place of the deleted Article 10(5), that is, for the question of when you may process such data at all for the detection and correction of bias.
- Point 43, post-remote biometric identification system. The counterpart to the real-time system, on which Article 26(10), among others, depends.
- Point 50 and point 51, personal data and non-personal data.
- Point 52, profiling.
- Point 62, critical infrastructure. An area of its own in Annex III.
The pattern is striking. The overview presents biometrics in full breadth, from biometric identification through verification to the real-time remote identification system, and leaves out precisely the post-remote system. Anyone who audits by it has half of biometrics in view and does not notice, because the table looks dense at this point.
A recital is not a definition
The third issue costs the most in an audit. Overviews like to pad their table with passages from the recitals: transparency, diversity, social and environmental well-being. These are the ethical principles from recital 27. They then stand in the same column as the definition of the AI system from Article 3(1), as if both were equally robust.
They are not. Recitals explain why a regulation looks the way it does. They are an aid to interpretation, but they do not create an obligation. You cannot write a nonconformity against a recital. If you want to base a finding on transparency, you need Article 13 or Article 50, not recital 27. A table that does not mark this invites exactly that mistake.
Four questions to ask of any overview of definitions
You do not have to be a lawyer for this. Four questions are enough, and you answer them in two minutes.
- Which source is given underneath? A position of the European Parliament is not law in force. What is in force is the version published in the Official Journal, here Regulation (EU) 2026/1744.
- What date is the status? Anyone who cites the Omnibus changes from a version before 24 July 2026 is citing a draft.
- Is the range of numbers complete? From 1 to 68, plus 14a and 14b. A gap means that someone made a selection and did not say so.
- Does every row say where it comes from? Article 3 is binding, a recital is not. If both stand undistinguished in one column, you are auditing with a table that does not itself know the decisive difference.
What this means for your management system
If you run an AI management system to ISO/IEC 42001, your list of legal requirements is documented information. Clause 7.5.3 requires that it is available and suitable and that changes are controlled. A table of definitions from an outdated draft does not meet that, however good it looks. And it comes to light at the moment when it is unpleasant: when someone looks up the cited wording in the Official Journal.
The practical advice is unspectacular and works immediately. For every legal requirement you adopt, keep two details with it: the reference and the date on which you last checked it against the primary source. Anyone who does that does not have to know everything. They only have to be able to show where they got it from.
If a provider evidences its conformity to you with an overview of this kind, that is not evidence, but a claim dressed up as a table. I take on this check for you.
View supplier auditsFinally, the caveat I impose on myself: this article, too, is a secondary source. Check it in the same way. The references are below, they lead straight to the Official Journal, and you need less than ten minutes for the comparison.
Primary sources
Frequently asked questions
What did the Digital Omnibus change in the definitions of the EU AI Act?+
Exactly three things. Article 1(4) of Regulation (EU) 2026/1744 recasts Article 3(14) and inserts points 14a (SME) and 14b (small mid-cap enterprise). No other points in Article 3 are affected.
Is the German term Sicherheitsbauteil or Sicherheitskomponente?+
Sicherheitsbauteil. That is the official German term for safety component in Article 3(14) of the EU AI Act, also after the amendment by the Digital Omnibus. “Sicherheitskomponente” is a widespread but incorrect rendering.
How many definitions does Article 3 of the EU AI Act contain?+
68 numbered definitions, plus points 14a and 14b since the Digital Omnibus.
Does the abbreviation SMC exist in the German text of the EU AI Act?+
No. The official German term is “kleines Midcap-Unternehmen” (small mid-cap enterprise) and is determined by point 2 of the Annex to Recommendation (EU) 2025/1099.
Author & expert review: Lars Zimmermann · ISO/IEC 42001 Senior Lead Auditor & Senior Lead Implementer · ISO/IEC 27001 Lead Auditor & Lead Implementer (PECB)
Last updated: 10 November 2026. Researched and reviewed to the best of our knowledge; not a substitute for individual legal advice.
Questions about your own case?
In a free 15-minute intro call we assess where you stand on ISO 42001, ISO 27001 and the EU AI Act, honestly and without a sales pitch.