« HIT Standards Committee Privacy and Security WG review | Main | What does it mean to be Direct Project compliant? »



Feed You can follow this conversation by subscribing to the comment feed for this post.

John Theisen


It is very interesting to watch the progression of discovery on this topic as reasonably intelligent people attempt to solve the problem and will, I believe given similar constraints, see that where we ended up with the Direct Project specification is one of the natural solutions.

The very fact that in the industry today we do not have vendors freely inter-operating and exchanging data with so called easy to develop with technologies such as REST, XMPP or HTTP/POX tells me that it is not as easy as people suspect to achieve.

For me, I really think the way to go is chipping away at this with known and established standards and the fact that we have two very solid reference implementations that substantially reduce the investment that an organization must make to inter-operate using the Direct Project's specification.

John T.

David C. Kibbe MD MBA

Thanks, Arien. Nice job of teasing out the details and the complexity. In my opinion, your examples from the real world of clinical medicine are quite accurate with respect to the likelihood of a given physician or medical practice needing to communicate across multiple boundaries, and many organizational networks, each with its own capabilities, vendors, and CAs.
Regards, DCK

The comments to this entry are closed.