Difference between revisions of "ConnectR Superset Source"
Jump to navigation
Jump to search
(Created page with '=ConnectR Superset – Process Diagram= Image:ConnectR Superset Process Diagram.jpg =ConnectR Superset – Database Interaction= [[Image:ConnectR Superset Database Interactio…') |
John.Buckley (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | =ConnectR Superset – Process Diagram= | + | [[Category:ConnectR|Superset Source]] |
| + | __TOC__ | ||
| + | ==ConnectR Superset – Process Diagram== | ||
[[Image:ConnectR Superset Process Diagram.jpg]] | [[Image:ConnectR Superset Process Diagram.jpg]] | ||
| − | =ConnectR Superset – Database Interaction= | + | ==ConnectR Superset – Database Interaction== |
[[Image:ConnectR Superset Database Interaction.jpg]] | [[Image:ConnectR Superset Database Interaction.jpg]] | ||
| − | =ConnectR Superset - Example= | + | ==ConnectR Superset - Example== |
| − | ==Event triggered within AE-EHR== | + | ===Event triggered within AE-EHR=== |
[[Image:ConnectR Superset Example.jpg]] | [[Image:ConnectR Superset Example.jpg]] | ||
| − | ==ConnectR monitors, picks-up and processes the event== | + | ===ConnectR monitors, picks-up and processes the event=== |
[[Image:ConnectR Superset Example2.jpg]] | [[Image:ConnectR Superset Example2.jpg]] | ||
| − | ==Event is translated into well-structured message== | + | ===Event is translated into well-structured message=== |
[[Image:ConnectR Superset Example3.jpg]] | [[Image:ConnectR Superset Example3.jpg]] | ||
| − | =="Extract" stored procedures are called to pull pertinent information out of the AE-EHR related to the event== | + | ==="Extract" stored procedures are called to pull pertinent information out of the AE-EHR related to the event=== |
[[Image:ConnectR Superset Example4.jpg]] | [[Image:ConnectR Superset Example4.jpg]] | ||
| − | =Additional Information= | + | ==Additional Information== |
*When importing interface shells for outbound interfaces (move-to-live of test interface for instance), such as charge or order interfaces, it is imperative to ensure that there are NOT two or more superset source systems polling the same event table in an EHR database. | *When importing interface shells for outbound interfaces (move-to-live of test interface for instance), such as charge or order interfaces, it is imperative to ensure that there are NOT two or more superset source systems polling the same event table in an EHR database. | ||
*Recall, if there are two or more superset source systems polling the same event table in an EHR database, there will be conflicts and mismatches with the interface mapping and intended message processing. If there are more than one outbound superset source system, the steps in the next slide should be followed (execute these steps with the new source and target system NOT RUNNING) | *Recall, if there are two or more superset source systems polling the same event table in an EHR database, there will be conflicts and mismatches with the interface mapping and intended message processing. If there are more than one outbound superset source system, the steps in the next slide should be followed (execute these steps with the new source and target system NOT RUNNING) | ||
Latest revision as of 15:17, 16 November 2012
ConnectR Superset – Process Diagram
ConnectR Superset – Database Interaction
ConnectR Superset - Example
Event triggered within AE-EHR
ConnectR monitors, picks-up and processes the event
Event is translated into well-structured message
Additional Information
- When importing interface shells for outbound interfaces (move-to-live of test interface for instance), such as charge or order interfaces, it is imperative to ensure that there are NOT two or more superset source systems polling the same event table in an EHR database.
- Recall, if there are two or more superset source systems polling the same event table in an EHR database, there will be conflicts and mismatches with the interface mapping and intended message processing. If there are more than one outbound superset source system, the steps in the next slide should be followed (execute these steps with the new source and target system NOT RUNNING)