HIE BLOG: Direct messaging

Secure Direct Messaging for Provider-to-Provider Communications

Timeliness and Productivity are two of the keys to successful Practice Management. Being able to quickly communicate from provider to provider can mean saving a life or cutting down on the cost of operations that includes time, staff and expense. The Dept of Health and Human Services ONC has developed regulations that require secure encrypted...

View full post »

OPC – FOSS vs Proprietary HIT

By Richard Braman CTO OPC – You Know Me By now,  if you haven’t  been hiding under a rock somewhere, you have probably heard of OPM (Other People’s Money), and OPP (Other People’s (relationship) Partners).  But today, I want to talk to you about what I like to refer to as OPC “Other People’s Code”,...

View full post »

NHIN Direct: Beyond Bare Metal Series

Beyond Bare Metal Series discusses moving the Java Reference implementation code “Known as Bare Metal” from the Direct Project and tuning it into a production capable Direct Messaging system. Some of the topics we have already blogged include: Beyond Bare Metal: Enabling S-POP and S-SMTP in Direct Beyond Bare Metal: Integrating NwHIN Direct to Use...

View full post »

Beyond Bare Metal: Enabling S-POP and S-SMTP in Direct

Background In order to make sure the connection between the Direct User and the Direct James Mail server secure, you must enable S-POP and S-SMTP, which simply adds SSL to secure the connection . Encryption between the client and server is required for HIPAA and Meaningful Use Privacy and Security. The following shows how to...

View full post »

Beyond Bare Metal: Integrating NwHIN Direct to Use LDAP for User Authentication

Part of our deployment strategy for NwHIN Direct Java Bare Metal project into a production environment requires that we replace the default James User store with an LDAP based schema. James has been configured to use LDAP before, so there were some example classes for us to look at and consider as we built our...

View full post »