> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/pt-br/triggers/others/hl7.md).

# HL7 Trigger

Saiba mais sobre o HL7 Trigger e como usá-lo na Digibee Integration Platform.

O **HL7 Trigger** recebe mensagens no formato HL7 de sistemas de saúde para a Digibee Integration Platform. HL7 (Health Level 7) é um protocolo de comunicação amplamente utilizado na área da saúde para a troca de dados entre sistemas e dispositivos médicos.

Para enviar mensagens HL7 da Plataforma para sistemas externos, utilize o [conector HL7](/documentation/connectors-and-triggers/pt-br/connectors/industry-solutions/hl7.md).

## **Parâmetros**

Dê uma olhada nos parâmetros de configuração do trigger.

<table data-full-width="true"><thead><tr><th>Parâmetro</th><th>Descrição</th><th>Valor padrão</th><th>Tipo de dado</th></tr></thead><tbody><tr><td><strong>HL7 Pipeline Name</strong></td><td>Nome do pipeline.</td><td>hl7-pipeline</td><td>String</td></tr><tr><td><strong>HL7 Message Charset</strong></td><td>Charset usado para interpretar a mensagem HL7 recebida pelo trigger.</td><td>UTF-8</td><td>String</td></tr><tr><td><strong>Maximum Connection Timeout (in ms)</strong></td><td>Tempo máximo permitido para estabelecer a conexão entre o trigger e a aplicação cliente, em milissegundos.</td><td>600000</td><td>Integer</td></tr><tr><td><strong>Maximum Concurrent Connections</strong></td><td>Número máximo de conexões simultâneas que o trigger pode estabelecer para receber mensagens HL7 da aplicação cliente.</td><td>5</td><td>Integer</td></tr><tr><td><strong>Pipeline Execution Timeout (in ms)</strong></td><td>Tempo máximo permitido para a execução do pipeline antes do seu encerramento por timeout, em milissegundos.</td><td>30000</td><td>Integer</td></tr><tr><td><strong>Filter from Header (MSH-3)</strong></td><td>Valor do cabeçalho HL7 usado para filtrar mensagens por tipo. Este campo é obrigatório e lê o cabeçalho MSH-3 para identificar diferentes tipos de mensagem.</td><td>N/A</td><td>Header</td></tr><tr><td><strong>Documentation</strong></td><td>Campo opcional para descrever a configuração do conector e quaisquer regras de negócio relevantes.</td><td>N/A</td><td>String</td></tr></tbody></table>

## **HL7 Trigger em ação**

### Parâmetro Filter from Header (MSH-3): Exemplo de uso

Os filtros de cabeçalho a serem incluídos devem seguir o formato padrão de palavra única, conforme mostrado no exemplo abaixo:

<figure><img src="https://3268428548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSKBJ6ZiEWBU93x170HH4%2Fuploads%2FJeeQNT8zgfRGbjoPfqI1%2Fhl1.png?alt=media&amp;token=2421e130-ddc3-4f24-ae4a-6db970ef7e45" alt=""><figcaption></figcaption></figure>

Filtros já habilitados nas configurações do parâmetro manterão o formato original:

<figure><img src="https://3268428548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSKBJ6ZiEWBU93x170HH4%2Fuploads%2FuUttm9cVrzJxg6kFXl7r%2Fhl72.png?alt=media&amp;token=9e9a10ba-3db7-44a5-8d8e-1e0b76860bc0" alt="" width="563"><figcaption></figcaption></figure>

### **Saída**

```json
{
 "body": "<CONTEUDO_DA_MSG_HL7>"
}
```

Exemplo de mensagem (anonimizada):

{% code overflow="wrap" %}

```json
{
"body": "MSH|^~\\&|TESTE|SFCT|RAPP|RFCT|20080312181835||ADT^A01|0D23ACC3-17CD-4FF4-BE66-AD4A6572079E|P|2.4\rEVN|A01|20080312181835\rPID|1||722347^^^^MR||PATIENT^TEST||19581221|F|||HIGH STREET 91^^SAINT PAUL^MN^55175^USA||(123)456-78-90^^PH|(844)955-17-21^^PH\rPV1|1|I|P166^R8^B4|R|||728625^WRIGHT^AMANDA^^MD^DR\rDG1|1|I9|472|CHRONIC PHARYNGITIS AND NASOPHARYNGITIS||A"
}
```

{% endcode %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/connectors-and-triggers/pt-br/triggers/others/hl7.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.