The following is a summary of HealthUnity’s proposed architecture for healthcare information networks (HIEs and RHIOs). For a copy of the detailed document please request the “Model Architecture for the National Health Information Network” whitepaper

Click here to request the whitepaper

This section describes each of the integration and workflow patterns that are expected of a typical HIE/RHIO solution. In order to understand the different patterns utilized, it is important to first identify where these patterns are applicable.

Developing the patterns is a two step process. The first step is to identify the different parties that interact using the patterns.

In the HIE/RHIO network the following parties interact with the system. Note that operations could either be synchronous (i.e. the requestor waits for the response before proceeding) or asynchronous (i.e. the requestor does not wait for a response before proceeding).

The patterns are thus defined separately for the following interacting parties.

• Client End-Users: this includes the practitioner and office staff using the HIE/RHIO client interface
• Backend Adapter: this includes all the adapter components that interact with backend EMR or similar systems
• Network Level Services (a.k.a. Gateway services): These are network-deployed services that interface with Labs, ePrescribing networks, radiology centers etc.
• Other RHIOs and HIEs: This is the standardized interface with other RHIO implementations.

For the end user of the HIE/RHIO client, the following are the basic patterns of interaction with the system. Additional patterns for interaction can be built by composition of these basic patterns.

These are standardized patterns followed by network service providers, to receive requests and to respond to them. These are classified into two modes of operation Inbound-to-Provider and Outbound-from-provider.

The following are the general patterns that may be expected.