> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/integrations/messaging/hin-secure-email.md). # HIN Secure Email Welkin integrates with HIN (Health Info Net), Switzerland's trusted healthcare communication network. This integration enables secure, compliant email communication directly through the Welkin Care portal, ensuring that all sensitive communications meet Swiss healthcare data protection standards (DSG & GDPR). ## How it works in Welkin The secure email provider — HIN or Paubox — is set at the system level by an administrator. Once HIN is configured as the provider in system settings, Welkin routes secure emails through HIN. Automations configured in Designer can send secure emails via HIN. For example, patient notification automations that previously used Paubox can be configured to use HIN instead, depending on which provider is set in system settings. ## Setup HIN setup requires coordination with your Welkin implementation team. To enable HIN for your environment, contact . --- # 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.welkinhealth.com/integrations/messaging/hin-secure-email.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 `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.