# 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 patient communications meet Swiss healthcare data protection standards (DSG & GDPR). HIN is the Swiss equivalent of Paubox — both provide HIPAA/DSG-compliant secure email, but HIN is specifically designed for the Swiss healthcare system and its regulatory requirements. ## What is HIN? HIN (Health Info Net AG) is Switzerland's national health information network. It provides secure digital communication infrastructure for healthcare professionals, including identity-verified secure email that meets the requirements of the Swiss Data Protection Act (DSG) and GDPR. ## How it works in Welkin Once HIN is configured as the secure email provider in system settings, Welkin uses it to deliver secure emails to patients across the Care portal and automations. The secure email provider — HIN or Paubox — is set at the system level by an administrator, and Welkin routes all secure email through the configured provider. **Supported workflows:** * Sending secure emails to patients manually from the Care portal * Automated secure email via Welkin Automations (e.g., appointment confirmations, care plan updates, patient notifications) ## Setup HIN setup requires coordination with your Welkin implementation team. To enable HIN for your environment, contact . --- # Agent Instructions: 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: ``` GET https://docs.welkinhealth.com/integrations/messaging/hin-secure-email.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.