1. Data Normalization Architecture
Institution
Mayo Clinic
SHARPn cloud
Direct Mirth input
Institutional back-end
Mirth Connect
NwHIN Aurion Gateway
SHARP NwHIN Aurion Gateway
Mirth
Connect
UIMA
Pipeline
CEM Instance Database
Architecture concept

2. Cloud Images to Realize Architecture
Institution
Mayo Clinic
SHARPn cloud
Direct Mirth input
Mirth Connect with NwHIN/Aurion 
plus the Data Normalization pipeline
Institutional back-end
Mirth Connect
NwHIN Aurion Gateway
SHARP NwHIN Aurion Gateway
Mirth
Connect
UIMA
Pipeline
CEM Instance Database
emi-11B51218*
Architecture concept
SHARPn cloud image
* SHARPn collaborators use

3. Component descriptions
Data is passed from an organization to the data normalization pipeline.
External to the cloud environment this is through NwHIN Connect Gateway.
Internally this is simply via the file system.
Mirth Connect transforms incoming data from HL7 messages, CCD and CDA documents to XML appropriate to the configuration of the pipeline. Mirth could also be used at the institution for transformation before being sent over the wire.
The UIMA-based pipeline transforms the incoming XML documents to objects represented by CEMs.
Syntactic (extract values from XML and place into CEM fields based on configuration file)
Semantic (transform local codes to standardized codes based on configuration file)
The CEM XML output is sent to Mirth Connect
Mirth Connect transforms the CEM XML result into a database (or other desired forms) for further consumption and research