Why is that better than a Web portal or a traditional RHIO architecture?
It really depends on what you’re trying to do. If you’re trying to build a system to provide a single view of information across multiple applications in an enterprise, accessible from anywhere, a portal is the ideal choice. If you’re trying to create an aggregated view of information about a patient collected across a community, the RHIO approaches may be the way to go. If however, your goal is to automate the exchange of information between a hospital and a remote physician EMR, neither portals nor RHIO architectures are good choices simply because it’s not what they were designed to do. To solve that problem, you require some type of intelligence to interface to applications installed on private, inaccessible networks managed by different organizations, built using a variety of technologies and standards. You must be able to securely distribute information from one private network to another. Also, because you must install software in remote locations across the community, whatever
