Heath Information Technology Commission Report - Fy2010 Appropriation Bill - Michigan Department Of Community Health Page 43

ADVERTISEMENT

of Community Health must also develop a set of interfaces to expose their services as
described above.
4.3.10
Technical Architecture/Approach
This section describes the components of the MiHIN Shared Services Bus (SSB) architecture.
The symbols next to each component title reference the symbols used in Figure 1, the MiHIN
Conceptual Architecture.
4.3.10.1
M
HIN S
S
B
I
HARED
ERVICES
US
The MiHIN Shared Services will be designed as an Enterprise Service Bus (ESB) architecture.
The ESB will be capable of supporting ESB nodes which can provide transaction services. The
exact topology of the MiHIN ESB has not yet been designed (single instance or federated for
example). The ESB will support one or more service registries for web services provided by
secure nodes. Community HIEs will be required to be secure nodes and utilize a four level
protocol stack for communication to the ESB.
4.3.10.2
EMPI/RLS
Enterprise Master Patient Index/Record Locator Service will be used for subject discovery
(patient lookup) and content indexing services. This component can either be a single
component or two separate components.
4.3.10.3
P
I
ROVIDER
NDEX
This is an index of all care providers in the state. This could be part of the EMPI listed above or
could be implemented as a User Directory.
4.3.10.4
M
G
ESSAGING
ATEWAY
Used for all transaction-based services such as Lab Ordering, Results Reporting and Eligibility
Checking. Primary function with be interface transactions and message translation.
Nomenclature normalization will be expected to happen at the HIE level.
4.3.10.5
D
W
/R
ATA
AREHOUSE
EPOSITORY
Data repository would be used for centralized storage of data for Public Health Reporting,
Quality Reporting, Medical Research and Chronic Disease Registries.
MiHIN Strategic Plan
Page 37

ADVERTISEMENT

00 votes

Related Articles

Related forms

Related Categories

Parent category: Legal