The latest release of K2 blackpearl adds support for secure communication through HTTPS.
According to the release notes,
During the installation of K2 4.6.7 all K2 sites will be certified and configured to run as HTTPS or HTTP. The K2 Workspace site can run as previously configured (HTTP) or it can run as a certified site (HTTPS). When using the K2 installer to create your sites, both HTTP and HTTPS will be setup [SIC] and created with certificates generated by K2. Upgrades will use previously setup [SIC] bindings, with the user having the ability to choose which bindings must be configured for K2.
This is welcome news, particularly for those of us supporting healthcare operations. The addition of “out-of-the-box” secure protocol support can green-light expansion of workflow solutions to include PHI (and other sensitive information)-related processes.