Editorial

SolAce Secure Wire provides secure and reliable messaging over any network. SolAce Secure Wire was designed specifically for the HIPAA Security Rule, including compression, encryption, public/private keys, digital signatures, signed and authenticated receipts, and audit trails.

Our native messaging bus is based on features in IETF's AS2 Internet EDI (EDI-INT) protocol. Due to comments from our users, let's make a few things clear.

• This does NOT mean SolAce Secure Wire is AS2-compliant. In fact, we feel AS2 is horribly lacking in features, and the specification is incomplete or just not very well written to begin with (as of this writing in 2003).
• Yes, we realized up front that using a proprietary approach means some people will not adopt our solution. That's just fine with us, you don't have to use our stuff, it won't hurt our feelers one bit.
• AS2 is simply a point-to-point file transfer protocol with less features than FTP and a hole in receipt security. FTP is not a messaging solution, so SolAce Secure Wire is a mix of the two and is NOT an attempt at creating an AS2-compliant solution.
• If you don't mind a secure & reliable messaging solution based around XML-RPC web services with support for directory retrieval and both point-to-point (push/push) and hub-and-spoke (push/pull) topologies, then you're not losing anything (AS2 doesn't have it) and you are gaining all that was just listed (SolAce Secure Wire does have it).
• If you happen to be crazy enough to pay $20,000 to certify our product or your own product as AS2-compliant then we've got some Arizona beachfront property for sale.

While we're on the soapbox, we have reviewed the final rule approved mid-February 2003 to determine any gaps from when we developed SolAce Secure Wire originally, and have determined that the it was "defanged" between the proposed and final rules. SolAce Secure Wire was developed with the proposed HIPAA Security Rule in mind.