In the Swiss healthcare sector, HIN is the de facto standard for protected electronic communication: physicians, hospitals, pharmacies, laboratories, and insurers exchange patient information over HIN-secured mail. For the IT staff responsible in these organizations, HIN is not an app but infrastructure, with its own on-premises components, its own deadlines, and a mail flow that differs fundamentally from open internet mail traffic.
Matching commands
Ready-to-run HIN commands for PowerShell and the Unix shell, with examples to copy.
Articles on HIN (3)
- Aug 1, 2026 Access Gateway 2026 HIN Platform Renewal 2026: Access Gateway, Client, and Deadlines Through September 14
- Jul 8, 2026 Backup & Recovery Backing up and restoring the HIN Mail Gateway after a failure
- Jun 19, 2026 Login Failure 15.0.5 HIN Mailgateway 15.0.5: Fixing Login Failures After a Cluster Update
Identity first
The foundation of the platform is the HIN identity: a verified electronic identity per healthcare professional or organization. The services build on it, above all HIN Mail: messages between HIN participants travel encrypted within the platform, and the identity of the other party is verified. Mail to recipients outside the HIN world is secured through protected delivery paths, for example portal retrieval. User access runs conventionally through the HIN Client on the workstation or organization-wide through central components.
The HIN Mail Gateway in an organization’s own mail flow
Organizations with their own mail infrastructure connect to HIN through the HIN Mail Gateway: a component in the organization’s own data center that sits as an SMTP station between the internal mail system (typically Exchange) and the HIN platform. Internally, users write ordinary mail; the gateway handles encryption and decryption toward the HIN world. The same operating rules therefore apply to the gateway as to any secure mail gateway: it is operationally critical in the mail path, its configuration and key material belong in the backup, its releases need to be installed in a planned manner, and its interaction with connectors in the mail system must be documented. In addition, the Access Gateway serves as the central access point for user authentication in larger environments.
Evolution of the platform
HIN develops the platform in generations. Such platform upgrades typically involve new network endpoints, minimum versions for the HIN Client and Access Gateway, and hardware generation changes for the Mail Gateway; they are announced by HIN and accompanied by transition periods.
Operational view
Three points govern operations: the delivery paths, meaning which messages travel through HIN and which through normal mail flow, along with the rules that make that decision; the version levels of gateway and clients, because platform upgrades come with minimum versions; and the identities, whose mapping to people and roles has to be maintained so that deputies and departures are represented correctly.