This is part 2 in a series of articles on the basics of Direct messaging. Part 1 of this series can be found here.
In this article I'll attempt to provide an overview of how a Direct message gets from one person to another (from sender to recipient). I'm purposefully going to leave out a lot of detail because I want to focus on the very basic mechanisms of the transfer. We will then uncover the details through future articles, tackling
This is the first in a series of articles on the basics of Direct messaging. Be sure to come back for more in the series.
The Direct Project was designed by industry and government to be a simple and trusted means of sending and receiving secure messages. At its heart, Direct is simply encrypted email (aka S/MIME). But encrypting email has been around for a long time, so can’t we simply turn this feature on in Outlook and be happy?
Here are some notes and examples of how to take your ICAetc certificates and import them to your Java keystore.
Before you get started, you will need the openssl package. You can download openssl from our Downloads page. Be sure to add the openssl path to your system path before you start, and make sure when you open a shell (cmd.exe on Windows) that you can type “openssl” at the command prompt and it launches (does not return a program not found
The IHE requires TLS security for all connections. SOAP transactions, such as those used in XDS, are fairly straightforward to secure with TLS, due to good development tool support. Java, .NET and many other languages make TLS implementations at least manageable, and there are plenty of places to find help.
Securing ATNA and HL7v2, however, can often prove more challenging for a variety of reasons. Interface engine support for TLS is spotty (or may cost a lot); and while developer tool