> 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/27.md). # Art. 27 — Fundamental rights impact assessment for high-risk AI systems 1. Prior to deploying a high-risk [AI system](https://headlesslaw.com/definitions/ai-act/ai-system/) referred to in [Article 6(2)](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/6.md), with the exception of high-risk AI systems intended to be used in the area listed in point 2 of Annex III, deployers that are bodies governed by public law, or are private entities providing public services, and deployers of high-risk AI systems referred to in points 5 (b) and (c) of Annex III, shall perform an assessment of the impact on fundamental rights that the use of such system may produce. For that purpose, deployers shall perform an assessment consisting of: 1. a description of the [deployer](https://headlesslaw.com/definitions/ai-act/deployer/)’s processes in which the high-risk AI system will be used in line with its [intended purpose](https://headlesslaw.com/definitions/ai-act/intended-purpose/); 2. a description of the period of time within which, and the frequency with which, each high-risk AI system is intended to be used; 3. the categories of natural persons and groups likely to be affected by its use in the specific context; 4. the specific risks of harm likely to have an impact on the categories of natural persons or groups of persons identified pursuant to point (c) of this paragraph, taking into account the information given by the [provider](https://headlesslaw.com/definitions/ai-act/provider/) pursuant to [Article 13](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/13.md); 5. a description of the implementation of human oversight measures, according to the [instructions for use](https://headlesslaw.com/definitions/ai-act/instructions-for-use/); 6. the measures to be taken in the case of the materialisation of those risks, including the arrangements for internal governance and complaint mechanisms. 2. The obligation laid down in paragraph 1 applies to the first use of the high-risk AI system. The deployer may, in similar cases, rely on previously conducted fundamental rights impact assessments or existing impact assessments carried out by provider. If, during the use of the high-risk AI system, the deployer considers that any of the elements listed in paragraph 1 has changed or is no longer up to date, the deployer shall take the necessary steps to update the information. 3. Once the assessment referred to in paragraph 1 of this Article has been performed, the deployer shall notify the [market surveillance authority](https://headlesslaw.com/definitions/ai-act/market-surveillance-authority/) of its results, submitting the filled-out template referred to in paragraph 5 of this Article as part of the notification. In the case referred to in [Article 46(1)](/mica.wtf/ai-act/chapter-iii-high-risk-ai-systems-art.-6-49/46.md), deployers may be exempt from that obligation to notify. 4. If any of the obligations laid down in this Article is already met through the data protection impact assessment conducted pursuant to Article 35 of Regulation (EU) 2016/679 or Article 27 of Directive (EU) 2016/680, the fundamental rights impact assessment referred to in paragraph 1 of this Article shall complement that data protection impact assessment. 5. The [AI Office](https://headlesslaw.com/definitions/ai-act/ai-office/) shall develop a template for a questionnaire, including through an automated tool, to facilitate deployers in complying with their obligations under this Article in a simplified manner. --- # 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/27.md?ask=&goal= ``` `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.