This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIMBAA: CSAM Health Plexus"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
[[category:RIMBAA]] | [[category:RIMBAA]] | ||
| − | + | ==Overview== | |
| + | |||
| + | ..CSAM.. ..Plexus.. | ||
*See [http://www.csam.no/ CSAM company website] | *See [http://www.csam.no/ CSAM company website] | ||
| + | |||
| + | ==Architecture== | ||
| + | |||
| + | ===Architecture in terms of the technology matrix=== | ||
| + | In terms of the technology matrix the application uses the RP-CO-CS cells. | ||
| + | |||
| + | The application has to support the use of v3 messages (the CS square) in multiple countries. the internal format (the CO square) is the UV version of a constrained RIM model. RP is absed on the pure RIM, with some extensions for a) things that aren't modeled in the v3 standard, such as users/usergroups/accounts, and b) legacy clinical data for specialized clinical areas. | ||
| + | |||
| + | ===Architecture using platform specific terms=== | ||
| + | The core platform/technology used is Oracle JDeveloper and BPEL. Oracle TopLink as the [[ORM]] solution. | ||
Revision as of 08:57, 6 January 2010
Contents
Overview
..CSAM.. ..Plexus..
Architecture
Architecture in terms of the technology matrix
In terms of the technology matrix the application uses the RP-CO-CS cells.
The application has to support the use of v3 messages (the CS square) in multiple countries. the internal format (the CO square) is the UV version of a constrained RIM model. RP is absed on the pure RIM, with some extensions for a) things that aren't modeled in the v3 standard, such as users/usergroups/accounts, and b) legacy clinical data for specialized clinical areas.
Architecture using platform specific terms
The core platform/technology used is Oracle JDeveloper and BPEL. Oracle TopLink as the ORM solution.
