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 ...

You put your finger where it hurts the most :-) But there is hope... Here are a few things to consider:The big players of today might not be the big players of tomorrow. They know that and you cannot win a market by holding information hostage. This is true not just for health, see what happened to Office file formats :-)Customers are demanding ...

First, let me say I wholeheartedly applaud Microsoft's efforts on NHIN and with CHF. We have to start somewhere. I represent the small software developer who is trying to develop and market a new front-end product for the healthcare market with some ideas that have been piloted in a few places. What has led me to despair in the past is ...

Let me try and paint a picture, let's see if this applies to any of you:I have many portals, mostly provided by the line of business application vendors, that do not talk to each other I can look at the information in the portal, but on order to change it I need to go back to the original application I have multiple applications that do not ...

References, checklists and further information

How to use the Architecture and Design Blueprint

Technical framework

Business framework

Introduction and overview