High-risk AI systems are AI applications that pose significant risks to fundamental rights, safety, or health. The concept covers classification, governance, risk assessment and mandatory conformity measures. It aims to ensure robustness, transparency and human-centric safeguards throughout the system lifecycle. Organizations must combine processes, technica…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
High-risk AI systems are applications whose purpose, context, and potential impact create heightened requirements for safety and fundamental rights.
The term emerged with risk-based AI regulation, classifying systems by possible harm rather than technical novelty. The exact classification depends on the applicable law and use case.
Risk is not determined by the model alone: purpose, affected people, decision impact, and human oversight also matter. Systems used for safety-critical or consequential decisions need evidence about data, accuracy, monitoring, and accountability. Risk category is therefore a governance property of deployment.
Purpose and context determine the consequences an AI system may have.
Assessment considers possible harm to safety, health, or fundamental rights.
Responsible people must monitor, understand, and if needed override system behavior.
The classification guides procurement, documentation, testing, monitoring, and accountability. It is jurisdiction-specific and should be checked against current regulation before production use.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.