> For the complete documentation index, see [llms.txt](https://docs.voa.health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voa.health/integracao/plugin.md).
# Plugin
### Visão Geral
Esta documentação descreve como integrar a Voa com sistemas de prontuários eletrônicos por meio de um Plugin injetado via script na página.
### Funcionalidades
* Carregar a Voa dentro do sistema de prontuário eletrônico
* Iniciar e gerenciar consultas diretamente do prontuário
* Comunicação bidirecional entre a Voa e o prontuário eletrônico
{% hint style="warning" %}
Plugin (e a [Chave de API](https://docs.voa.health/api-reference/chaves-de-api) que o autentica) permite **usar a Voa dentro de outros sistemas** — gravar atendimentos e gerar documentos. A Voa **não disponibiliza API pública de consulta de dados**: não é possível ler ou exportar pacientes, consultas ou documentos via API.
{% endhint %}
### Suporte
Para questões técnicas ou suporte, entre em contato com nossa equipe de integração em .
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.voa.health/integracao/plugin.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.