Difference between revisions of "RIMBAA: CSAM Health Plexus"
| Line 8: | Line 8: | ||
==Architecture== | ==Architecture== | ||
| + | |||
| + | ===Logical architecture=== | ||
| + | CSAM uses the HL7 RIM to design a clinical data repository. This is a flexible repository which can handle complete patient information, encounters, order/requests and results, or simply meta information about a given event. | ||
| + | |||
| + | Following the SOA principles, CSAM Health is using HL7 v3 messaging standard to build interfaces for both cross application communication and for application specific services. Having a pragmatic view on the application services, we use the HL7 elements which are already represented in CSAM Plexus. | ||
| + | |||
| + | The figure below illustrates the conceptual architecture of CSAM Plexus, where HL7 plays an important role inside our “black-box” | ||
| + | [[Image:ConseptualArchitecture.jpg]] | ||
===Architecture in terms of the technology matrix=== | ===Architecture in terms of the technology matrix=== | ||
In terms of the technology matrix the application uses the RP-CO-CS cells. | 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 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. |
| + | |||
| + | ===Base technology=== | ||
| + | CSAM Plexus is a J2EE application deplopyed on av WebLogic server. | ||
| + | Plexus Brainware Integration services are based on the bpel standard, giving us flexibility in processing the incomming/outgoing HL7 v3 based information. | ||
| + | The HL7 RIM is materialized in an Oracle database | ||
===Architecture using platform specific terms=== | ===Architecture using platform specific terms=== | ||
The core platform/technology used is Oracle JDeveloper and BPEL. Oracle TopLink as the [[ORM]] solution. | The core platform/technology used is Oracle JDeveloper and BPEL. Oracle TopLink as the [[ORM]] solution. | ||
Revision as of 00:20, 13 January 2010
Contents
Overview
CSAM Health as is a Norwegian based software development company, building applications for specialised care and integrated healthcare. CSAM has focused on HL7 for some years and has been working on migrating from custom made formats into utilizing both the HL7 RIM and the HL7 v3 messaging standard.
Architecture
Logical architecture
CSAM uses the HL7 RIM to design a clinical data repository. This is a flexible repository which can handle complete patient information, encounters, order/requests and results, or simply meta information about a given event.
Following the SOA principles, CSAM Health is using HL7 v3 messaging standard to build interfaces for both cross application communication and for application specific services. Having a pragmatic view on the application services, we use the HL7 elements which are already represented in CSAM Plexus.
The figure below illustrates the conceptual architecture of CSAM Plexus, where HL7 plays an important role inside our “black-box”
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.
Base technology
CSAM Plexus is a J2EE application deplopyed on av WebLogic server. Plexus Brainware Integration services are based on the bpel standard, giving us flexibility in processing the incomming/outgoing HL7 v3 based information. The HL7 RIM is materialized in an Oracle database
Architecture using platform specific terms
The core platform/technology used is Oracle JDeveloper and BPEL. Oracle TopLink as the ORM solution.
