The generic description of the eHealth Services Hub in part 3 of the Architecture and Design Blueprint includes a superset of all different types of services that may be needed at various points and levels in a distributed healthcare network.  As described in the section "Deployment Options" (p.105), depending on the topology of the ...

We had a fairly well attended session and the objective of providing an overview of the Health Connection Engine (HCE) and IHE XDS.b reference implementations was achieved, although with the time we had I could not get into a lot of detail. We have talked about the HCE in the past so I'll try to focus on the IHE aspect in this post. Background on ...

I'm here at the MS-HUG TechForum this week and right now sitting in the Kodiak Room in the Microsoft Conference Center where the TechForum takes place. Steve Aylward, the General Manager for the US Health and Life Sciences group, just gave us an update on the work that Microsoft is doing in supporting Healthcare Providers, Health Plans and Life ...

We have released version 2.1.1 of the Health Connection Engine to CodePlex. The release addresses a few issues we identified in setup and the Deployment Guide and some security and performance warning raised by FxCop. From the project description: ''The Health Connection Engine facilitates the interoperability between these multiple systems by ...

As you probably have seen from the HIMSS news, we have posted our first reference implementation for the Connected Health Framework reference architecture:Health Connection Engine (HCE): The Health Connection Engine is a reference implementation based on the Connected Health Framework architecture. HCE allows for faster and incremental development ...