> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/34.md).

# Art. 34 — Operational obligations of notified bodies

1. Notified bodies shall verify the conformity of high-risk AI systems in accordance with the [conformity assessment](https://headlesslaw.com/definitions/ai-act/conformity-assessment/) procedures set out in [Article 43](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/43.md).
2. Notified bodies shall avoid unnecessary burdens for providers when performing their activities, and take due account of the size of the [provider](https://headlesslaw.com/definitions/ai-act/provider/), the sector in which it operates, its structure and the degree of complexity of the high-risk [AI system](https://headlesslaw.com/definitions/ai-act/ai-system/) concerned, in particular in view of minimising administrative burdens and compliance costs for micro- and small enterprises within the meaning of Recommendation 2003/361/EC. The [notified body](https://headlesslaw.com/definitions/ai-act/notified-body/) shall, nevertheless, respect the degree of rigour and the level of protection required for the compliance of the high-risk AI system with the requirements of this Regulation.
3. Notified bodies shall make available and submit upon request all relevant documentation, including the providers’ documentation, to the [notifying authority](https://headlesslaw.com/definitions/ai-act/notifying-authority/) referred to in [Article 28](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/28.md) to allow that authority to conduct its assessment, designation, notification and monitoring activities, and to facilitate the assessment outlined in this Section.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/34.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.